-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add initial material for Telltale analysis #18
base: main
Are you sure you want to change the base?
Conversation
safety-analysis/telltale/README.md
Outdated
|
||
## Purpose and scope | ||
|
||
This section of the repository the OSEP working group's analysis of the Automotive Working Group's [Instrument Cluster use case](https://github.com/elisa-tech/wg-automotive/tree/master/Cluster_Display_Use_Case_v2). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missing a verb - suggest '[...] repository hosts the [...]'
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
* The system boundary is an ECU running an operating system (involving Linux) that is responsible for executing the cluster display and associated processing | ||
* The checking control and safety manager are the safety-relevant components that implement the safety mechanism | ||
* The dashboard manager may also be safety relevant, because it provides the input data to the checking control | ||
* The watchdog may be internal to the ECU or external (future design decision) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggest insertion:
- The question how the Display works with regards to ensuring/making observable that the telltale display, as well as the user notification about potential safety violations, actually performs as expected, is part of a follow-on iteration in the future, as well as another potential system/analysis boundary
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @dakrbo. I've added an extra paragraph - does this capture your points?
Signed-off-by: Paul Albertella <[email protected]>
7a9616f
to
1b53922
Compare
No description provided.