Docs Case studies UORust Case studies: Features and journeys // case study · UORust
Features and journeys What UORust does, the calls that do it, the rows that accept it, and the paths people take.
Iris Prism modeler
“Walk me through each facet, one record kind at a time.”
Explanation: read it end to end, away from the keyboard.
Subject: UORust at commit afd5cea950a8 , 331 facet records , source digest f3f743b6834adaff.
Features and journeys records by kind Feature: 10 records; Journey: 5 records Feature 10 Journey 5
Features and journeys records by kind. The 15 records this page teaches, one bar for each kind. Each kind has its own section below.The data in this figure 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. Features and journeys facet explains the facet for every Prism model , with the counts of every case study.
Every record Every record 15 rows Index Record Kind Name 142 Features::featureBrowserRoutesFeature UORust's application answers the route table of model/routes.toml route for route, and replays every router and workbench vector of that file in order 143 Features::featureCheckProjectionFeature Check that a directory holds exactly the projection of a workspace. 144 Features::featureCheckedOutputFeature The gate checks the committed fixture projection and a fresh projection of this workspace with lexlean and prismpm 145 Features::featureDeterministicOutputFeature Two projections of the same workspace are byte-identical, for the fixture and for this workspace 146 Features::featureLiftBehaviorFeature Function bodies to LexLean definitions, where the lift is mechanical. 147 Features::featureProjectWorkspaceFeature Write the projection of a workspace into a directory. 148 Features::featureRefuseAmbiguityFeature Admission: what the router proposes is admitted, or refused with a typed reason that becomes an open claim. 149 Features::featureRouteFactsFeature The route table and the router: which kind of Rust fact becomes which kind of Prism record in which facet. 150 Features::featureSelfModelFeature UORust is modeled in every facet, each with records, and every module title has a project-local glossary entry 151 Features::featureTypedErrorsFeature Every way a run can end without a projection is a typed UorustError variant with a negative test 152 Features::journeyDevRelAuthorJourney journeyDevRelAuthor 153 Features::journeyMaintainerJourney journeyMaintainer 154 Features::journeyPrismModelerJourney journeyPrismModeler 155 Features::journeyRustDeveloperJourney journeyRustDeveloper 156 Features::journeySecurityReviewerJourney journeySecurityReviewer
Feature (10) UORust's application answers the route table of model/routes.toml route for route, and replays every router and workbench vector of that file in order Features::featureBrowserRoutes Feature #142 source
UORust's application answers the route table of model/routes.toml route for route, and replays every router and workbench vector of that file in order
statement UORust's application answers the route table of model/routes.toml route for route, and replays every router and workbench vector of that file in ordercalls Features::callPagesRouteRoutes::dispatchacceptance Routes::acceptanceVectorsTaught by Features and journeys , Slides and video script
Check that a directory holds exactly the projection of a workspace. Features::featureCheckProjection Feature #143 source
Check that a directory holds exactly the projection of a workspace.
statement Check that a directory holds exactly the projection of a workspace.calls acceptance Features::acceptFixtureProjectionFeatures::acceptByteIdenticalTaught by Features and journeys
The gate checks the committed fixture projection and a fresh projection of this workspace with lexlean and prismpm Features::featureCheckedOutput Feature #144 source
The gate checks the committed fixture projection and a fresh projection of this workspace with lexlean and prismpm
statement The gate checks the committed fixture projection and a fresh projection of this workspace with lexlean and prismpmcalls Features::callPrismPmCheckacceptance Features::acceptFixtureProjectionFeatures::acceptGateTaught by Features and journeys
Two projections of the same workspace are byte-identical, for the fixture and for this workspace Features::featureDeterministicOutput Feature #145 source
Two projections of the same workspace are byte-identical, for the fixture and for this workspace
statement Two projections of the same workspace are byte-identical, for the fixture and for this workspacecalls Features::callProjectFeatures::callCheckacceptance Features::acceptByteIdenticalTaught by Features and journeys
Function bodies to LexLean definitions, where the lift is mechanical. Features::featureLiftBehavior Feature #146 source
Function bodies to LexLean definitions, where the lift is mechanical.
statement Function bodies to LexLean definitions, where the lift is mechanical.calls Features::callProjectWorkspaceacceptance Taught by Features and journeys
Write the projection of a workspace into a directory. Features::featureProjectWorkspace Feature #147 source
Write the projection of a workspace into a directory.
statement Write the projection of a workspace into a directory.calls Features::callProjectFeatures::callProjectWorkspaceacceptance Features::acceptFixtureProjectionFeatures::acceptGateTaught by Features and journeys
Admission: what the router proposes is admitted, or refused with a typed reason that becomes an open claim. Features::featureRefuseAmbiguity Feature #148 source
Admission: what the router proposes is admitted, or refused with a typed reason that becomes an open claim.
statement Admission: what the router proposes is admitted, or refused with a typed reason that becomes an open claim.calls Features::callProjectWorkspaceFeatures::callRespondacceptance Features::acceptTypedRefusalsFeatures::acceptRouteTheoremsTaught by Features and journeys
The route table and the router: which kind of Rust fact becomes which kind of Prism record in which facet. Features::featureRouteFacts Feature #149 source
The route table and the router: which kind of Rust fact becomes which kind of Prism record in which facet.
statement The route table and the router: which kind of Rust fact becomes which kind of Prism record in which facet.calls Routes::dispatchFeatures::callRespondFeatures::callRoutesacceptance Routes::acceptanceVectorsFeatures::acceptRouterConformanceFeatures::acceptRouteTheoremsTaught by Features and journeys
UORust is modeled in every facet, each with records, and every module title has a project-local glossary entry Features::featureSelfModel Feature #150 source
UORust is modeled in every facet, each with records, and every module title has a project-local glossary entry
statement UORust is modeled in every facet, each with records, and every module title has a project-local glossary entrycalls Features::callPrismPmCheckacceptance Features::acceptGateFeatures::acceptRouteTheoremsTaught by Features and journeys
Every way a run can end without a projection is a typed UorustError variant with a negative test Features::featureTypedErrors Feature #151 source
Every way a run can end without a projection is a typed UorustError variant with a negative test
statement Every way a run can end without a projection is a typed UorustError variant with a negative testcalls Features::callProjectFeatures::callCheckacceptance Features::acceptTypedErrorsTaught by Features and journeys
Journey (5) explanation Learn case study Markdown
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. stakeholder A person or group with an interest in the system, as ISO/IEC/IEEE 42010 defines it.