Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
arc42 by Example

You're reading from   arc42 by Example Software architecture documentation in practice

Arrow left icon
Product type Paperback
Published in Oct 2019
Publisher
ISBN-13 9781839214356
Length 236 pages
Edition 1st Edition
Arrow right icon
Authors (4):
Arrow left icon
Michael Simons Michael Simons
Author Profile Icon Michael Simons
Michael Simons
Ralf D. Müller Ralf D. Müller
Author Profile Icon Ralf D. Müller
Ralf D. Müller
Stefan Zörner Stefan Zörner
Author Profile Icon Stefan Zörner
Stefan Zörner
Gernot Starke Gernot Starke
Author Profile Icon Gernot Starke
Gernot Starke
Arrow right icon
View More author details
Toc

Table of Contents (9) Chapters Close

About the Book Acknowledgements
I - Introduction FREE CHAPTER II - HTML Sanity Checking III - Mass Market Customer Relationship Management IV - biking2 V - DokChess VI - docToolchain VII - macOS Menu Bar Application

V.10 Quality Scenarios

The quality scenarios in this section depict the fundamental quality goals of DokChess as well as other required quality properties. They allow the evaluation of decision alternatives.

10.1 Utility Tree

The following diagram gives an overview of the relevant quality attributes and their associated scenarios:

Figure 5.42: Utility Tree

10.2 Evaluation Scenarios

The evaluation scenarios can be listed as follows:

  1. A person with basic knowledge of UML and chess looks for an introduction to the DokChess architecture. They get the idea of the solution strategy and the essential design within 15 minutes.
  2. An architect wishes to apply arc42 searches to a concrete example for an arbitrary section of the template. They find the relevant content immediately in the documentation.
  3. An experienced Java developer searches for the implementation of a module described in the design. They find it in the source code without detours or help from others.
  4. A developer...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image