TCL #745
AlexanderLanin
started this conversation in
Operational Community
TCL
#745
Replies: 1 comment
-
|
Where to document? Option 1: next to the tool 🎏
Option 2: Central list
Option 3: when used
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Public source: https://www.embitel.com/blog/embedded-blog/why-is-software-tool-qualification-indispensable-in-iso-26262-based-software-development
Editable link: https://excalidraw.com/#json=X5XGWm54x5c5zMVPd5M5N,JXYTSX4t0ltCcvgjN3RzEQ
Q&A
Q: What does it mean 'Chance of error being detected' ? By who, humans, the tool?
A: Anyone. This includes humans and (other) tools. e.g. compilers will detect when code generators generate gibberish.
Q: How does one classify the tool confidence (TCL1,2,3)?
A: See image above.
Q: What qualifies as a 'tool' in this context?
A: Every single line of code written (shell scripts, bazel scripts, python scripts, external tools, ...). With a reasonable abstraction level!
Q: What do we need to document, where and how?
A: Process team will provide templates during 2025. Infrastructure team should contribute - specifically to the where and how.
Beta Was this translation helpful? Give feedback.
All reactions