TY - JOUR
AU - Hoeltje, Dirk
AB - Empirical Software Engineering, 2, 143–207 (1997) ° c 1997 Kluwer Academic Publishers, Boston. Manufactured in The Netherlands. Qualitative Analysis of a Requirements Change Process KHALED EL EMAM elemam@iese.fhg.de Fraunhofer—Institute for Experimental Software Engineering, Germany DIRK HOELTJE Positron Inc., Canada 1. Introduction The implementation of good software requirements management practices is believed to be one of the first process improvement steps that an organization should take. This is clear, for example, in the implied staging of practices in the CMM for software where requirements management is a level 2 Key Process Area (KPA) (Software Engineering Institute, 1995). One analysis of data available at the SEI found that 61% of assessments had findings that map to the requirements management KPA (Kitson and Masters, 1993). This indicates that there is an industrial priority to improve software requirements management practices. In the related discipline of systems engineering, good systems requirements management (SRM) practices are believed to be some of the first that should be addressed to increase systems engineering maturity. For example, in one systems engineering maturity model generalized from the CMM for software, the system requirements management KPA is at level 2 (Brill and Brammer, 1993). In another systems engineering maturity model, 
TI - Qualitative Analysis of a Requirements Change Process
JF - Empirical Software Engineering
DO - 10.1023/A:1009797116594
DA - 2004-09-28
UR - https://www.deepdyve.com/lp/springer-journals/qualitative-analysis-of-a-requirements-change-process-PY7ZRRJg2K
SP - 143
EP - 152
VL - 2
IS - 2
DP - DeepDyve
ER -