Figure D-14. Common Subsystem adaptability

D.7.6 Maturity

CCPDS-R had a specific reliability requirement, for which the software had a specific allocation. The independent test team constructed an after-hours, automated test suite that exercised the evolving software baselines with randomized message scenarios. This strategy resulted in extensive test time being logged under realistic conditions from which a credible software MTBF could be substantiated. The reliability-critical components, forced by the iteration plan into the earliest baselines, were subjected to the most reliability stress testing. This plan ensured early insight into maturity and software reliability issues. Figure D-15 illustrates the results.

With modern distributed architectures, this sort of statistical testing is both necessary for ensuring maximum coverage and useful for uncovering significant issues of races, deadlocks, resource overruns, memory leakage, and other Heisen-bugs. Executing randomized and accelerated scenarios for long periods of time (running all night or over a long weekend) enables early insight into overall system resource integrity.

D.7.7 Cost/Effort Expenditures by Activity

Table D-8 provides the overall cost breakdown for the CCPDS-R Common Subsystem. These data were extracted from the final WBS cost collection runs and were structured as recommended in Section 10.1. The next-level elements are described in Table D-9.


o si cd











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