Defect evolution in a product line environment

Authors:
Marvin V. Zelkowitz;Ioana Rus
Affiliations:
Fraunhofer Center for Experimental Software Engineering, Maryland 4321 Hartwick Road, Suite 500, College Park, MD 20740, USA and Department of Computer Science, University of Maryland, College Par ...;Fraunhofer Center for Experimental Software Engineering, Maryland 4321 Hartwick Road, Suite 500, College Park, MD 20740, USA
Venue:
Journal of Systems and Software
Year:
2004

Citing 7
Cited 0

Measuring and Evaluating Maintenance Process Using Reliability, Risk, and Test Metrics

IEEE Transactions on Software Engineering
Understanding IV & V in a safety critical and complex evolutionary environment: the NASA space shuttle program

ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
An Assessment of Space Shuttle Flight Software Development Processes

An Assessment of Space Shuttle Flight Software Development Processes
How To Evaluate Legacy System Maintenance

IEEE Software
Statistical Process Control: Analyzing a Space Shuttle Onboard Software Process

IEEE Software
The Role of Independent Verification and Validation in Maintaining a Safety Critical Evolutionary Software in a Complex Environment: The NASA Space Shuttle Program

ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
Adding Value to the Software Development Process: A Study in Independent Verification and Validation

Adding Value to the Software Development Process: A Study in Independent Verification and Validation

Quantified Score

Hi-index	0.00

Visualization

Abstract

One mechanism used for monitoring the development of the Space Shuttle flight control software, in order to minimize any risks to the missions, is the independent verification and validation (IV&V) process. Using data provided by both the Shuttle software developer and the IV&V contractor, in this paper we describe the overall IV&V process as used on the Space Shuttle program and provide an analysis of the use of metrics to document and control this process over multiple releases of this software. Our findings reaffirm the value of IV&V, show the impact of IV&V on multiple releases of a large complex software system, and indicate that some of the traditional measures of defect detection and repair are not applicable in a multiple-release environment such as this one.