Premium
A CONCURRENT GOVERNMENT/CONTRACTOR APPROACH FOR DEVELOPING DESIGN CONSTRAINTS
Author(s) -
Shimizu Choichi,
Goerke Leah
Publication year - 1993
Publication title -
incose international symposium
Language(s) - English
Resource type - Journals
ISSN - 2334-5837
DOI - 10.1002/j.2334-5837.1993.tb01625.x
Subject(s) - engineering design process , process (computing) , concurrent engineering , systems design , computer science , system requirements specification , requirements management , systems engineering , non functional requirement , functional requirement , requirements analysis , identification (biology) , reliability (semiconductor) , engineering , software engineering , operations management , software development , software , mechanical engineering , software construction , power (physics) , physics , quantum mechanics , botany , scheduling (production processes) , biology , programming language , operating system
Specifications which define the requirements of a system, sub system, or end items consist of both performance requirements and design constraints. Performance requirements state what a system or item must do and how well it must do it. Design constraints state boundary conditions within which the system or item must perform (i.e., environments, reliability, physical characteristics). Design constraints typically form approximately 80% of the requirements in a specification. Early definition and proper allocation of both the performance requirements and design constraints are essential to the successful development of the end item. At the Ballistic Missile Organization, the System Requirements Analysis (SRA) process has been used to synthesize system design and develop specifications from design constraints and performance requirements. This paper concentrates on the SRA process peculiar to design constraints. A team approach was used with both government and contractor technical experts. The entire process will be discussed from the initial identification of design constraints to the incorporation of these constraints into the specifications as authenticated requirements. This process is consistent with the latest system engineering standards being implemented.