Requirements and Data Content Evaluation of Industry In-House Data Management System

Abstract

This paper presents an industrial case study performed on an in-house developed data management system for an automation firm. This data management system has been in use and evolving over a span of fifteen years. To ensure the system is robust to withstand the future growth of the corporation, a study is done to identify deficiencies that may prohibit efficient large scale data management. Specifically, this case study focused on the means in which project requirements are managed and explored the issues of perceived utility in the system. Two major findings are presented: completion metrics are not consistent or expressive of the actual needs and there is no linking between the activities and the original client requirements. Thus, the results of the study were used to depict the potential vulnerability of such deficiencies.

Corporate Requirement Culture in Development of a Large Scale Medical System: A Case Study

“…(Tony,3/8/16) This has also been observed in literature. Where, the most influential variable on the cost of requirements stems from change management, with a significant amount of time also spent collecting and finding information which is inconsequential to the accomplishment of activities and tasks (Morkos et al, 2010). This was further triangulated by the company's Systems Engineering director in his statement:…”

“…(Oakley,3/11/16) As designers look to various knowledge bases including existing and pre-existing project records (Morkos et al, 2010), this is a notable point tying in with comments made by the other directors. As delays are often a result of the time expended during data acquisition (Morkos et al, 2010), the time expended by team members to perform cumbersome document comparisons were both manual and cumbersome, simultaneously not furthering project development. As a result, the company installed state-of-the-art document control and requirements tracing tools and validated them.…”

“…Requirements change is defined here as the addition, deletion, or modification of existing requirements (Obeidat, 2016). The perspectives of the parties involved with requirements change in large complex projects is still an aspect that is not well understood (Almefelt et al, 2006;Morkos et al, 2010). As requirements are at the forefront of the design process, the requirements process supports many of the activities in the design process (Tayal, 2013).…”

Examining the Differences in Student Motivation for Industry Projects and Non-Industry Projects in Senior Capstone Design

“…4 Further, senior design provides students the opportunity to work on a project where they can both address both technical requirements (something they learn in course work) and learn how to manage projects (an aspect of engineering they have yet to learn). 5 Prior research performed by the authors has determined that motivation plays a significant role on students' performance in senior design capstone courses. 3,[6][7][8] As such, we implement qualitative research methods to assist in explaining this phenomenon.…”

A Mixed Methods Analysis of Motivation Factors in Senior Capstone Design Courses

“…Further, it provides students the opportunity to work on a project where they can both address both technical requirements and learn how to manage projects. 5 Prior research performed by the authors has determined that motivation plays a significant role on students' performance in senior design capstone courses. [6][7][8][9] As such, we implement qualitative research methods to assist in explaining this phenomenon.…”