Tirsvad-Udemy-100-days-of-code/016-pretty-table
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add Pretty Table project: plan, accepted documents and code

Browse Source 
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:
Tirsvad
2026-10-07 12:02:59 +08:00
parent 115b6c64bf
commit b0a7414204
137 changed files with 6801 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.agents/skills/artifact/references/DICT.md
+31
View File
@@ -0,0 +1,31 @@
# Domain Dictionary (DICT)
Cite in `CrossReference` only if the instance exists (`new-artifact.sh` checks this for you):
- **BC** — The business goals the vocabulary serves
- **SA** — The Product Owner (and other business stakeholders) whose terms are recorded
- **DM** — Concepts whose PO terms are recorded
## Required sections (after Metadata / Version History)
1. **Purpose and Scope** — the PO language and domain (from the registry's
`Languages` section, also in the `Language` and `Domain` Metadata rows) and
what the dictionary covers.
2. **Dictionary** — one row per term:
`PO term | Language | IT term | Definition | Used as PO term in | Used as IT term in`.
The definition is written in the PO language. "Used as PO term in" and
"Used as IT term in" list artifact types (for example `DM` and `OC, SD,
DCD, ERD`).
3. **Rules** — the register split (PO term in the Domain Model, use cases and
user stories; IT term in the Operation Contract, Sequence Diagram, Design
Class Diagram and ERD) and one IT term per PO term.
One dictionary has one domain: the PO terms are the domain's own words (for
example `medical`), the IT terms are professional IT. A project whose PO terms
come from two domains keeps one dictionary per domain, each with its own
`Domain` row; a term never appears in two.
Keep the dictionary in step with the Domain Model: a new concept gets a row
in the same change. When the PO language is English, the PO and IT columns can
still differ (a business word against a technical one); keep the file anyway
when the two registers use different words.