|
|
 |
 |
Technical missions | Development Cycles: The DPAC has adopted the use of development cycles as a fundamental element of its SW development strategy. During each development cycle requirements are specified, code developed, delivered and tested. This strategy mirrors the MDB versioning that will take place during satellite operations, but more practically allows working prototypes of the SW modules to be developed early, allowing full testing of the interfaces to take place early in the project. In the first cycles these prototypes will be simple in content, with increasing sophistication in later cycles. Below are the end-dates and names of each cycle, the latter being the names of the ten highest terrestrial mountain peaks, in ascending order. We are in Cycle 12. | Cycle |  | Name | | End Date | | DPAC Milestones | | 1 | | Annapurna | | 11/06 | | | | | 2 | | Nanga Parbat | | 05/07 | | | | | 3 | | Manaslu | | 11/07 | | System Requirements Review | | | 4 | | Dhaulagiri | | 05/08 | | - initial MDB ICD defined
- all SW Design Documents submitted
| | | 5 | | Cho Oyu | | 11/08 | | - all DPC Development Plans submitted
- GTS tested, validated and installed at all DPCs
- MDB ICD under configuration control
- CU2 GOG system consistent with MDB ICD
- AGIS handles 10 million Primary objects
- all SW Test Plans submitted
- DPAC Operations Plan submitted
| | | 6 | | Makalu | | 05/09 | | - DPAC E2E Test Plan submitted
- Critical Design Review
- radiation recovery demonstrated in IDT/FL
- all simulated intermediate data from CU2 channeled through MDB
| | | 7 | | Lhotse | | 11/09 | | - CU2 GASS system consistent with final telemetry ICD
- MDB handles at 100 million objects
- data processing results from other DPCs ingested into MDB
| | | 8 | | Kangchenjunga | | 05/10 | | - MDB Ingestor/Extractor automated
- DPC's launch configuration HW procured, installed and under configuration control
- AGIS handles 50 million Primary sources
- all launch and mission critical SW systems delivered and integrated at ESAC
| | | 9 | | K2 | | 11/10 | | - final testing of IDT, FL, POS, AGIS, CU5 and CU6 systems
- payload monitoring and oparation procedures submitted
- perform regular MDB mission cycle
| | | 10 | | Everest | | 05/11 | | - final testing of IDU, AVU, CU4, CU7 and CU8 systems
- MDB handles 1000 million objects
- Implementation/Acceptance Review
| | |
|
|
|
