|
Verification methods (design, analysis, inspection and/or test), verification level (whether the concerned requirement is verified at system or subsystem level), milestones (at which stage in the programme the requirement is verified) and constraints, when applicable, are discussed. Particular emphasis is put on addressing how the key system requirements, i.e., the ones with a larger impact on the science return, are planned to be verified. Also, special attention is given to describe the model approach in place to help in the system-level verification activity. Finally, some conclusions and lessons learned extracted so far from the system requirements verification activity are summarized. |
|
|
