Greenfield development is a rare luxury in the software world. Usually developers and software architects have to enhance, modify or repair existing systems. The emphasis of changes lies on additional features, instead of architectural, structural or conceptual improvement – often resulting from restricted budgets and severe timing constraints.
This tutorial helps you out of this maintenance dilemma – by showing how to:
- identify important and valuable improvement opportunities within your system,
- convince management that architectural evolution is neccessary – and which benefits and risks to expect,
- find appropriate solution approaches to technical problems and risks,
- maintain conceptual integrity of your system over its complete lifetime – keeping understandability high and maintenance costs an adequate ranges.
We introduce aim42 – the (open source) methodical approach to systematic architecture improvement.
aim42 relies on a few clear domain concepts and works iteratively in three phases (analyze, evaluate, improve) supported by crosscutting activities. For each phase, In the tutorial, you experience many of the proven and established practices and patterns contained in aim42. We explain how to addresses both business and technical stakeholders of your system.
By participating, you enhance your own methodical toolset by various practices to identify problems and issues, evaluate those in economical terms and find technical and structural remedies for improvement.
All our content is backed by intensive experience. We cover detailed examples from various domains and projects, and provide practical tipps on how to improve your own systems.