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

VI.2 Architecture Constraints

The following are the various architectural constraints:

  • C1: Run everywhere: docToolchain has to run on all modern operating systems that users need for development, such as Windows, Linux, and macOS.
  • C2: Built for the JVM: docToolchain is built for the JVM. While some of the features provided might also work together with other environments, this can't be guaranteed for all tasks.
  • C3: Enterprise-ready: docToolchain has to run in restricted enterprise environments. It has to run with proxies, minimal dependencies, restricted internet access, and so on.

    This is also listed as requirement RQ3.

  • C4: Headless: docToolchain has to run headless; that is, without a display, to run on build servers. User interaction and Windows features have to be avoided.