Security Architecture for Hybrid Cloud

Appendix B. Artifact Mapping

You’re probably already using another method that contains its own artifacts, and the artifact names in this book don’t exactly align with the names you are using. We’ve tried to use a generic set of names that are easily mapped to different methods. In the following tables, we’ve mapped our artifact names to methods that are publicly available either as open source or in published books.

The methods we’ve used are:

1. Unified Modeling Language (UML) 2.5.1 from the Object Management Group

2. C4 Model from Simon Brown

3. arc42

4. Practical Software Architecture from Tilak Mitra

This should help you map to any methods you may be using. Feel free to adapt our artifacts to your method.

Table B-1. Requirements artifact mapping

Artifact name	Unified Modeling Language (UML) 2.5.1	C4 Model	arc42	Practical Software Architecture
Use case	Use case diagram	-	-	Use case diagram
Journey map	-	-	-	-
User story	-	-	-	-
Swimlane diagram	Activity diagram	-	-	-
Separation of duties matrix	-	-	-	-
Non-functional requirementsa	Non-functional requirements	Non-functional requirements	Quality goals/quality requirements	Non-functional requirements
Information asset register	-	-	-	-
a Also sometimes called quality attributes or architectural characteristics

Table B-2. Architecture artifact mapping

Artifact name	Unified Modeling Language (UML) 2.5.1	C4 Model	arc42	Practical Software Architecture
Architecture overview	-	-	-	Architecture overview