Metrics for requirements engineering

Abstract Today's large software-intensive systems have critical quality requirements, limited budgets, and stringent development and maintenance schedules. It is therefore necessary to be able to objectively evaluate these systems during their development to determine whether they will meet requirements, schedule, and budget, to assist risk management, and to facilitate corrective and preventive action. The discipline of software metrics has the potential for providing the objective information necessary for technical and managerial insight into, and control of, the development effort. However, the current software metrics literature does not address the need for integrated and consistent system- and software-level metrics, nor does it provide detailed descriptions of metrics for full life cycle coverage. This article is an introduction to work in progress at The Aerospace Corporation and California State University, Long Beach, in the area of metrics for requirements engineering. The first in a planned series of papers on metrics for full life cycle system and software engineering, it describes the role of metrics in an integrated approach to system and software engineering, introduces the basic components of complete metric definitions, and discusses the use of metrics in comprehensively assessing objective aspects of the requirements engineering process and its products.

[1]  Robert L. Glass,et al.  Measuring software design quality , 1990 .

[2]  John C. Kelly,et al.  An analysis of defect densities found during software inspections , 1992, J. Syst. Softw..

[3]  Chris F. Kemerer,et al.  A Metrics Suite for Object Oriented Design , 2015, IEEE Trans. Software Eng..

[4]  Herman P. Schultz Software Management Metrics , 1988 .

[5]  Julian C. Holtzman,et al.  Systems engineering of computer-based systems , 1994, Computer.

[6]  W. W. Royce,et al.  Managing the development of large software systems: concepts and techniques , 1987, ICSE '87.

[7]  Robert B. Grady,et al.  Software Metrics: Establishing a Company-Wide Program , 1987 .

[8]  Brian Henderson-Sellers,et al.  The object-oriented systems life cycle , 1990, CACM.

[9]  Barry W. Boehm,et al.  A spiral model of software development and enhancement , 1986, Computer.

[10]  Alan M. Davis,et al.  Software Requirements: Objects, Functions and States , 1993 .

[11]  G. D. Hoffman,et al.  Early introduction of software metrics , 1989, Proceedings of the IEEE National Aerospace and Electronics Conference.

[12]  Hossein Saiedian,et al.  A study of two frameworks for quality software process , 1995, SAC '95.

[13]  Robert B. Grady,et al.  Practical Software Metrics for Project Management and Process Improvement , 1992 .

[14]  Victor R. Basili,et al.  Evaluation of a software requirements document by analysis of change data , 1981, ICSE '81.

[15]  Horst Zuse,et al.  Software metrics: using measurement theory to describe the properties and scales of static software complexity metrics , 1989, SIGP.

[16]  Robert E. Park,et al.  Software Size Measurement: A Framework for Counting Source Statements , 1992 .

[17]  Steven Glaseman,et al.  Software requirements for embedded computers : a preliminary report , 1980 .

[18]  Barry W. Boehm,et al.  Software Engineering Economics , 1993, IEEE Transactions on Software Engineering.

[19]  H. D. Rombach,et al.  The Goal Question Metric Approach , 1994 .

[20]  William Wilson,et al.  Automated quality analysis of Natural Language requirement specifications , 1996 .

[21]  Sallie M. Henry,et al.  Software Structure Metrics Based on Information Flow , 1981, IEEE Transactions on Software Engineering.

[22]  David Bellin,et al.  Object-oriented metrics: an overview , 1994, CASCON.

[23]  Alan M. Davis,et al.  Identifying and measuring quality in a software requirements specification , 1993, [1993] Proceedings First International Software Metrics Symposium.

[24]  Anas N. Al-Rabadi,et al.  A comparison of modified reconstructability analysis and Ashenhurst‐Curtis decomposition of Boolean functions , 2004 .

[25]  R. R. Dumke CAME tools-lessons learned , 1996, Proceedings of the Fourth International Symposium on Assessment of Software Tools.