1-4 | Scope, terms, and the system engineering discipline and process | 0 |
5.1 | Produce and maintain a system engineering plan | 0 |
5.2.1 | Analyse customer requirements and derive controlled lower-level requirements | 0 |
5.2.2 | Keep forward and backward traceability of every requirement | 0 |
5.2.3.1 | Establish consistent technical requirements specifications and a specification tree | 0 |
5.2.3.2 | Consolidate incomplete, ambiguous or contradictory requirements at the start of each phase | 0 |
5.2.3.3 | Identify the requirements that drive system risk | 0 |
5.2.3.4 | Assign verification methods to every requirement and record them in the verification matrix | 0 |
5.2.3.5 | Allocate system requirements and their verification methods to lower levels | 0 |
5.2.3.6 | Verify that requirements are consistent and non-redundant across levels | 0 |
5.2.3.7 | Validate requirements against the expressed needs with the customer in phase 0 | 0 |
5.2.3.8 | Maintain the requirements through to the end of phase F | 0 |
5.2.3.9 | Define the documents that form the requirements baseline | 0 |
5.3.1 | Perform mission, functional, physical, performance and cost analyses and document them | 0 |
5.3.2 | Establish environments, qualification and acceptance criteria, factors and margins | 0 |
5.3.3 | Conduct trade-off analyses and report them | 0 |
5.3.4 | Define, validate and maintain analysis methods, tools and models | 0 |
5.4.1.1 | Establish a whole-life system design from architecture, allocation and technology | 0 |
5.4.1.2 | Define, apportion and control technical budgets under the margin policy | 0 |
5.4.1.3 | Define, validate and maintain design methods, tools and models with an agreed coordinate system | 0 |
5.4.1.4 | Maintain the design definition file, the design justification file and the user manual | 0 |
5.4.2.1 | Define the complete configuration at every level and document it | 0 |
5.4.2.2 | Establish configuration baselines at defined milestones | 0 |
5.4.2.3 | Define and document the hierarchy and assembly sequence | 0 |
5.5 | Verify the complete product on its defined architecture per ECSS-E-ST-10-02 | 0 |
5.6.1 | Define, plan and manage the integrated technical effort | 0 |
5.6.2 | Keep the system engineering plan aligned with the project schedule | 0 |
5.6.3 | Define the engineering data repository and electronic exchange interfaces | 0 |
5.6.4 | Control external and internal interfaces through specifications and interface control documents | 0 |
5.6.5 | Define the coordinate systems and the units system | 0 |
5.6.6 | Control the technical budgets and define the margin policy | 0 |
5.6.7 | Identify, assess and plan candidate technologies | 0 |
5.6.8 | Contribute engineering data and controls to risk management | 0 |
5.6.9 | Assess every change proposal and nonconformance technically and control agreed actions | 0 |
6.1 | Overview of the phase model | 0 |
6.2 | Plan and monitor system engineering activities by project phase and identify critical elements | 0 |
6.3 | Phase 0: support need identification and propose system concepts | 0 |
6.4 | Phase A: finalise the needs and propose solutions with their risks | 0 |
6.5 | Phase B: establish the preliminary definition and demonstrate it meets the requirements | 0 |
6.6 | Phase C: establish the detailed definition and demonstrate the capability to meet the specification | 0 |
6.7 | Phase D: complete qualification and acceptance and prepare for operations | 0 |
6.8 | Phase E: support the launch campaign, operations and anomaly resolution | 0 |
6.9 | Phase F: support disposal and the Mission Close-out Review | 0 |
A | Document requirements definitions | 0 |