Objectives of the Document. Figure 1-1 Relationship of development documents during project lifecycle These Demonstration Procedures (DP) fit into the project development lifecycle that is shown in Figure 1-1. The figure shows the interrelationship of project deliverables as the schedule advances throughout the project. The different phases of the project are shown on the right: System Requirements, Preliminary and Detailed Design, Implementation/Integration and Demonstration. For each phase, a set of documents is produced and delivered to the EC and PSA at a milestone that signifies the end of the corresponding phase. Once the milestone has been completed successfully, a new set of documents are derived from the previous ones. For example the System Requirements Document (SRD) gives rise to a test/demonstration specification and PDD; the PDD is used to create the Detailed Design (DD) documents and Procedures for demonstration. These latter documents then enable the production of the documents that drive the common core integration and testing of the software and hardware modules. Finally, a test/demonstration report that summarises the tests that have been performed with the demonstrators is delivered, thus validating the development process shown above. This DP is dedicated to the demonstrator of In Space Assembly Simulator of PULSAR.
Objectives of the Document. Figure 1-1 Relationship of development documents during project lifecycle These Detailed Design Documents (DDD) fit into the project development lifecycle shown in Figure 1-1. The figure shows the interrelationship of project deliverables as the schedule advances throughout the project. The different phases of the project are shown on the right: System Requirements, Preliminary and Detailed Design, Implementation/Integration and Demonstration. For each phase, a set of documents is produced and delivered to the EC and PSA at a milestone that signifies the end of the corresponding phase. Once the milestone has been successfully completed, a new set of documents are derived from the previous ones. For example the System Requirements Document (SRD) gives rise to a test/demonstration specification and PDD; the PDD is used to create the Detailed Design (DD) documents and Procedures for demonstration. These latter documents then enable the production of the documents that drive the common core integration and testing of the software and hardware modules. Finally, a test/demonstration report that summarizes the tests that have been performed with the demonstrators is delivered, thus validating the development process shown above. The present document, Test and Demonstration Procedures, is dedicated to the demonstrator of the Precision Assembly of Mirror Tiles (dPAMT) within PULSAR. This document is complemented with deliverable D8.1 – dPAMT Detailed Design Document. The current Test and Demonstration Procedures Document has three main sections: • Demonstration scenarios for dPAMT • Specific verification of requirements - SMT • Generic test plan
Objectives of the Document. As described in the Preliminary Design Document [RD-2], limitations of the design, testing facilities, and equipment may have an effect on the specification of the demonstration, requiring several distinct demonstrations for one demonstrator. The present document thus aims to provide a clear identification of the demonstration scenarios to be used as a reference document during the next phase of the project. For each demonstrator and for each scenario, the following information is provided: Objective of the scenario: what is to be demonstrated by this scenario? A description of the scenario: The detailed demonstration steps presented here are also illustrated in the Preliminary Design Document [RD-2], as the scenarios were an important input to the design process of the demonstrators. The system requirement(s) addressed by this scenario. Some system requirement may not be addressed by a scenario in which case they are listed in Section 5. For each of these requirement, a rationale is provided to justify why such a requirement is not addressed by any scenario. At this stage of the project, high-level demonstration scenarios meant to address all system-level requirements are defined. In the detailed design phase of the project, further unit tests and demonstrations will be specified for each demonstrator and software components in their respective design deliverables.
Objectives of the Document. This document details all the data that have been collected during the executions of the tests and demonstrations. Each data will be accessible under request to the project coordinator.
