Title: Confidence in the Use of Software Tools | ISO 26262 Academy URL: https://iso26262.academy/features/concepts/tool-confidence Description: Learn how to classify tools by TCL (1-3) based on Tool Impact, Tool Error Detection, and ASIL requirements. --- Concept guide · ISO 26262-8 §11 · 7 chapters · 1h video # Confidence in the Use of Software Tools Master tool qualification per ISO 26262-8 Clause 11, from TI/TD classification through qualification method selection to complete evidence packages, with 1 hour of video, a full GCC compiler walkthrough and 10 worked tool examples. 7 Chapters 6 Flowcharts & Diagrams 10 Tool Examples 1h Video Included in Pro Expert [Start learning](https://iso26262.academy/register?plan=free&from=%2Fconcepts%2Ftool-confidence&utm_source=website&utm_medium=cta&utm_campaign=features_concepts) See the chapters Course intro · 3 min Free preview A 3 min look inside the course. 1 hour of course videos for registered users. The short version ## Quick answers What is Tool Confidence Level (TCL) in ISO 26262? Tool Confidence Level (TCL) is a classification from TCL1 to TCL3 that determines whether and how rigorously a software tool must be qualified for use in safety-related development. TCL is derived from two parameters: Tool Impact (TI1 or TI2) and Tool error Detection (TD1, TD2, or TD3). TCL1 means no qualification is needed, TCL2 requires qualification with moderate rigor, and TCL3 requires the highest qualification effort. The classification is defined in ISO 26262-8:2018 Clause 11. What is the difference between TI1 and TI2 in tool classification? Tool Impact (TI) assesses whether a tool malfunction can introduce or fail to detect errors in safety-related work products. TI1 means the tool cannot introduce errors or fail to detect them (e.g., a text editor, debugger). TI2 means the tool can introduce or fail to detect errors that could violate a safety requirement (e.g., a compiler generating incorrect code, a test tool missing a failure). Only TI2 tools require further TD analysis and potential qualification. Keep going, free - [Article · 8 min read Confidence in Software Tools: A Guide to ISO 26262 Qualification](https://iso26262.academy/blog/confidence-in-software-tools-a-guide-to-iso-26262-qualification) - [Article · 8 min read Evaluating Software Tools in ISO 26262: A Practical EPS Example](https://iso26262.academy/blog/evaluating-software-tools-in-iso-26262-a-practical-eps-example) - [Demo exam · no account Test yourself with 7 exam-style questions](https://iso26262.academy/demo-exam) A practical sample · no account needed ## How is confidence in a software tool assessed? Tool confidence assessment considers whether a tool malfunction could introduce or fail to detect an error, and how confidently such an error would be detected or prevented. The assessment depends on the tool’s intended use in a specific workflow. The same code generator is used in two projects. One project independently checks its output; the other accepts the output without that check. Can you copy the confidence assessment solely because the tool version matches? **Reveal the reasoning** No. Intended use and error-detection measures differ. Document the workflow, evaluate tool impact and tool error detection, then determine the applicable confidence level and qualification measures. Illustrative learning example, not a project assessment. ISO 26262, Part 8, Clause 11 · [About the academy](https://iso26262.academy/about) This example is public. A free account gives you access to the full videos for this topic; the written guide follows the plan access shown above. Why this course · ISO 26262, Part 8, Clause 11 ## Why it pays for itself ### Stop guessing your TCL The TI/TD/TCL decision flowcharts turn "do we need to qualify this tool?" from a week of committee meetings into a defensible 30-minute classification. ### Evidence your assessor accepts Learn exactly which artifacts a qualification package needs - classification rationale, validation records, usage constraints - before the functional safety assessment asks for them. ### Reuse instead of redo 10 worked tool examples (GCC, Simulink, TargetLink, VectorCAST, Polyspace...) give you a starting point that matches the tools already in your pipeline. After the course ## What you’ll be able to do ### Classify Tools with TI/TD/TCL Determine Tool Impact, Tool error Detection, and Tool Confidence Level using the ISO 26262-8 classification framework and decision flowcharts. ### Select Qualification Methods Choose the right qualification method (1a-1d) based on TCL, ASIL, and practical constraints using ISO Tables 4 and 5. ### Qualify Compilers & Code Generators Execute a complete qualification for safety-critical tools like GCC, Simulink, and TargetLink with proper evidence packages. ### Handle Tool Chains Qualify interconnected tool chains with interface testing, end-to-end validation, and individual tool assessment strategies. ### Manage Requalification Identify requalification triggers and apply evidence reuse strategies when tools, environments, or usage patterns change. ### Apply Across Standards Map tool qualification concepts across IEC 61508, EN 50128, and DO-178C for cross-domain safety projects. The curriculum · 7 chapters ## Chapter by chapter 1. 01 **Standard Requirements** Understand what ISO 26262-8 Clause 11 requires: purpose, scope, when it applies, the TI/TD/TCL matrix, prerequisites, documentation items, and RACI responsibilities. - TCL matrix - RACI table - Documentation checklist 2. 02 **Process & Roles** Follow the 4-phase qualification process (Planning, Classification, Execution, Documentation) with timing estimates, role definitions, tool prioritization, and the detailed 11-step workflow. - 4-phase process - 11-step workflow - Role definitions 3. 03 **Tool Classification** Master TI (Tool Impact), TD (Tool error Detection), and TCL determination with interactive decision flowcharts, tool registration, classification review, and compiler malfunction classes. - TI decision tree - TD flowchart - TCL classification flow 4. 04 **Qualification Methods** Explore all four qualification methods per ISO Tables 4 and 5, vendor kits, advanced techniques, V-Model integration, Agile adaptation, tool chain qualification, and requalification triggers. - V-Model diagram - Tool chain pipeline - COTS vs in-house 5. 05 **Practical Guidelines** Real-world guidance for Cloud/SaaS tools, four common pitfalls to avoid, and how to qualify self-programmed tools and scripts with proper TI/TD analysis. - Cloud/SaaS guidance - 4 pitfalls - Script qualification 6. 06 **Worked Examples** Walk through a complete GCC compiler qualification from TI/TD analysis to documentation. Explore 10 detailed tool examples including Simulink, VectorCAST, Polyspace, and dSPACE TargetLink. - GCC walkthrough - 10 tool examples - Tool chain flow 7. 07 **Beyond ISO 26262** Compare tool qualification across safety standards: IEC 61508, EN 50128 (railway), and DO-178C (aerospace). Explore cross-standard mapping and validation record requirements. - Cross-standard table - IEC 61508 mapping - Validation records Flowcharts & Diagrams ## Not just text: the visual toolkit ### TI Classification Decision Tree SVG flowchart with decision diamonds guiding you through Tool Impact analysis to determine TI1 or TI2 classification. ### TD Assessment Flowchart Score-based SVG assessment aid with three questions to determine TD1, TD2, or TD3 classification for tool error detection. ### TCL Classification Flow Complete SVG diagram showing the full path from tool collection through TI/TD analysis to TCL determination and qualification method selection. ### V-Model Tool Integration Large SVG V-Model diagram showing 9 development and verification phases with specific tools mapped to each stage (DOORS, Simulink, GCC, CANoe, etc.). ### Tool Chain Pipeline Visual tool chain flow from requirements through code generation and compilation to testing, with TCL-colored classification badges at each stage. ### GCC Qualification Walkthrough Expandable 5-phase worked example with clickable process step modals showing detailed inputs, outputs, and GCC-specific context at each step. Worked Examples ## 10 Real-World Tool Qualifications Each tool example includes complete TI/TD analysis, TCL determination, qualification strategy, required artifacts, coverage targets, and effort estimates. - GCC/LLVM Compiler: full 5-phase qualification walkthrough (TCL3) - MATLAB/Simulink and dSPACE TargetLink code generation (TCL3) - Polyspace Code Prover and VectorCAST test tools (TCL2) - Vector CANoe integration and communication testing (TCL2) - Git, Jira, and Lauterbach TRACE32 tool chain (TCL1) GCC Compiler Qualification Phase 1: Tool Impact Analysis → TI1 (direct output influence) Phases 2-5 in course Built for ## Who this guide is for - Engineers who just inherited "tool qualification" as a side duty - Safety managers planning a qualification budget for a tool chain - Software leads introducing a compiler, code generator, or test tool into an ASIL project - Anyone facing an assessor question about TCL classification evidence ## Frequently Asked Questions Common questions about Confidence in the Use of Software Tools ISO 26262-8 defines four qualification methods: Method 1a (Increased Confidence from Use) relies on proven field experience and usage history. Method 1b (Evaluation of the Tool Development Process) assesses whether the tool was developed following a suitable quality process. Method 1c (Validation of the Software Tool) performs targeted testing of tool functionality relevant to safety. Method 1d (Development in Accordance with a Safety Standard) requires the tool to be developed per a recognized safety standard. The applicable methods depend on TCL and ASIL per ISO Tables 4 and 5. A compiler like GCC is typically classified as TI2 (since compiler errors can introduce faults in generated code) with TD3 (since compiler errors are difficult to detect without specific measures), resulting in TCL3 (highest qualification level). Qualification typically combines Method 1c (targeted validation testing of compiler features used in the project) with Method 1a (field experience from widespread use). Key activities include defining the exact compiler version and flags, identifying failure modes, creating validation test suites, and documenting usage constraints. The course walks this end to end in a 5-phase worked example. The course includes 1 hour of video that is available to registered users as part of the free-videos program, along with the 3-minute intro on this page. The full 7-chapter guide with flowcharts, worked examples, and quizzes is part of the concept library; a free account starts you off, and the Pro and Expert plans unlock more of the library. ## Start the course today A free account unlocks one full concept guide, 3 work product templates, 1 guided process, the Markov simulator, and 5 practice exams per month - plus 1 hour of course videos for registered users. The Pro and Expert plans unlock more of the 78-guide library. No credit card required. [Start learning](https://iso26262.academy/register?plan=free&from=%2Fconcepts%2Ftool-confidence&utm_source=website&utm_medium=cta&utm_campaign=features_concepts) [View Pricing Plans](https://iso26262.academy/pricing)