| 1 |
Uses ubiquitous/business language throughout; no technical or implementation jargon (e.g. no "table", "class", "pointer") |
Pass |
Business terms; API address is the only technical word and is the data the Maintainer configures. |
| 2 |
Multiplicities on associations are correct and complete (e.g. 1..*, 0..1) |
Pass |
All 21 associations have both multiplicities, including the optional GitHub paths. |
| 3 |
No operation/method signatures shown — attributes and associations only |
Pass |
Attributes and associations only. |
| 4 |
Associations are named with an unambiguous reading direction |
Pass |
Each association has a reading direction. |
| 5 |
Generalization/specialization used correctly, reflecting true "is-a" relationships, not misused for code reuse |
Pass |
Only Repository specializes into Gitea Repository and GitHub Repository, justified as is-a. |
| 6 |
Every concept traces to a noun phrase found in the use cases or glossary |
Pass |
The concept table traces every concept to a UC-001 step or precondition. |
| 7 |
Attributes are simple domain data (no foreign-key-like references or object pointers modeled as attributes) |
Pass |
Attributes are simple data; links are associations. |