PrismDevRelOpen the app
Case studies: Design views in OPM and UML

Overview

Case studies

UORust

How UORust was modeledArchitecture walkthroughDesign views in OPM and UMLFeatures and journeysSecurity and threat modelQuality model (ISO/IEC 25010)Behavior and proofsSystem and releaseExtension facetsCommand referenceSlides and video scriptRecord explorerllms.txt and Markdown twins

Prism-DevRel

How Prism-DevRel was modeledArchitecture walkthroughDesign views in OPM and UMLFeatures and journeysSecurity and threat modelQuality model (ISO/IEC 25010)Behavior and proofsExtension facetsSlides and video scriptRecord explorerllms.txt and Markdown twins

Rule 30

How Rule 30 was modeledArchitecture walkthroughSecurity and threat modelQuality model (ISO/IEC 25010)Behavior and proofsSlides and video scriptRecord explorerllms.txt and Markdown twins

Verdant Resonance

How Verdant Resonance was modeledBehavior and proofsExtension facetsSlides and video scriptRecord explorerllms.txt and Markdown twins

Foundry

How Foundry was modeledBehavior and proofsSlides and video scriptRecord explorerllms.txt and Markdown twins

// case study · UORust

Design views in OPM and UML

Every design view of UORust, drawn. It shows things, steps, parts, messages and states.

Subject: UORust at commit afd5cea950a8, 331 facet records, source digest f3f743b6834adaff.

Design views records by kindDesignView: 4 records; OpmLink: 8 records; OpmState: 3 records; OpmThing: 10 records; OpmZoom: 4 records; SystemProcess: 9 records; SystemState: 5 records; UmlComponent: 5 records; UmlConnector: 5 records; UmlLifeline: 5 records; UmlMessage: 6 records; UmlState: 5 records; UmlTransition: 4 recordsDesignView4OpmLink8OpmState3OpmThing10OpmZoom4SystemProcess9SystemState5UmlComponent5UmlConnector5UmlLifeline5UmlMessage6UmlState5UmlTransition4
Design views records by kind. The 73 records this page teaches, one bar for each kind. Each kind has its own section below.
The data in this figure
records
DesignView4
OpmLink8
OpmState3
OpmThing10
OpmZoom4
SystemProcess9
SystemState5
UmlComponent5
UmlConnector5
UmlLifeline5
UmlMessage6
UmlState5
UmlTransition4

Design views add drawings to the architecture. OPM (ISO/PAS 19450) views show objects and processes. UML 2.5.1 views show components, sequences and state machines. The SDK checks every element against the system model (PP2012). It renders OPM views as .opl and UML views as .puml in the build. The drawings here come from the same records. See PrismPM SPEC section 2.1.

Design views facet explains the facet for every Prism model, with the counts of every case study.

The projection process

Design::viewOpmPipeline, a opmObjectProcess view for viewpoint Architecture::viewpointPipelineCompleteness.

The projection processeffectinvocationagentresultinvocationinvocationinstrumentinstrumentzoom 0zoom 1zoom 2zoom 3AdmissionAdmituorust CLIEmitIngestPrismPM SDKRouteRouterRunSubject workspace
The projection process. Boxes are parts, arrows are the links between them, drawn from the model's own records.
The data in this figure

10 elements: Admission, Admit, uorust CLI, Emit, Ingest, PrismPM SDK, Route, Router, Run, Subject workspace. Admission to Admit (effect). Admit to Emit (invocation). uorust CLI to Run (agent). Emit to PrismPM SDK (result). Ingest to Route (invocation). Route to Admit (invocation). Router to Route (instrument). Subject workspace to Ingest (instrument). Run to Ingest (zoom 0). Run to Route (zoom 1). Run to Admit (zoom 2). Run to Emit (zoom 3).

Components of the pipeline

Design::viewUmlComponents, a umlComponent view for viewpoint Architecture::viewpointPipelineFidelity.

Components of the pipelineAdmissionuorust CLIEmitterIngestRouter
Components of the pipeline. Boxes are parts, arrows are the links between them, drawn from the model's own records.
The data in this figure

5 elements: Admission, uorust CLI, Emitter, Ingest, Router. Admission to Emitter. uorust CLI to Ingest. Emitter to uorust CLI. Ingest to Router. Router to Admission.

States of a fact's admission

Design::viewUmlFactAdmission, a umlStateMachine view for viewpoint Architecture::viewpointRefusal.

States of a fact's admissionprocessAdmitprocessRefuseprocessRecordClaimprocessReleaseFactAdmittedFactOpenClaimFactProposedFactRefusedFactReleased
States of a fact's admission. Boxes are parts, arrows are the links between them, drawn from the model's own records.
The data in this figure

5 elements: FactAdmitted, FactOpenClaim, FactProposed, FactRefused, FactReleased. FactProposed to FactAdmitted (processAdmit). FactProposed to FactRefused (processRefuse). FactRefused to FactOpenClaim (processRecordClaim). FactAdmitted to FactReleased (processRelease).

A workspace through ingest, route, admit and emit

Design::viewUmlSequence, a umlSequence view for viewpoint Architecture::viewpointPipelineFidelity.

A workspace through ingest, route, admit and emituorust CLIIngestRouterAdmissionEmittersynchronous: processIngestsynchronous: processRoutesynchronous: processAdmitsynchronous: processRefusesynchronous: processEmitreply: processEmit
A workspace through ingest, route, admit and emit. Boxes are parts, arrows are the links between them, drawn from the model's own records.
The data in this figure

