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

VI.10 Quality Requirements

QS1: Confidentiality

In order to keep control over the content of your documentation, docToolchain will never use a web-based, remote service for any task without the explicit knowledge of the user.

QS2: Security (besides Confidentiality)

When you think of documentation, security is not the first thing that comes to mind, is it?

However, when you automate some parts of your documentation, or even just include remote sources, security comes into play.

It could even be that you use a plugin (such as the asciidoctorj-screenshot plugin, which is available at https://github.com/asciidoctor/asciidoctorj-screenshot) that lets you execute arbitrary code in the generation phase.

In docToolchain, we assume that the documentation is under your control, and hence, do not apply any special security measures besides respecting QS1: Confidentiality.

QS3: Repeatability

Every run of a docToolchain task creates the same predictable output.

This rule ensures that it doesn't matter if...

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