Premium
Capturing and Taming Derived Requirements
Author(s) -
Scheurer Robert P.,
Volz Michael E.
Publication year - 1994
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1994.tb01686.x
Subject(s) - requirements management , requirements analysis , computer science , requirements elicitation , non functional requirement , business requirements , requirement , functional requirement , system requirements , process (computing) , requirements engineering , product (mathematics) , risk analysis (engineering) , systems engineering , process management , software engineering , engineering , business , business process , operations management , work in process , software , mathematics , operating system , software construction , software system , programming language , geometry
Systems engineers are concerned with identifying, allocating, and managing their customer requirements to appropriate design teams. However, as anyone involved with the design process can testify, contractual requirements are only one piece of the requirements management puzzle. Designs as well as requirements evolve and are iterated to very low levels of detail, with each succeeding level offering more complexity and additional requirements. Unless these added requirements are well‐understood and documented, costly mistakes or omissions can be introduced into the completed product. As the reader will see, system requirement definitions can and do go far beyond the initial mandates imposed by the customer.