Architecture reviews support transparency in software development, they identify major risks and expose important tradeoffs. This cheat sheet offers a well-founded overview.
Stefan Toth und Stefan Zörner
Challenges
- A new development effort is pending and initial solution approaches are being discussed. Are you and your team on the right path?
- Management has lost confidence in your solution. How do you win them back while radiating a sense of security?
- Different stakeholders have contradictory goals for your software. How do you specify and prioritise their wishes?
- Modernization, extension or larger remodelling efforts are planned. How do you find and communicate suitable solution approaches?
- You want to fuel iterative architecture efforts. How do you get continuous feedback?
In this edition
- What’s the benefit of architecture reviews?
- Which methods and tools are helpful?
- Who should be included in reviews and to which extent?
