21.11.2014 Views

TSPi Support Tools document (pdf) - Carnegie Mellon University

TSPi Support Tools document (pdf) - Carnegie Mellon University

TSPi Support Tools document (pdf) - Carnegie Mellon University

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

9.4. The Configuration Status Report: CSR<br />

The CSR form is first used to report configuration status after the SRS <strong>document</strong> has been<br />

developed, inspected, and baselined. This is done in the requirements phase. The SRS will be the<br />

first product to be baselined. Until it is, there is nothing to report on the CSR form.<br />

Things to Check: CSR Form<br />

The principal thing to check is that the team has baselined the SRS <strong>document</strong> and that the support<br />

manager has recorded the number of text pages. Thereafter, check each week to make sure that all<br />

appropriate new items were added when they were completed and inspected. This would be the<br />

SDS at the end of the design phase and all the source code at the end of implementation. In<br />

addition, make sure that all changes to baselined products are approved with a CCR, that the<br />

proper INS forms are attached to the CCR, and that all changes are reported on the CSR.<br />

Interpreting the Data: CSR Form<br />

For the modest-sized <strong>TSPi</strong> projects, you will not generally be able to draw much useful<br />

information from the CSR reports. With larger projects, the CSR data can indicate when the<br />

requirements have settled down and when a product is stabilizing in integration or system test.<br />

These data can also show code growth during implementation as well as the decline of change<br />

activity as testing nears completion. These analyses, however, require trend data over an extended<br />

period. With <strong>TSPi</strong>, there is not enough time to get trend data. You can look at the volume of test<br />

defects and compare the results among teams or development cycles, but because the test phase<br />

will takes one week or less, there will be not be weekly trend data.<br />

Common Reporting Mistakes: CSR Form<br />

The principal mistakes are that teams either do not baseline all their products or they do not<br />

properly track their configuration and change activity and status.<br />

General Comments: CSR Form<br />

Again, for the small <strong>TSPi</strong> products, the software configuration management process need not be<br />

overly formal. The students should recognize that the CCR process is a mechanism to ensure<br />

proper consideration of every change. Teams need to learn to manage all their baseline changes,<br />

not only to control the projects but also to maintain control of quality from the beginning of the<br />

job.<br />

http://www.awl.com/cseng/titles/0-201-47719-X/onlinesupplements/9-4.htm (1 of 2) [11/5/1999 10:31:13 AM]

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!