1 / 30

Experiences from the Architectural Change Process

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. The Product Lifecycle. Market Penetration. Maturity. Decline. Growth. Introduction. Time. Releases.

alana-fulton
Download Presentation

Experiences from the Architectural Change Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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 Maturity Decline Growth Introduction Time Releases

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

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

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

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

  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 • Initial decision preparation • Document background • Identify stakeholders/decision makers • Decision: Go/no-go • Decision preparation • Analyze technical alternatives • Analyze process and organization impact • Return on investment • Decision: Rollout • Rollout 2 3 4 5 6

  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 • Protocol Framework • Real-Time Operating System Company B: Platforms for consumer electronics • Data Router • HAL Split • Include-file Reorganization Company C: Development tools • Communication Mechanism • Editor Framework

  17. The Changes 1 Protocol Framework: RTOS switch: 2 Data Router: HAL Split: 3 Include-file reorganization: 4 Communication mechanism: Editor Framework: 5 6

  18. 1: A Need Emerges 1 • 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 2 3 4 5 6

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

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

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

  22. 5: Decision Point: Rollout 1 • 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? 2 3 4 5 6

  23. 6: Rollout 1 • 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 2 3 4 5 6

  24. 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 Differences Functional/Architectural Changes

  25. 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? Rollout

  26. How work is done Process Product Features Project Quality Organization Line Architecture Architectural Changes lead to Process and Organizational Changes 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 Preemptive Architecture Investment Release Unscheduled Architecture Fix Time

  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

More Related