PrismDevRelOpen the app
Case studies: Quality model (ISO/IEC 25010)

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 · Rule 30

Quality model (ISO/IEC 25010)

What good quality means for Rule 30, and the numbers that measure it.

Subject: Rule 30 at commit e3be477fded2, 2180 facet records, source digest c4584388f052fc09.

Quality records by kindProductQualityCharacteristic: 1 records; QualityMeasure: 1 records; QualityRequirement: 1 records; QualitySubcharacteristic: 1 recordsProductQualityCharacteristic1QualityMeasure1QualityRequirement1QualitySubcharacteristic1
Quality records by kind. The 4 records this page teaches, one bar for each kind. Each kind has its own section below.
The data in this figure
records
ProductQualityCharacteristic1
QualityMeasure1
QualityRequirement1
QualitySubcharacteristic1

The quality facet follows ISO/IEC 25010:2023. It holds product quality characteristics, their subcharacteristics, the requirements under them, and measures with thresholds. See PrismPM SPEC section 2.

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

Every record

IndexRecordKindName
539ResearchArchitecture::boundedWorkQualitySubcharacteristicboundedWork
563ResearchArchitecture::libraryBuildBudgetQualityMeasurelibraryBuildBudget
565ResearchArchitecture::maintainabilityProductQualityCharacteristicmaintainability
567ResearchArchitecture::oneLibraryPerCohortQualityRequirementoneLibraryPerCohort

ProductQualityCharacteristic (1)

QualityMeasure (1)

QualityRequirement (1)

QualitySubcharacteristic (1)

referenceEvaluatecase studyMarkdown

Words on this page 4
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.
theorem
A statement about the model that the Lean kernel has checked, so it holds for every input, not only the ones tested.