Lifelines: uorust CLI, Ingest, Router, Admission, Emitter. 1. uorust CLI to Ingest, synchronous, processIngest. 2. Ingest to Router, synchronous, processRoute. 3. Router to Admission, synchronous, processAdmit. 4. Admission to Admission, synchronous, processRefuse. 5. Admission to Emitter, synchronous, processEmit. 6. Emitter to Admission, reply, processEmit.

Every record

Every record 73 rows
IndexRecordKindName
69Design::connectorAdmissionEmitterUmlConnectorconnectorAdmissionEmitter
70Design::connectorCliIngestUmlConnectorconnectorCliIngest
71Design::connectorEmitterCliUmlConnectorconnectorEmitterCli
72Design::connectorIngestRouterUmlConnectorconnectorIngestRouter
73Design::connectorRouterAdmissionUmlConnectorconnectorRouterAdmission
74Design::lifelineAdmissionUmlLifelinelifelineAdmission
75Design::lifelineCliUmlLifelinelifelineCli
76Design::lifelineEmitterUmlLifelinelifelineEmitter
77Design::lifelineIngestUmlLifelinelifelineIngest
78Design::lifelineRouterUmlLifelinelifelineRouter
79Design::linkAdmissionChangedOpmLinklinkAdmissionChanged
80Design::linkAdmitInvokesEmitOpmLinklinkAdmitInvokesEmit
81Design::linkCliRunsOpmLinklinkCliRuns
82Design::linkEmitResultOpmLinklinkEmitResult
83Design::linkIngestInvokesRouteOpmLinklinkIngestInvokesRoute
84Design::linkRouteInvokesAdmitOpmLinklinkRouteInvokesAdmit
85Design::linkRouterRoutesOpmLinklinkRouterRoutes
86Design::linkWorkspaceIngestedOpmLinklinkWorkspaceIngested
87Design::message0UmlMessagemessage0
88Design::message1UmlMessagemessage1
89Design::message2UmlMessagemessage2
90Design::message3UmlMessagemessage3
91Design::message4UmlMessagemessage4
92Design::message5UmlMessagemessage5
93Design::opmStateAdmittedOpmStateopmStateAdmitted
94Design::opmStateProposedOpmStateopmStateProposed
95Design::opmStateRefusedOpmStateopmStateRefused
96Design::processAdmitSystemProcessprocessAdmit
97Design::processEmitSystemProcessprocessEmit
98Design::processIngestSystemProcessprocessIngest
99Design::processRecordClaimSystemProcessprocessRecordClaim
100Design::processRefuseSystemProcessprocessRefuse
101Design::processReleaseSystemProcessprocessRelease
102Design::processReplayVectorsSystemProcessprocessReplayVectors
103Design::processRouteSystemProcessprocessRoute
104Design::processRunSystemProcessprocessRun
105Design::stateFactAdmittedSystemStatestateFactAdmitted
106Design::stateFactOpenClaimSystemStatestateFactOpenClaim
107Design::stateFactProposedSystemStatestateFactProposed
108Design::stateFactRefusedSystemStatestateFactRefused
109Design::stateFactReleasedSystemStatestateFactReleased
110Design::thingAdmissionOpmThingthingAdmission
111Design::thingAdmitOpmThingthingAdmit
112Design::thingCliOpmThingthingCli
113Design::thingEmitOpmThingthingEmit
114Design::thingIngestOpmThingthingIngest
115Design::thingPrismPmOpmThingthingPrismPm
116Design::thingRouteOpmThingthingRoute
117Design::thingRouterOpmThingthingRouter
118Design::thingRunOpmThingthingRun
119Design::thingWorkspaceOpmThingthingWorkspace
120Design::transition0UmlTransitiontransition0
121Design::transition1UmlTransitiontransition1
122Design::transition2UmlTransitiontransition2
123Design::transition3UmlTransitiontransition3
124Design::umlComponentAdmissionUmlComponentumlComponentAdmission
125Design::umlComponentCliUmlComponentumlComponentCli
126Design::umlComponentEmitterUmlComponentumlComponentEmitter
127Design::umlComponentIngestUmlComponentumlComponentIngest
128Design::umlComponentRouterUmlComponentumlComponentRouter
129Design::umlStateFactAdmittedUmlStateumlStateFactAdmitted
130Design::umlStateFactOpenClaimUmlStateumlStateFactOpenClaim
131Design::umlStateFactProposedUmlStateumlStateFactProposed
132Design::umlStateFactRefusedUmlStateumlStateFactRefused
133Design::umlStateFactReleasedUmlStateumlStateFactReleased
134Design::viewOpmPipelineDesignViewThe projection process
135Design::viewUmlComponentsDesignViewComponents of the pipeline
136Design::viewUmlFactAdmissionDesignViewStates of a fact's admission
137Design::viewUmlSequenceDesignViewA workspace through ingest, route, admit and emit
138Design::zoomRun0OpmZoomzoomRun0
139Design::zoomRun1OpmZoomzoomRun1
140Design::zoomRun2OpmZoomzoomRun2
141Design::zoomRun3OpmZoomzoomRun3

DesignView (4)

OpmState (3)

OpmThing (10)

OpmZoom (4)

SystemProcess (9)

SystemState (5)

UmlComponent (5)

UmlConnector (5)

UmlLifeline (5)

UmlMessage (6)

UmlState (5)

UmlTransition (4)

explanationLearncase studyMarkdown

Words on this page 5
Prism model
A description of an app, written in LexLean, that covers every facet of it and that the Lean kernel checks before the app is built.
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.
state machine
A model of something that is always in one state and moves between states on events, as in UML 2.5.1.