The PLE adoption activities provide the input to identifying the PLE adoption pattern:

• Requirements centric
• Code centric
• Systems engineering

In this activity review each of the adoption patterns from the PLE process and identify which one closely aligns to your organization. This gives guidance on which pattern to apply for product line engineering.

Requirements-centric PLE focuses on managing and reusing requirements for products. A requirement can be represented textually and with models. The tools involved with this include those which manage various formats for these specifications; this includes DOORS, DOORS Next Gen, Rhapsody, Rational Design Manager, Simulink, and other tools such as those for interface definitions. 

Code-centric PLE focuses on managing and reusing source configuration baselines for products. The focus here is managing streams of development where there is often a platform team which builds core capabilities and they are shared/reused within products and across products. The tools for this kind of PLE includes RTC.

Systems engineering PLE includes managing all of the artifacts across the lifecycle but with a focus on requirements/specifications and models. This will include requirements, designs, code, tests and their related artifacts. This includes the breadth of the tools such as DOORS, DOORS Next Gen, Rhapsody, Rational Design Manager, Rational Team Concert, and Rational Quality Manager.