Info

2,135

Formal SAT testing was scrutinized by the government and required fairly long lead times for review. The government required overly detailed test procedures for numerous design details that should not have been treated as requirements. In the heat of development, the SAT procedures were rarely available 30 to 60 days before turnover, as required by the contract for any requirements verification test. The formal SAT process was one of the main reasons that the turnover reviews were consistently completed later than planned.

Test progress at month 41, for example:

523 of 589 SAT verifications

1,003 of 1,003 EST verifications

0 of 543 EST5/FQT verifications

1,526 of 2,135 requirements verified (72% complete)

Test progress at month 41, for example:

523 of 589 SAT verifications

1,003 of 1,003 EST verifications

0 of 543 EST5/FQT verifications

1,526 of 2,135 requirements verified (72% complete)

Contract Month Figure D-ll. Common Subsystem test progress

D.7.3 Stability

Figure D-12 illustrates the overall rate of configuration baseline changes. It shows the cumulative number of SLOC that were broken (checked out of the baseline for rework because of an identified defect, enhancement, or other change) and the number of SLOC repaired (checked back into the baseline with fixes, enhancements, or other changes). Breakage rates that diverged from repair rates resulted in management attention, reprioritization of resources, and corrective actions taken to ensure that the test organization (driving the breakage) and development organization (driving the repair) remained in relative equilibrium. Overall, the situation shown depicts a very healthy project.

Figure D-13 identifies the total breakage as a ratio of the entire software subsystem. This metric identifies the total scrap generated by the Common Subsystem software development process as about 25% of the whole product. Industry averages for software scrap run in the 40% to 60% range. The initial configuration management baseline was established around the time of PDR, at month 14. There were 1,600 discrete changes processed against configuration baselines thereafter.

Contract Month

Figure D-12. Common Subsystem stability

Contract Month

Figure D-12. Common Subsystem stability

Closed rework Currently open rework o o

About 25% of all SLOC were scrapped and reworked after their initial baseline.

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