1. Experiences from the Architectural Change Process Josef Nedstam Even-André Karlsson Martin Höst Dept of Telecom, Lund University, Sweden www.telecom.lth.se/Personal/josefn/lic

2. The Product Lifecycle Market Penetration Time Releases Introduction Growth Maturity Decline

3. Architecture Work Changes over the Product Lifecycle Time Releases Establish Architecture Use Architecture New Architecture Market Penetration

4. Process Improvement vs Process Change Time Releases Project oriented Line oriented Next product generation – New process Market Penetration

5. Research Question Requirements -> Functions -> Modules: Fairly well understood Problem -> Technically optimal architecture solution: Fairly well understood Existing system -> Changing Driving Requirements -> Architecture Changes? F1 Fn M1 Mn ReqDesignImplIntegrationSys Test ?

6. Method Round 1: General interviews ”Hypothesis”: There’s a process Analysis: Does the process apply? 3 Companies Round 2: Specific interviews 7 Cases

7. Round 1: Interviews 1-2 Architects at 3 companies How are architectural changes decided? Identifying and discussing current architecture changes

8. Round 1: Interviews 1-2 Architects at 3 companies How are architectural changes decided? Identifying and discussing current architecture changes

9. Round 1: Interviews 1-2 Architects at 3 companies How are architectural changes decided? Identifying and discussing current architecture changes

10. A Generic Architecture Change Process 1.A need emerges 2.Initial decision preparation –Document background –Identify stakeholders/decision makers 3.Decision: Go/no-go 4.Decision preparation –Analyze technical alternatives –Analyze process and organization impact –Return on investment 5.Decision: Rollout 6.Rollout 4 2 3 5 6 1

11. Round 2: Interviews Architects involved in the 7 changes What was the architecture change? Why was the architectural change needed? Who initiated it? How was the associated decision made?

12. Round 2: Interviews Architects involved in the 7 changes What was the architecture change? Why was the architectural change needed? Who initiated it? How was the associated decision made?

13. Round 2: Interviews Architects involved in the 7 changes What was the architecture change? Why was the architectural change needed? Who initiated it? How was the associated decision made?

14. Round 2: Interviews Architects involved in the 7 changes What was the architecture change? Why was the architectural change needed? Who initiated it? How was the associated decision made?

15. Round 2: Interviews Architects involved in the 7 changes What was the architecture change? Why was the architectural change needed? Who initiated it? How was the associated decision made?

16. The Changes Company A: Control systems 1.Protocol Framework 2.Real-Time Operating System Company B: Platforms for consumer electronics 3.Data Router 4.HAL Split 5.Include-file Reorganization Company C: Development tools 6.Communication Mechanism 7.Editor Framework

17. 4 2 3 5 6 1 The Changes ChgDriverSource 1Distribute development Corporate, mergers, TtM 2Cut nbr of OSesCorporate, costs 3Save memoryArchitects, HW costs 4Simplify HW changesDevelopers, TtM 5Restore tool supportAll, tool failure 6Increase nbr of editorsArchitects, integration 7Reuse editor elementsArchitects, distribution, TtM Protocol Framework: RTOS switch: Data Router: HAL Split: Include-file reorganization: Communication mechanism: Editor Framework:

18. 4 2 3 5 6 1 1: A Need Emerges Initiators: All Levels Technical implications from organizational changes/business decisions come as a surprise More knowledge needed regarding impact of decisions People should be encouraged to start analyzing architecture changes

19. 4 2 3 5 6 1 2: Initial Decision Preparation Low cost step – hopefully possible for anyone to initiate Background, stakeholders, decision-makers, impact Will change be accepted?

20. 4 2 3 5 6 1 3: Decision Point: Go/No-Go First decision to commit resources Initiator: Convince Decision maker: Prioritize resources Who can commit resources? Tie preparations to people affected

21. 4 2 3 5 6 1 4: Decision Preparation Technical alternatives Process/organizational impact Return on investment Performed as Implementation Proposal Company: Make right decision Initiator: Show need for change

22. 4 2 3 5 6 1 5: Decision Point: Rollout As Tollgate 2 But who will implement changes? (Technical / process / organziational) Tradeoff: Amount of architectural change vs amount of new feature content When will rollout happen?

23. 4 2 3 5 6 1 6: Rollout Technical aspects: Product- oriented projects –Solutions developed separately by architects may not be embraced –Finding a project that will accept responsibility Organizational/Process aspects: –Organization seldom exists –Synchronize with technical change

24. Differences Functional/Architectural Changes Functional –Needs come from customers –Established organization and process for managing change –Feature by feature _ –Limited effects –Part of standard work Architectural –Needs can emerge from many sources –Changes often not tied to architecture organization, no established process _ –Often spans many features –Affects organization –Affects how people work

25. Rollout How to implement technical parts? –Separate project –Parallel project –Part of standard project –New product generation How to implement organizational changes? –Insufficient long- term view in projects? –Insufficient ability to influence projects from line management?

26. Architectural Changes lead to Process and Organizational Changes Process Project Architecture Features Line How work is done Product Organization Quality Thesis: Changes of Processes and Architectures www.telecom.lth.se/Personal/josefn/lic

27. Further Work The balance between line and project Survey: Categorization of architecture changes: Drivers, initiators, success factors, organization, implementation environment Deep dive into the organizational change Empowering architects

28. Further Work Architecture Investment Business Cases? Cost Time Release Preemptive Architecture Investment Unscheduled Architecture Fix

29. My Solution The PM Pointer Upcoming Ideas: PM Rearview Mirror PM Kick-in-the-butt

30. Discussion Issues How to organize architecture work? (Line/Project) When to do architecture work? (Preemptive/Just-in-time/The bottom line) How to perform neccessary reorganizations? How to develop? –Line: Effective, specialized –Project: Teamwork, from start to finish, clear goals