Note: This goal of this adoption framework is to highlight the main focus areas that need to be taking in consideration when moving to a strategic reuse based approach. This guidance is not prescriptive and constitutes just an exemplar that an organization might use as a reference when planning for this kind of migration.

There are two objectives for this process:

1. Prepare your team to adopt practices using IBM solutions
2. Determine the focus for your adoption: requirements, code, or broader system engineering

This entails aligning teams and projects to define product structure and reusable components within that structure. The teams need to define the artifacts and their links necessary to deliver products. The linked artifacts require tool integrations, which may or may not exist; it also requires versioning and baseline strategies to be enforced. Conducting the adoption activities provides clarity on the main pattern for your organization. There primary patterns are:

• Requirement-centric
• Code-centric
• System engineering

As you determine the product line engineering pattern it is important to determine how the new activities map into your engineering process.

To use this adoption process effectively use the IBM Rational Team Concert work item templates generated based on the related workflows.