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.11 Risks and Technical Debt

Note

You may want to know about the technical risks of your system so that you can address potential future problems.

In addition, you may want to support your management stakeholders (that is, project management, product owner, and so on) by identifying technical risks.

In our small example, we can't see any real risks for architecture and implementation. Therefore, the risks that follow are a bit artificial.

11.1 Technical Risks

The technical risks are as follows:

Figure 2.27: Technical risks

11.2 Business or Domain Risks

The business risks are as follows:

Figure 2.28: Business risks