73 lines
4.8 KiB
Markdown
73 lines
4.8 KiB
Markdown
# Domain Dictionary (PO and IT terms)
|
|
|
|
## Metadata
|
|
| Key | Value |
|
|
| --- | --- |
|
|
| ID | DICT-001 |
|
|
| CrossReference | [BC-001], [SA-001], [DM-001], [DM-002], [DM-003] |
|
|
|
|
## Version History
|
|
| Date | Status | Author | Reviewer | Change | Commit |
|
|
| --- | --- | --- | --- | --- | --- |
|
|
| 2026-10-07 | Proposed | Jens Tirsvad Nielsen | S02 | Added Command Link, Checkout and Working Folder (DM-003, UC-002) | [1cd27f7] |
|
|
| 2026-10-07 | Proposed | Jens Tirsvad Nielsen | S02 | `ConfigFiles` named as a system concept without a PO term | [0ab5006] |
|
|
|
|
---
|
|
|
|
## Purpose and Scope
|
|
|
|
Maps each Product Owner (PO) term to its professional IT term. PO language: English (`en`), from the registry's `Languages` section. It covers the concepts of [DM-001] and [DM-002].
|
|
|
|
## Dictionary
|
|
|
|
| PO term | Language | IT term | Definition | Used as PO term in | Used as IT term in |
|
|
| --- | --- | --- | --- | --- | --- |
|
|
| Maintainer | en | Maintainer | The person who creates a new project. | DM, UC, US | OC, SD, DCD |
|
|
| Project | en | ProjectRequest | The new software project being set up, with its name, description and visibility. | DM, UC, US | OC, SD, DCD |
|
|
| Configuration | en | Configuration | The service addresses and access tokens set up before starting. | DM, UC | OC, SD, DCD |
|
|
| Git Host | en | GitHost | A service that holds repositories: Gitea or GitHub. | DM, UC | OC, SD, DCD |
|
|
| Access Token | en | Credential | A secret that lets the Maintainer act on a Git Host; never part of an address. | DM, UC | OC, SD, DCD |
|
|
| Owner | en | Owner | The user or organization on a Git Host that owns repositories. | DM, UC | OC, SD, DCD |
|
|
| Repository | en | Repository | A place on a Git Host that holds a project's history. | DM, UC | OC, SD, DCD |
|
|
| Gitea Repository | en | GiteaRepository | The repository on Gitea; the source of truth. | DM, UC | OC, SD, DCD |
|
|
| GitHub Repository | en | GitHubRepository | The repository on GitHub; it receives its content from the mirror. | DM, UC | OC, SD, DCD |
|
|
| License | en | LicenseFile | The legal terms file added to the Gitea repository when a license applies. | DM, UC | OC, SD, DCD |
|
|
| Mirror | en | PushMirror | The push mirror that copies a Gitea repository to a GitHub repository. | DM, UC | OC, SD, DCD |
|
|
| Local Project | en | LocalProject | The project directory on the Maintainer's machine. | DM, UC | OC, SD, DCD |
|
|
| Remote | en | Remote | A named link from a local project to a repository. | DM, UC | OC, SD, DCD |
|
|
| Framework | en | Submodule | The SQA-QC-Framework added to a local project; the IT term names how it is attached. | DM, UC | OC, SD, DCD |
|
|
| Framework Setup | en | HookSetup | The skills and git hooks installed from the framework, with the plan gate on or off. | DM, UC | OC, SD, DCD |
|
|
| Template | en | Template | A framework file copied into a project. | DM, UC | OC, SD, DCD |
|
|
| Credentials File | en | EnvFile | The file in the local project that holds a copy of the credentials the project needs; owner-only and ignored by git. | DM, UC | OC, SD, DCD |
|
|
| Command Link | en | CommandLink | A name on the shell's search path that leads to the script; made by the Maintainer, only followed by the system (no design class). | DM, UC | OC, SD, DCD |
|
|
| Checkout | en | Checkout | The folder that holds RepoFoundry and its default `config.env` and `.env`. | DM, UC | OC, SD, DCD |
|
|
| Working Folder | en | WorkingFolder | The folder the Maintainer starts the script in; the base of the default project directory. | DM, UC | OC, SD, DCD |
|
|
| Summary | en | Summary | The report of what was created, skipped or failed and how to continue. | DM, UC | OC, SD, DCD |
|
|
|
|
## Rules
|
|
|
|
- The Domain Model, use cases and user stories use the PO term; the Operation
|
|
Contract, Sequence Diagram, Design Class Diagram and ERD use the IT term.
|
|
- One IT term per PO term and one PO term per IT term; no synonyms.
|
|
- `Run`, `ToolCheck`, `PreflightResult`, `PromptSet` and `ConfigFiles` (the two
|
|
files chosen for the Configuration, in [OC-002]) appear in the Operation
|
|
Contracts but have no PO term: they are system concepts, not domain concepts, and are not
|
|
in the Domain Model.
|
|
- `InstallResult` and the enumeration `Visibility` appear only in [DCD-001]:
|
|
`InstallResult` carries the three results of one operation, and `Visibility`
|
|
is the type of the Project and Repository attribute of the same name. Neither
|
|
is a domain concept.
|
|
- A new concept in a Domain Model gets a row here in the same change.
|
|
|
|
---
|
|
|
|
[BC-001]: ./business-case.md
|
|
[DM-003]: ./uc-002/dm.md
|
|
[SA-001]: ./stakeholder-analysis.md
|
|
[DM-001]: ./uc-001/dm.md
|
|
[DM-002]: ./domain-model.md
|
|
[OC-001]: ./uc-001/oc.md
|
|
[DCD-001]: ./uc-001/dcd.md
|
|
[1cd27f7]: https://git.tirsystem.com/TirSystem-BashScript/repo_foundry/commit/1cd27f77ed844773a969210a11de0d8bb98ac98f
|
|
[0ab5006]: https://git.tirsystem.com/TirSystem-BashScript/repo_foundry/commit/0ab50068bf9e5be82a801af9dbe5b763eeaf7f31
|