U.6.1 Adapt a set of reusability criteria and a classification scheme for major project deliverables.
Reusability criteria and classification schemes should not be defined independently for for each project. Organizations should establish these criteria and a classification approach for global use. Each team should then adapt the reuse conventions for the project.
U.6.2 Define guidelines for creating reusable software components (data, documents and programs) and train managers and practitioners in their application.
A distinct set of guidelines (developed from the criteria developed in Task U.6.1) should be developed. Managers and practitioners should receive training so that they will be capable of implementing the guidelines.
U.6.3 Define reuse evaluation points (REP) on the project timeline.
Reusability must be evaluated as models are created and deliverables are produced. The team must establish a mechanism for accomplishing this.
U.6.4 Define candidate software components for entry into the reuse library or candidate components for extraction from the library.
As analysis and design models are created, the project team should evaluate data and functional components (or OO classes) to determine whether an existing component is available. For new components, the team must evaluate the component against reuse criteria for potential entry into the library.
U.6.5 Define specific SQA procedures for reusable components, prior to their entry into the library.
When software components have been selected for entry into the library, the project team and an independent SQA group must assess quality rigorously. This task must be performed for all candidate reusable components.
U.6.6 Classify reusable components and enter them into the library.
Using the classification scheme, the project team must define a set of classification parameters so that database searches of the library will uncover the component.
U.6.6.1 Define component by type (i.e., data, document, program) and subtype.
U.6.6.2 Define the component application domain, functional domain and technical domain.
U.6.6.3 Define implementation characteristics.
U.6.6.4 Attach reuse guidelines.
U.6.6.5 Submit for review prior to insertion in reuse library.
U.6.7 Define specific validation procedures for reusable components, subsequent to their extraction from the library.
Although reusable components are assumed to be validated prior to entry into the library, local validation within the context of the project scope should be planned and executed for each component.
U.6.8 Product Reuse Status Report (RSR).
The Reuse Status Report indicates components that have been reused from the library and reusable components produced by the project team. The RSR is produced at the conclusion of the engineering modeling and implementation activities.
Use Browser "back" arrow or return to APM Process Design Language Description