Standards: radar, patterns, decisions, exceptions
Standards are the rules of the road of a workspace, kept in one register. iyedy checks your diagrams against them: a technology on hold, a pattern copy out of date, an exception past its date or a design changed since its review each raise a finding.
On this page
One register, four kinds
Open it with Standards register in the Governance menu. Each row says its type, its name, its version or ring, how the open diagram uses it, and the deviations the checks report about it.
| Kind | What it records | The checks that watch it | Guide |
|---|---|---|---|
| Radar | Each technology with a ring (Adopt, Trial, Assess, Hold) and its lifecycle dates | STD-01 end of life, STD-02 on hold, STD-03 not on the radar | Use the technology radar |
| Pattern | A reusable piece of model, published in versions | Copies show when a newer version exists | Apply a pattern |
| Decision | A review decision pinned to a revision, with its conditions | GOV-03 overdue condition, GOV-04 changed since the decision | Record a decision |
| Exception | An accepted gap to a standard, with its expiry and controls | GOV-01 expired, GOV-02 due for review | Accept an exception |
Filter the register with All, Patterns, Radar, Decisions and Exceptions, or search by name, key or technology. A row opens the editor that owns it: the radar sheet, the pattern, or the governance register.
How standards reach your diagrams
- Through the checks. The STD and GOV rules run with the others, in your browser, on every change. Their findings sit in the same review list. See Check rules.
- Through the review page. Its Standards tab shows the standards this diagram applies and the deviations its checks report.
- Through the Assistant. Designs and reviews read your standards: the technologies to adopt or on hold, and the standard patterns. See What the Assistant reads.
Who keeps it
The register belongs to a workspace. In an organisation, the owners of the workspace keep it, and editors change the radar and record decisions; the register says who to ask. In your personal workspace it is Your standards: the technologies, patterns and decisions you apply to your diagrams.
The register starts empty: no vendor list ships with iyedy. In your personal workspace, Start from an example list adds a few rated technologies to begin with.
What this means for you
- Architects: rate the few technologies that matter first (your database, your runtime, what you want to stop), then let STD-01 and STD-02 point at them in every diagram.
- Review boards: record each decision with its conditions; GOV-03 and GOV-04 tell you when a condition is late or a design moved on.
- Teams with legacy: an exception with a date is better than a dismissed finding: it says why, until when, and with which controls.
Was this page helpful?Your answer is anonymous and counts only if you accepted measurement.
What went wrong?
Don't write personal data.