Home / Defined terms / System Definition and Realisation
System Definition and Realisation · processSystem Definition and Realisation
The process area that takes the acquirer's needs through requirements, architecture, realisation, integration, verification and delivery.
What it means here
The process area that takes the acquirer's needs through requirements, architecture, realisation, integration, verification and delivery.
Most of the evidence in a systems engineering file sits in this process.
How to use it
The term appears in the register wherever the distinction changes what a person must do. A policy that uses the word without the distinction is a policy that cannot be tested. The practice pages link back to this definition so the reader can check the meaning before signing a row.
Use it once in the scope note, once in the role table and once in the evidence index. If the three uses disagree, the file is not ready. The definition is narrow on purpose: a broad definition lets two teams believe they agree when they do not.
The practices that depend on it
Every practice in the register is written to be testable, which means the terms in it have to be concrete. Start with the register, then read the practice that carries the term in its statement. If the term is still unclear after that, the row is not ready to sign.