论文信息 - 3.3.2 The Communications Requirements Evaluation & Assessment Prototype (CREAP) Project: A Case Study of a System Engineering Educational Project

3.3.2 The Communications Requirements Evaluation & Assessment Prototype (CREAP) Project: A Case Study of a System Engineering Educational Project

This paper contains a case study describ- ing the development of a software tool to prove a con- cept for use in design to inventory scenarios. The tool was developed by Master's students at the University of South Australia. The case study, designed as a reference for similar activities in other academic institutions, con- tains a list of lessons learned on the project. All the lessons learned have to do with the non-technical as- pects of the project. Even though the project was small, many of the attributes of large projects were seen. BACKGROUND

Joseph Kasser | Stephen C. Cook | Anthony Pilgrim | Yoyok Gamaliel | Dat Bao Ton

[1] Joseph Kasser,et al. 6.3.2 A Frame‐Based Approach to Requirements Engineering , 2001 .

[2] J. E. Kasser. Using organizational engineering to build defect free systems, on schedule and within budget , 1999, PICMET '99: Portland International Conference on Management of Engineering and Technology. Proceedings Vol-1: Book of Summaries (IEEE Cat. No.99CH36310).

[3] Joseph Kasser,et al. 9.2.0 The Communications Requirements Evaluation & Assessment Prototype (CREAP) , 2002 .

[4] Joseph Kasser,et al. Applying total quality management to systems engineering , 1995 .

[5] Joseph Kasser. A Framework for Requirements Engineering in a Digital Inte- grated Environment 1 , 2000 .