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.11 Risks

The following risks have been identified at the beginning of the project (December 2010). They influenced the planning of the first three iterations significantly. Since the completion of the third iteration, the risks are mastered. This architectural overview shows the risks, including the former eventuality planning, because of their large impact on the solution.

11.1 Risk: Connecting to a Frontend

There is no knowledge about connecting an engine to an existing chess frontend. Available open source engines are programmed in C and are delivered as executable programs (*.exe). Since DokChess is developed in Java, they are of limited use as examples. Nothing is known in the project about chess communication protocols.

If it is not possible to make a working connection, the solution cannot be used with existing frontends. This not only lacks an important feature (refer V.1.1 Requirements Overview), but also makes the solution as a whole, especially as a case study, untrustworthy.

Eventuality...