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

II.12 Glossary

Note

You need to understand the most important domain terms and expressions that stakeholders use when communicating with the system, its interfaces, goals, and requirements.

The glossary is one manifestation of our pledge to "explicit, not implicit," as it associates words or terms with sense, meaning, and semantics.

In the case of our small example, the terms given here should be good friends to most developers.

The following table lists the important terms that have been used throughout:

Figure 2.29: Glossary of common terms
Figure 2.29: Glossary of common terms