arc42 by Example - Volume 2
arc42 by Example - Volume 2
Architecture Documentation for Embedded Systems and IoT
About the Book
This book contains a couple of examples of System Architecture Documentation based upon the practical, economical, well-established and systematic arc42 approach. It shows how you can document and communicate system architectures (i.e. architecture of hardware/software systems).
About the Authors
Bundles that include this book
Table of Contents
-
-
Preface
- Acknowledgement
- Conventions
- Disclaimer
-
Preface
-
I. Introduction
-
- I.1. What is arc42?
- I.2. Why this book?
- I.3. What this book is not
- I.4 Overview of Examples
-
-
II. Octopus
-
II.1. Introduction and Goals
- 1.1 Requirements Overview
- 1.2. Quality Goals
- 1.3 Stakeholders
-
II.2. Constraints
- 2.1. Technical Constraints
- 2.2. Organizational Constraints
-
II.3. Scope and Context
- 3.1 Business Context
- 3.2 Technical Context
- II.4. Solution Strategy
-
II.5. Building Block View
- 5.1 Front-end Application and Back-end Application
- 5.2 Analysis
-
II.6. Runtime View
- 6.1 Reading Values
- 6.2 Configuration Setting
-
II.7. Deployment View
- 7.1 Wireless Version
- 7.2 Wired Version
-
II.8. Crosscutting Concepts
- 8.1 Software Updates
- 8.2 Software Modularization
- 8.3 REST
- II.9. Architecture Decisions
- II.10. Quality Scenarios
- II.11. Risks and Technical Debts
- II.12. Glossary
-
II.1. Introduction and Goals
-
III. Traffic Pursuit Unit (TPU)
-
III.1. Introduction
- 1.1 Requirements
- 1.2 Quality Goals
- 1.3 Stakeholders
- III.2. Architectural Constraints
-
III.3. Scope and Context
- 3.1 Business Context
- 3.2 Technical Context
- III.4 Solution Strategy
-
III.5. Building Block View
- 5.1 White Box of TPU
- 5.2 White Boxes Level 2
- 5.3 White Boxes Level 3
-
III.6. Runtime View
- 6.1 Processing and Propagation of Measuring Data
-
III.7. Deployment View
- 7.1 Deployment Level 1
- 7.1 Deployment Level 2
-
III.8. Crosscutting Concepts
- 8.1 Domain Entity Model
- 8.2 Event Handling
- III.9. Architecture Decisions
-
III.10. Quality Requirements
- 10.1 Quality Tree
- 10.2 Quality Scenarios
- III.11. Risks and Technical Debts
- III.12. Glossary
-
III.1. Introduction
- The Authors
- Further Reading
- Notes
The Leanpub 60 Day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.
You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!
So, there's no reason not to click the Add to Cart button, is there?
See full terms...
80% Royalties. Earn $16 on a $20 book.
We pay 80% royalties. That's not a typo: you earn $16 on a $20 sale. If we sell 5000 non-refunded copies of your book or course for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $13 millionwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them
