1. 13 April 2004 Experiences from Architectural Evolution Josef Nedstam Even-André Karlsson

2. 13 April 2004/132

3. 13 April 2004/133 Business goals and architectural goals Objective of SPL: Jan Bosch: Exploiting commonality Charles Krueger: Optimize SE effectiveness/efficiency by capitalizing on the commonality and managing the variation within similar systems BUT! Business objectives/strategies: Low costs Market share Differentiation 1st mover advantage...

4. 13 April 2004/134 Architectural Maturity Jan Bosch – context of SPLs – exploiting commonality Independent products – none Standardized infrastructure – common generic commercial components: OS, DB, GUI Platform – internal domain- specific components used in all products SPL – covering more than what is common to all products Config product base – all products share all code

5. 13 April 2004/135 The study Workgroup in ”platforms and product lines” www.SPIN-Syd.org Workshops Seminars Interviews And companies from previous studies, plus one from here

6. 13 April 2004/136 Observed states Apart from Bosch’s Internal platform Platform as product Consecutive releases from stable architecture Configurable product base (unmanaged) Consultants

7. 13 April 2004/137 Observed transitions: Product Lifecycle Consecutive releases Need for new product generation Jenga® is a registered trademark of Pokonobe Associates

8. 13 April 2004/138 Observed transitions: Platform Balance How to maintain a platform? Treat as proper product Still problems: competition, high risk

9. 13 April 2004/139 Observed transitions: Packaging knowledge Consultants want to package knowledge in product (and vice versa) As independent product – then platform, or directly as platform

10. 13 April 2004/1310 Observed transitions: Not based on architecture Config product base Multiple versions based on CM SPL based on CM instead of architecture

11. 13 April 2004/1311 Observed transitions: How to go back? Abandoned plan to differentiate

12. 13 April 2004/1312 Further work Maintaining an SPL? Balancing resources, funding and scheduling between common and specific components Solutions Hard work Split up No dedicated resources Trainees Proper RE for common resources

13. 13 April 2004/1313 Further work Clarify definitions, classifications in the framework Is it possible to build a theory for what to do when? The business goal should indicate the architectural strategy /EDSER-6