PrismDevRelOpen the app
Explanation: Architecture facet

Evaluate

How one prompt becomes every facet

Learn

Architecture facetDesign views facetFeatures and journeys facetSecurity and threat model facetQuality facetBehavior and proofs facetSystem and release facetExtension facets facetApplication facet

// explanation · Learn

Architecture facet

What this facet holds and the standard it follows. Then how each case study uses it.

Architecture records by case studyUORust: 61 records; Prism-DevRel: 44 records; Rule 30: 37 records; Verdant Resonance: 0 records; Foundry: 0 recordsUORust61Prism-DevRel44Rule 3037Verdant Resonance0Foundry0
Architecture records by case study. How many architecture records each case study declares, one bar for each.
The data in this figure
records
UORust61
Prism-DevRel44
Rule 3037
Verdant Resonance0
Foundry0

The architecture facet is an ISO/IEC/IEEE 42010 architecture description. It says who the system is for (stakeholders) and what they worry about (concerns). It names the parts (components) and how data and control move between them (edges). Viewpoints and views answer each concern. Each record is a definition whose result is a Foundation.Arch record, numbered by its identifier. The rules are in PrismPM SPEC section 2. How to write them is in Write the model.

The facet follows ISO/IEC/IEEE 42010. The facets of a Prism app lists every facet beside this one.

How the case studies declare it

For each case study, its records of this facet by kind. The first record of each kind links to where the case study teaches it.

UORust

UORust declares 61 records of 7 kinds. Architecture walkthrough teaches them.

Prism-DevRel

Prism-DevRel declares 44 records of 7 kinds. Architecture walkthrough teaches them.

Rule 30

Rule 30 declares 37 records of 6 kinds. Architecture walkthrough teaches them.

Verdant Resonance

Verdant Resonance declares no record of this facet.

Foundry

Foundry declares no record of this facet.

explanationLearnMarkdown

Words on this page 3
facet
One view of a model, such as its architecture, its security or its quality. Each facet holds records.
record
One entry in a facet: a component, a threat, a measure or a journey step, with the place in the source it came from.
stakeholder
A person or group with an interest in the system, as ISO/IEC/IEEE 42010 defines it.