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:
-
Unified Modeling Language (UML) 2.5.1 from the Object Management Group
-
C4 Model from Simon Brown
-
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.
| 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 | ||||
| Artifact name | Unified Modeling Language (UML) 2.5.1 | C4 Model | arc42 | Practical Software Architecture |
|---|---|---|---|---|
Architecture overview |
- |
- |
- |
Architecture overview |
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access