Acknowledgements
Dr. Gernot Starke
Long ago, on a winter's day in 2004, I sat together with Peter Hruschka, a long-time friend of mine and discussed one of our mutual favorite subjects – the structure and concepts of software systems. We reflected on an issue we had both encountered often within our work, independent of client, domain, or technology: developers know their way around implementation/technologies; managers know their way around budgets and risk management. But when forced to communicate (or even document) the architecture of systems, they often start inventing their own specific ways of articulating structures, designs, concepts, and decisions.
Peter talked about his experience in requirements engineering: he introduced ...
Get arc42 by Example now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
