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.2 Constraints

Note

You want to know the constraints that restrict your freedom regarding design decisions or the development process. Such constraints are often imposed by organizations across several IT systems.

HtmlSC should be:

  • Platform-independent and should run on the major operating systems (Windows, Linux, and macOS).
  • Implemented in Java or Groovy.
  • Integrated with the Gradle build tool.
  • Runnable from the command line.
  • Have minimal runtime and installation dependencies (a Java runtime may be required to run HtmlSC).
  • Developed under a liberal open source license. In addition, all the required dependencies/libraries need to be compatible with a Creative Commons license.