Requirements, Testing and Metrics (1998)
| Venue: | In 15th Annual Pacific Northwest Software Quality Conference |
| Citations: | 7 - 0 self |
BibTeX
@INPROCEEDINGS{Rosenberg98requirements,testing,
author = {Linda H. Rosenberg and Phd Theodore and F. Hammer and Lenore L. Huffman},
title = {Requirements, Testing and Metrics},
booktitle = {In 15th Annual Pacific Northwest Software Quality Conference},
year = {1998}
}
Share
 |
 |
 |
 |
||
OpenURL
Abstract
The criticality of correct, complete, testable requirements is a fundamental tenet of software engineering. Also critical is complete requirements based testing of the final product. Modern tools for managing requirements allow new metrics to be used in support of both of these critical processes. Using these tools, potential problems with the quality of the requirements and the test plan can be identified early in the life cycle. Some of these quality factors include: ambiguous or incomplete requirements, poorly designed requirements databases, excessive or insufficient test cases, and incomplete linkage of tests to requirements. This paper discusses how metrics can be used to evaluate the quality of the requirements and test to avoid problems later. Requirements management and requirements based testing have always been critical in the implementation of high quality software systems. Recently, automated tools have become available to support requirements management. At NASA’s Goddard Space Flight Center (GSFC), automated requirements management tools are being used on several large projects. The use of these tools opens the door to innovative uses of metrics in characterizing test plan quality and assessing overall testing risks. In support of these projects, the Software Assurance Technology Center (SATC) is working to develop and apply a metrics program that utilizes the information now available through the application of requirements management tools. Metrics based on this information provides real-time insight into the testing of requirements and these metrics assist the Project Quality Office in its testing oversight role. This paper discusses three facets of the SATC’s efforts to evaluate the quality of the requirements and test plan early in the life cycle, thus preventing costly errors and time delays later. Data from NASA projects are used to support and clarify the concepts discussed. 1.
Keyphrases
requirement management tool requirement management test plan life cycle costly error final product time delay software assurance technology center incomplete linkage goddard space flight center potential problem incomplete requirement oversight role metric program high quality software system new metric test plan quality real-time insight satc effort requirement database testable requirement nasa project several large project project quality office modern tool quality factor innovative us insufficient test case fundamental tenet software engineering critical process complete requirement overall testing risk
