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.2 KiB
1.2 KiB
Sequence Diagram (Design) (SD)
Cite in CrossReference only if the instance exists (new-artifact.sh checks this for you):
- OC — Required source: the contract whose postconditions each diagram realizes
- DCD — Forward: classes/methods these messages become
Required sections (after Metadata / Version History)
One block per realized Operation Contract:
- Realizes — the contract (
[OC-…]) and its operation name. - Diagram — PlantUML sequence diagram: sync (solid filled arrow),
async (open arrow), returns (dashed); activations matching the call
nesting;
create/destroyshown for transient objects;loop/alt/optfragments for conditional/repeated behavior. - Pattern Annotations — table
Pattern (GRASP/GoF) | Applied to | Rationale. Patterns are labelled, never implicit. - Postcondition Coverage —
Postcondition | Satisfied by message; every postcondition of the contract must be covered. - Responsibility Check — a short note showing no god-object receives all messages (low coupling, high cohesion).
Terminology
Use the IT terms from the dictionary (DICT), not the PO terms the Domain Model uses.