4,000
edits
Changes
Jump to navigation
Jump to search
mLine 42:
Line 42: − The PM should keep leadership and all stakeholders informed of cost, schedule, and performance impacts associated with requirement changes and requirements growth. + − + − Through the Requirements Management process, the Systems Engineer tracks requirements changes and maintains traceability of end-user needs to the system performance specification and, ultimately, the delivered capability. + − + − 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. + − + − The Systems Engineer also establishes and maintains a Requirements Traceability Matrix (RTM) that captures all requirements in the system performance specification, their decomposition/ derivation and allocation history, and rationale for all entries and changes.+
→Process Responsibilities
===Process Responsibilities===
===Process Responsibilities===
*tracks requirements changes and maintains traceability of the system performance specification and delivered capability
*traces the high-level requirements down to the system elements through the lowest level of the design as the system design evolves to lower levels of detail
*establishes and maintains a Requirements Traceability Matrix (RTM)
*#capturing all requirements in the system performance specification
*#documenting their decomposition/derivation and allocation history
*#document rationale for all entries and changes
*work with PM to track cost, schedule, and performance impacts associated with requirement changes and/or growth
===Risk Management===
===Risk Management===