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
RuleFindingsFindings without filed issue
HIGH descriptionDefinedInDesignPackage Design entity has no required description00
HIGH designChildrenBoundary Design contradicts the element's bottom-level declaration00
HIGH designChildrenParent Design lists a child with a different parent00
MODERATE designClassInstance Design class has no instance property in its file00
MODERATE designClassPascalCase Design class name violates PascalCase00
MODERATE designClassesTopLevel Design class is nested inside another declaration00
HIGH designElementDefined Design has no subject element00
MODERATE designObjectCamelCase Design instance name violates camelCase00
MODERATE forbiddenWordsInDesign Design entity contains forbidden wording00
HIGH nameDefinedInDesignPackage Design entity has no required name00
HIGH nonDesignEntityInDesignPackage Entity uses the wrong viewpoint package (Design)00
HIGH safetyMeasureAsilDefined Safety measure has no ASIL00
HIGH safetyMeasureMustLiveInDesign Safety measure lacks a containing design00
HIGH safetyMechanismAsilDefined Safety mechanism has no ASIL00
HIGH INFO safetyMechanismAsilExceedsElement Safety mechanism exceeds its element's ASIL00

More complete diagnostic records and evidence are available locally on the build machine (not published), at repository-relative path subsystems/robot-computer/build/docs/com.example.stig.subsystems.robot-computer--model-check-results.json.

Static decomposition

The robot application is the computer's modeled child and runs on its computing platform of SoC, memory, storage, Linux and ROS 2.

flowchart LR
subgraph computer["robotComputer<br/>«Subsystem»"]
application["robotApplication<br/>«Cluster»"]
end

Child context: robotApplication.

Functions and interactions

Camera images enter the computer's input_stream, reach the application's ROS 2 subscription, and lead to a published brake_request passed back through the computer boundary.

flowchart LR
subgraph computer["robotComputer<br/>«Subsystem»"]
direction LR
inputStream["inputStream<br/>«Event»"]
subgraph application["robotApplication<br/>«Cluster»"]
direction LR
applicationInput["inputStream<br/>«Subscriber»"]
applicationOutput["brakeRequest<br/>«Publisher»"]
applicationInput --> applicationOutput
end
brakeRequest["brakeRequest<br/>«Event»"]
inputStream -->|input_stream| applicationInput
applicationOutput -->|brake_request| brakeRequest
end

Types

Link copied to clipboard
class RobotComputerDesign : Design

Deployment of the obstacle-stop application on the computing platform.

Properties