Appendix. Diagram Review Checklist
| Diagram Review Checklist | ||
|---|---|---|
| General | ||
|
Does the diagram have a title? |
Yes |
No |
|
Do you understand what the diagram’s type is? |
Yes |
No |
|
Do you understand what the diagram’s scope is? |
Yes |
No |
|
Does the diagram have a key to describe any notation used? |
Yes |
No |
| Elements | ||
|
Does every element have a name? |
Yes |
No |
|
Do you understand the type of every element? (level of abstraction; software system, container, component, etc.) |
Yes |
No |
|
Do you understand what every element does? |
Yes |
No |
|
Where applicable, do you understand the technology choices associated with every element? |
Yes |
No |
|
Do you understand the meaning of all acronyms, abbreviations, and code names used? |
Yes |
No |
|
Do you understand the meaning of all colors used? |
Yes |
No |
|
Do you understand the meaning of all shapes used? |
Yes |
No |
|
Do you understand the meaning of all icons used? |
Yes |
No |
|
Do you understand the meaning of all border styles used? (solid, dashed, dotted, etc.) |
Yes |
No |
|
Do you understand the meaning of all element sizes used? (e.g., small versus large boxes) |
Yes |
No |
| Relationships | ||
|
Does every line have a label describing the intent of that relationship? |
Yes |
No |
|
Does the description match the relationship direction? |
Yes |
No |
|
Where applicable, do you understand the technology choices associated with every relationship? (e.g., protocols for interprocess communication) |
Yes |
|
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