Essentially, EIA-632 manages to explain how to apply a building block technique to the multi-layered development models associated with large-scale system developments. Each building block is a system
development process that obtains its requirements from the preceding block (or at the top-most level the end customer for the system). Given that my first target is a Requirements Management Process, the main interest for me is the diagram that illustrates how requirements are related through the building block.
Barring a few variations in the use of terms, this reflects a similar picture to that which I have evolved over the years of how requirements flow down from the initial source requirements to the requirements that specify the subsystems that comprise the system.
I have seen more than one example of a project that has had enormous difficulty with requirements management simply because there was little understanding of the transition states that apply to requirement flow-down.
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
| File | MIME type | Size (KB) | Language | Download | |
|---|---|---|---|---|---|
| Roll up for the main Attraction INCOSE.pdf | application/pdf | 234.72 KB | English | DOWNLOAD! |
Provides definitions
Cover images
Introduction
Admire the feats of balancing needed to ensure that
Systems Engineering Capability Modelling is used a tool
for process improvement rather than a hurdle for supplier
selection.
Thrill to the new opportunities for applying UML to
Systems Engineering – all performed without the aid of a
safety net.