Requirements Management Activities and Products Role of the PM and SE
Thoughtful analysis and management of requirements can help lay the foundation for system affordability. Configuration Management Process), can help the program to avoid or mitigate unintended or unanticipated consequences of changes through rigorous documentation of the system performance specification. Robust Requirements Management, implemented in synchronization with the program’s Configuration Management process (see SE Guidebook, Section 4.1.6. Bi-directional traceability also ensures that higher-level requirements are properly flowed to lower-level requirements and system element designs so that there are no "childless parent" higher-level requirements (i.e., each high-level requirement is ultimately being addressed by lower-level requirements and system element designs). It enables the development of an analytical understanding of any system-wide effects of changes to requirements for a given system element, updating requirements documentation with rationale and impacts for approved changes.Īt the same time, bi-directional traceability ensures that approved changes do not create any "orphaned" lower-level requirements (i.e., that all bottom-up relationships to applicable system-level requirements remain valid after the change). This bi-directional traceability is the key to effective management of system requirements. Requirements Management provides bottom-up traceability from any derived lower-level requirement up to the applicable source (system-level requirement) from which it originates. As the system design evolves to lower levels of detail, the Systems Engineer traces the high-level requirements down to the system elements through the lowest level of the design.
Through the Requirements Management process, the Systems Engineer tracks requirement changes and maintains traceability of end-user needs to the system performance specification and, ultimately, the delivered capability. Requirements Analysis Process, respectively). Stakeholder Requirements Definition Process and SE Guidebook, Section 4.2.2. The end-user needs are usually identified in operational terms at the system level during implementation of the Stakeholder Requirements Definition and Requirements Analysis processes (see Systems Engineering (SE) Guidebook, Section 4.2.1. This helps ensure delivery of a capability that meets the intended mission performance, as stipulated by the operational user. The Requirements Management process maintains a current and approved set of requirements over the entire acquisition life cycle.
0 kommentar(er)
