Common use of On-Board Flight Software Design Reviews Clause in Contracts

On-Board Flight Software Design Reviews. The Software Requirements Review (SRR) shall verify all software requirements are fully defined in the Flight Software Requirements document. The Requirements Document shall also define all performance, interface, operational, resource and verification requirements for the flight software. The SRR is the first part of the Flight Software PDR. An Architectural Design Review (ADR) shall be conducted to allow the contractor to satisfy Inmarsat formally of the Architectural Design concept. The review shall also verify that the Flight Software Architectural Design Document (ADD) is complete and correct. The ADD shall define the major components of the software and all interfaces between them. The ADD shall also define all external interfaces. A preliminary resource analysis (worst case timing, memory utilisation) shall be presented at ADR. A prerequisite to this review is a successfully completed Software Requirement Review. The Architectural Design Review is the second part of the Flight Software PDR. The Detailed Design Review (DDR) shall be conducted to allow the contractor to satisfy Inmarsat formally of the Flight Software Detailed Design. The review shall also verify that the Detailed Design Document (DDD) is complete and correct. The DDD shall describe the software to the bottom-level components. All interfaces between components as well as external interfaces are to be completely defined. Software components shall be described in detail, using Program Design Language or equivalent. The DDD shall include a matrix tracing all requirements in the Software Requirements Document to the Detailed Design implementation. Informal design walkthroughs prior to the review may be a useful way to facilitate an effective DDR. An updated resource analysis shall be presented at the Detailed Design Review. The Software Requirement Document and the Architectural Design Document shall be updated prior to the DDR to reflect any changes since ADR. The Detailed Design Review is equivalent to the Flight Software CDR. The software design must be mature at the time of Detailed Design Review and no software design changes are to be expected. Should any unforeseen changes occur after the Detailed Design Review, additional reviews addressing these changes have to be held prior to the Software Test Readiness Review. Formally these reviews will be part of the Detailed Design Review and the same design review and documentation requirements apply. The Detailed Design Document shall be updated to reflect all changes to the flight software. All flight software documentation updates must be completed prior to the Software Test Readiness Review. The actual resource utilisation is to be presented at Software Test Readiness Review. A matrix shall also be presented tracing how individual requirements in the Software Requirement Document are verified in specific Flight Software acceptance tests.