Evaluating the Quality of a UML Business Model
RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
The Automated Extraction of Requirements from UML Models
RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
The Evaluation of Large, Complex UML Analysis and Design Models
Proceedings of the 26th International Conference on Software Engineering
Foundations of the unified modeling language
2FACS'97 Proceedings of the 2nd BCS-FACS conference on Northern Formal Methods
Beyond Documents: Visualizing Informal Communication
REV '08 Proceedings of the 2008 Requirements Engineering Visualization
Model-driven generative development of measurement software
Software and Systems Modeling (SoSyM)
Automated measurement of models of requirements
Software Quality Control
| Hi-index | 0.00 |
The CMMI defines two process areas associated with requirements elicitation: Requirements Development (RD) and Requirements Management (REQM). The Measurements and Analysis process area (MA) requires measurements and quantitative objectives for RD and REQM, but nowhere does it state what those measurements are. Furthermore, in order to extract measurements and evaluate them, a process must enable or otherwise support the taking of measurements. It is especially difficult to do this during requirements development, as it is generally viewed as a writing activity that does not lend itself to quantitative measurements. This paper describes a CMMI compliant formal approach to measurement and analysis during a model-driven requirements development process. It presents a set of metrics that were used successfully on several Siemens projects, describing team dynamics, project size and staffing, how the metrics were captured and used, and lessons learned.