Add Pretty Table project: plan, accepted documents and code
Business Case, Stakeholder Analysis, Project Plan and milestone MIL-001 with review records RC-001 to RC-003, then the Python project: PrettyTable Pokemon table, constants, pytest tests, pyproject.toml, Doxyfile, CI workflow and README. Task: MIL-001#1 Task: MIL-001#2 Task: MIL-001#3 Task: MIL-001#4 Task: MIL-001#5 Task: MIL-001#6 Task: MIL-001#7 Task: MIL-001#8
This commit is contained in:
@@ -0,0 +1,35 @@
|
||||
# Use Case (UC)
|
||||
|
||||
Cite in `CrossReference` only if the instance exists (`new-artifact.sh` checks this for you):
|
||||
|
||||
- **UCD** — Actor and use-case names must match it exactly
|
||||
- **US** — Stories this use case decomposes into
|
||||
- **SA** — Stakeholders & Interests — cite S-IDs
|
||||
- **DM** — Forward: concepts derived from this use case's nouns
|
||||
- **SSD** — Forward: the SSD depicting this use case's main scenario
|
||||
|
||||
## Location
|
||||
|
||||
`docs/uc-NNN/uc.md`, one folder per use case (create with
|
||||
`new-artifact.sh UC --file docs/uc-NNN/uc.md`). The artifacts this use case
|
||||
affects are saved in the same folder; see the `project-planning` skill, "Use
|
||||
cases get their own folder".
|
||||
|
||||
## Required sections (after Metadata / Version History)
|
||||
|
||||
Pick the format explicitly (`Format: Brief | Casual | Fully Dressed`) and
|
||||
state the **scope/level** (summary, user-goal, subfunction). Always: primary
|
||||
actor, pre/postconditions, goal-perspective wording with no UI or
|
||||
implementation detail.
|
||||
|
||||
- **Brief** — a single paragraph summarizing only the main success scenario.
|
||||
- **Casual** — informal multi-paragraph narrative; may mention some
|
||||
alternate flows.
|
||||
- **Fully Dressed** — all sections, in order: Scope, Level, Primary Actor,
|
||||
Stakeholders and Interests (cite `SA` S-IDs), Preconditions,
|
||||
Postconditions (success guarantee), Main Success Scenario (numbered
|
||||
steps), Extensions / Alternative Flows (reference `<<include>>` /
|
||||
`<<extend>>` use cases), Special Requirements / Business Rules (per step),
|
||||
Open Issues.
|
||||
|
||||
Title and actor names must match `UCD` and `US` exactly.
|
||||
Reference in New Issue
Block a user