Explanation: Features and journeys facet
// explanation · Learn
Features and journeys facet
What this facet holds and the standard it follows. Then how each case study uses it.
Features say what the product does. Each has a statement, the interface calls that do the work, and the acceptance rows that accept it. A journey is the features one stakeholder uses, in order. The SDK checks them with PP2014 to PP2018. See PrismPM SPEC section 2.2.
- A feature needs at least one call and one acceptance row.
- A journey's actor is a declared stakeholder and every step a declared feature.
The facet follows PrismPM features and journeys. 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 15 records of 2 kinds. Features and journeys teaches them.
| Kind | Records | First record |
|---|---|---|
| Feature | 10 | Features::featureBrowserRoutes |
| Journey | 5 | Features::journeyDevRelAuthor |
Prism-DevRel
Prism-DevRel declares 20 records of 2 kinds. Features and journeys teaches them.
| Kind | Records | First record |
|---|---|---|
| Feature | 15 | Features::featureAgents |
| Journey | 5 | Features::journeyAuthor |
Rule 30
Rule 30 declares no record of this facet.
Verdant Resonance
Verdant Resonance declares no record of this facet.
Foundry
Foundry declares no record of this facet.
Words on this page 4
- 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.
- SDK
- Software development kit. Here, the PrismPM container image that builds, checks and verifies Prism models.
- stakeholder
- A person or group with an interest in the system, as ISO/IEC/IEEE 42010 defines it.