Package-level declarations
Design Check Results
All severities: 2 total / 2 without filed issue · Critical: 0 total / 0 without filed issue · High: 2 total / 2 without filed issue · Moderate: 0 total / 0 without filed issue · Low: 0 total / 0 without filed issue
| Rule | Findings | Findings without filed issue |
|---|---|---|
HIGH descriptionDefinedInDesignPackage Design entity has no required description | 0 | 0 |
HIGH designChildrenBoundary Design contradicts the element's bottom-level declaration | 2 total · 2 high | 2 total · 2 high |
HIGH designChildrenParent Design lists a child with a different parent | 0 | 0 |
MODERATE designClassInstance Design class has no instance property in its file | 0 | 0 |
MODERATE designClassPascalCase Design class name violates PascalCase | 0 | 0 |
MODERATE designClassesTopLevel Design class is nested inside another declaration | 0 | 0 |
HIGH designElementDefined Design has no subject element | 0 | 0 |
MODERATE designObjectCamelCase Design instance name violates camelCase | 0 | 0 |
MODERATE forbiddenWordsInDesign Design entity contains forbidden wording | 0 | 0 |
HIGH nameDefinedInDesignPackage Design entity has no required name | 0 | 0 |
HIGH nonDesignEntityInDesignPackage Entity uses the wrong viewpoint package (Design) | 0 | 0 |
HIGH safetyMeasureAsilDefined Safety measure has no ASIL | 0 | 0 |
HIGH safetyMeasureMustLiveInDesign Safety measure lacks a containing design | 0 | 0 |
HIGH safetyMechanismAsilDefined Safety mechanism has no ASIL | 0 | 0 |
HIGH INFO safetyMechanismAsilExceedsElement Safety mechanism exceeds its element's ASIL | 0 | 0 |
More complete diagnostic records and evidence are available locally on the build machine (not published), at repository-relative path clusters/aeb/build/docs/com.example.stig.clusters.aeb--model-check-results.json.
Documents the sensing-to-reaction architecture of the AEB cluster.
FusionActivity synchronizes and correlates sensor observations and publishes a fused scene plus health. The separate ReactionDecision component combines those outputs with vehicle motion and driver override, then publishes the cluster warning and bounded brake request.
The modeled safety mechanisms require a confirmed collision threat, clamp the brake command, and give driver override priority before the command leaves the cluster.