Build 1 and PDR Demo

Figure D-4. Overview of the CCPDS-R macroprocess, milestones, and schedule

The overall CCPDS-R software process had a well-defined macroprocess similar to the life-cycle phases described in Figure 5-1. Each major milestone was accompanied by a major demonstration of capability and typically included contributions from several of the on-going builds. It would be more accurate to call the design process used on the project incremental rather than iterative, although, as with any large-scale system, it was clearly both.

D.5.1 Risk Management: Build Content

Planning the content and schedule of the Common Subsystem builds resulted in a useful and accurate representation of the overall risk management plan. The importance of a sound build plan was well understood by the management team, and it was carefully thought out early in the inception phase. The management team set the expectation for reallocating build content as the life cycle progressed and more-accurate assessments of complexity, risk, personnel, and engineering trade-offs were achieved. This evolutionary plan was important, and there were several adjustments in build content and schedule as early conjecture evolved into objective fact.

Figure D-5 illustrates the detailed schedule and CSCI content of the Common Subsystem. The details of its build content are as follows:

• Build 0. This build comprised the foundation components necessary to build a software architecture skeleton. The intertask/interprocess communications, generic task and process executives, and common error reporting components were included. This build was also the conclusion of the research and development project executed in parallel with the CD (inception) phase. These NAS components were the cornerstone of the architectural framework and were built to be reusable across all three CCPDS-R subsystems. They represented very complex, high-risk components with stringent performance, reliability, and reusability demands.

• Build 1. This build was essentially the "architecture." It included a complete set of instantiated tasks (300), processes (70), interconnections (1,000), states, and state transitions for the structural solution of the CCPDS-R software architecture. To achieve a cycling architecture, this build also added all the NAS components for initialization, state management (reconfiguration), and instrumentation. A trivial user interface and the capability to inject test scenarios into the architecture were added to support the initial demonstration. Upon completion of build 1, only a few critical use cases were demonstrable: initializing the architecture, injecting


Was this article helpful?

0 0
Project Management Made Easy

Project Management Made Easy

What you need to know about… Project Management Made Easy! Project management consists of more than just a large building project and can encompass small projects as well. No matter what the size of your project, you need to have some sort of project management. How you manage your project has everything to do with its outcome.

Get My Free Ebook

Post a comment