This presentation offers a tool to work explicitly on what “good architecture” is in a specific situation. When the architect has a clear picture of when the architecture is good for a particular system and its environment, it becomes easier to choose among the abundance of approaches and techniques, while focusing on the most architecturally relevant aspects. The architect will have more clarity of the attention required by stakeholders, concerns, models and other architectural elements. The used framework starts with the following aspects, which we call the 3 Cs of good architecture:
Correctness: how doe the system fit in its environment?
Consistency: how well is the system engineered?
Communication: Does everyone know what they need to know?
To check if the architecture is good, and to give direction to the architectural activities, the architect uses a set of questions related to correctness, consistency, and communication. The architect must be able to answer each question or should be able to explain why an answer cannot be given. This presentation explains the concept of good architecture, illustrated by real-world examples.
Robert Deckers has been working on formal specifications, code generation, model interpreters and methods for domain modelling, architecture, and requirements since 1991. He has been active as architect and consultant on all organizational levels. Robert is author of the book “DYA|Software, architecture approach for mission critical applications”. Since 2010, he teaches courses on architecture, and domain modelling at companies and universities, and coaches architects. In 2013 he started his own company to devote himself to Model Driven Development with a focus on quality aspects and multiple domains because, “system development is about integrating knowledge, and not about realizing technology”. Robert currently fulfils a PhD position at the VU in Amsterdam on that topic.
Owner at Atom Free IT