Package-level declarations
Design Check Results
All severities: 0 total / 0 without filed issue · Critical: 0 total / 0 without filed issue · High: 0 total / 0 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 | 0 | 0 |
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 items/delivery-robot/build/docs/com.example.stig.items.delivery-robot--model-check-results.json.
Static decomposition
The delivery robot contains two modeled systems: the robot control unit observes obstacles and requests braking, while the drive unit brings the robot to rest.
flowchart LR
subgraph robot["deliveryRobot<br/>«Item»"]
direction LR
control["robotControlUnit<br/>«SystemElement»"]
drive["driveUnit<br/>«SystemElement»"]
endContent copied to clipboard
Child contexts: robotControlUnit and driveUnit.
Functions and interactions
The physical obstacle input passes through the control unit's observation and CAN brake_request path to the drive unit, whose physical stopping action produces the robot's stoppedMotion output.
flowchart LR
subgraph robot["deliveryRobot<br/>«Item»"]
direction LR
obstacleInPath["obstacleInPath<br/>«Event»"]
subgraph control["robotControlUnit<br/>«SystemElement»"]
direction LR
controlInput["obstacleInPath<br/>«Event»"]
controlOutput["brakeRequest<br/>«Message»"]
controlInput --> controlOutput
end
subgraph drive["driveUnit<br/>«SystemElement»"]
direction LR
driveInput["brakeRequest<br/>«Message»"]
driveOutput["stoppedMotion<br/>«Event»"]
driveInput --> driveOutput
end
stoppedMotion["stoppedMotion<br/>«Event»"]
obstacleInPath --> controlInput
controlOutput -->|CAN brake_request| driveInput
driveOutput --> stoppedMotion
endContent copied to clipboard