The Consortium Requirements Engineering Method Version 01.00.00
Abstract
The Consortium Requirements Project was created to address the key member company problem that: Requirements are incomplete, misunderstood, poorly defined, and change in ways that are difficult to manage. Work in 1990 determined that these problems could be substantially addressed by providing improved methods and tools targeted to the needs of line projects. The first goal of the project was to understand, in detail, what problems line projects have with requirements and where current methods or practices are deficient. This produced a detailed set of requirements for methods and tools supporting the requirements process. The second goal of the project was to develop a method and supporting tool that satisfied these member company requirements. This work initially focused on software (as opposed to system) requirements. Subsequent work will seek to validate the method through pilot projects in member companies. Validated products will be transferred to line projects through detailed guidebooks, examples, and training.
Document Details
- Document Type
- Technical Report
- Publication Date
- Sep 01, 1991
- Accession Number
- ADA262261
Entities
People
- David D. Smith
- James Kirby Jr.
- John Brackett
- Paul T. Ward
- Skip Osborne
- Steven Wartik
- Stuart Faulk