Generating high quality requirements
Linda H. Rosenberg · AIAA Space 2001 Conference and Exposition · 2001
Requirements development and management have always been critical to the successful implementation of software systems-engineers are unable to build what analysts can't define. It is generally accepted that the earlier in the life cycle potential risks are identified, the easier it is to eliminate or at least manage the conditions that introduce that risk. Problems that are not found until the testing phase are approximately 14 times more costly to fix than they would have been if they were found earlier in the requirements phase. The requirements specification document is the first tangible representation of the capabilities to be produced, be they system, hardware, software or operational requirements. The document also serves to establish the basis for all of the project's engineering management and assurance functions. If the quality of the requirements specification is poor, the project is at risk even before work begins.