PLANNING THE TRANSFER PHASE

Plans of TR phase activities must be drawn up in the DD phase. Generation of TR phase plans is discussed in Chapter 7. These plans cover project management, configuration management, verification and validation and quality assurance. Output? are the:

• Software Project Management Plan for the TR phase (SPMP/TR);

• Software Configuration Management Plan for the TR phase (SCMP/TR):

• Software Quality Assurance Plan for the TR phase (SQAP/TR).

2.8 THE DETAILED DESIGN PHASE REVIEW

The development team should hold walkthroughs and internal reviews of a product before its formal review. After production, the DD Review (DD/R) must consider the results of the verification activities and decide whether to transfer the software (DD11). This should be a

ESAPSS-05-05 Issue 1 (May 1992) 23 THE DETAILED DESIGN AND PRODUCTION PHASE

technical review. The recommended procedure is described in ESA PSS-05-10, which is based closely on the IEEE standard for Technical Reviews [Ref. 4].

Normally, only the code, DDD, SUM and SWP/AT undergo the full technical review procedure involving users, developers, management and quality assurance staff. The Software Project Management Plan (SPMP/TR), Software Configuration Management Plan (SCMP/TR), and Software Quality Assurance Plan (SQAP/TR) are usually reviewed by management and quality assurance staff only.

In summary, the objective of the DD/R is to verify that:

• the DDD describes the detailed design clearly, completely and in sufficient detail to enable maintenance and development of the software by qualified software engineers not involved in the project;

• the modules have been coded according to the DDD;

• the modules have been verified according to the unit test specifications in the SWP/UT:

• the major components have been integrated according to the ADD;

• the major components have been verified according to the integration test specifications in the SWP/IT:

• the software has been verified against the SRD according to the system test specifications in the SWP/ST;

• the SUM explains what the software does and instructs the users how to operate the software correctly;

• the SWP/AT specifies the test designs, test cases and test procedures so that all the user requirements can be validated.

The DD/R begins when the DDD, SUM, and SWP, including the test results, are distributed to participants for review. A problem with a document is described in a 'Review Item Discrepancy' (RID) form. A problem with code is described in a Software Problem Report (SPR). Review meetings are then held that have the documents, RIDs and SPRs as input. A review meeting should discuss all the RIDs and SPRs and decide an action for each. The review meeting may also discuss possible solutions to the problems raised by them. The output of the meeting includes the processed RIDs, SPRs and Software Change Requests (SCR).

24 ESAPSS-05-05 Issue 1 (May 1992) THE DETAILED DESIGN AND PRODUCTION PHASE

The DD/R terminates when a disposition has been agreed for all the RIDs. Each DD/R must decide whether another review cycle is necessary, or whether the TR phase can begin.

ESA PSS-05-05 Issue 1 (May 1992) 25 METHODS FOR DETAILED DESIGN AND PRODUCTION

Date: 2016-01-03; view: 811