Create the Business Case, Stakeholder Analysis (S01 course participant, S02 Udemy coursists, S03 GitHub viewers), Project Plan and the milestone documents MIL-001 (project setup, 6 tasks) and MIL-002 (game implementation, 8 tasks) for the console Blackjack game. Register PP and MIL in the artifact registry, set the PO language to en, and link the synced Gitea milestones in the Gateway Schedule. Refs #1 Refs #2 Refs #3 Refs #4 Refs #5 Refs #6 Refs #7 Refs #8 Refs #9 Refs #10 Refs #11 Refs #12 Refs #13 Refs #14
1.0 KiB
1.0 KiB
Entity Relationship Diagram (ERD) (ERD)
Cite in CrossReference only if the instance exists (new-artifact.sh checks this for you):
- DCD — Required source: classes/attributes each entity persists; data types must match
Required sections (after Metadata / Version History)
- Purpose and Scope.
- Diagram — PlantUML entity diagram with PK/FK marked on every entity and cardinality (1:1, 1:N) on every relationship; N:M relationships resolved through explicit junction entities.
- Entity Table — per entity:
Attribute | Type | PK/FK | Nullable | Source (DCD class.attribute). Types consistent with the DCD; consistent naming, no implementation-specific abbreviations. - Relationship Table —
Entity | Cardinality | Entity | FK | Rule. - Normalization Notes — 3NF confirmed; any denormalization documented with its performance justification.
Terminology
Entity and column names follow the IT terms from the dictionary (DICT), not the PO terms the Domain Model uses.