SPA Conference session: When good architecture goes bad | |||
| One-line description: | A workshop where participants explore the value of actively preventing decay of software architectures | ||
| Session format: | Workshop (150 mins) [read about the different session types] | ||
| Abstract: | As software evolves its architecture ‘as-is’ deviates from its architecture ‘as-hoped-for’ – the architecture is said to decay. Architectural decay can be a problem because: - the time, effort and risk in implementing further changes increases - the effect of further changes becomes harder to predict - further changes typically cause the ‘as-is’ architecture to deviate further from the ‘as-hoped-for’ architecture – the situation becomes worse. This session looks at some case studies of architectural decay and explores practices to prevent or slow such decay. A key element of the session is an attempt to place a value on such preventative work. Objectives: 1. To explore the causes, effects and costs of architectural decay. 2. To identify possible practices for maintaining architectural integrity. 3. To discuss the value of work to prevent or slow architectural decay. | ||
| Audience background: | Architects, designers, developers, managers and others involved in the development of software systems. | ||
| Benefits of participating: | Participants will leave the session with a better understanding of what it means for software architecture to decay and with some possible tools for preventing or slowing such decay and for estimating the value of such work. This will enable them to present more solid and informed business cases and plans for preventative work to maintain architectural integrity. | ||
| Materials provided: | Session slides, two short case study descriptions. | ||
| Process: | The session will be supported through slide-based exposition covering the key concepts. This will include examples of software systems suffering architectural decay and practices to prevent or slow such decay. Group exercises will allow participants to benefit by sharing their experience of architectural decay and how to address it. | ||
| Detailed timetable: | 1. Introduction – 5 mins 2. Architectural smells – 35 minutes 3. The cost of decay – 25 minutes 4. Causes of decay – 25 minutes 5. Preventing decay – 40 mins 6. The value of integrity – 25 mins 7. Closing remarks – 5 mins | ||
| Outputs: | Flip chart sheets and conference wiki review page. Follow-up activity - an architectural integrity manifesto? | ||
| History: | This session has been specially prepared for SPA2008. | ||
| Presenters | |||
| 1. Mark Dalgarno Software Acumen |
2. | 3. | |