Book Image

arc42 by Example

By : Dr. Gernot Starke, Michael Simons, Stefan Zörner, Ralf D. Müller
Book Image

arc42 by Example

By: Dr. Gernot Starke, Michael Simons, Stefan Zörner, Ralf D. Müller

Overview of this book

When developers document the architecture of their systems, they often invent their own specific ways of articulating structures, designs, concepts, and decisions. What they need is a template that enables simple and efficient software architecture documentation. arc42 by Example shows how it's done through several real-world examples. Each example in the book, whether it is a chess engine, a huge CRM system, or a cool web system, starts with a brief description of the problem domain and the quality requirements. Then, you'll discover the system context with all the external interfaces. You'll dive into an overview of the solution strategy to implement the building blocks and runtime scenarios. The later chapters also explain various cross-cutting concerns and how they affect other aspects of a program.
Table of Contents (9 chapters)
Free Chapter
1
Acknowledgements
8
VII - macOS Menu Bar Application

V.10 Quality Scenarios

The quality scenarios in this section depict the fundamental quality goals of DokChess as well as other required quality properties. They allow the evaluation of decision alternatives.

10.1 Utility Tree

The following diagram gives an overview of the relevant quality attributes and their associated scenarios:

Figure 5.42: Utility Tree

10.2 Evaluation Scenarios

The evaluation scenarios can be listed as follows:

  1. A person with basic knowledge of UML and chess looks for an introduction to the DokChess architecture. They get the idea of the solution strategy and the essential design within 15 minutes.
  2. An architect wishes to apply arc42 searches to a concrete example for an arbitrary section of the template. They find the relevant content immediately in the documentation.
  3. An experienced Java developer searches for the implementation of a module described in the design. They find it in the source code without detours or help from others.
  4. A developer...