Appendix J: Index

This index provides quick access to key topics, tools, and concepts covered throughout the book. Section references use the numbering format (for example, 25.00 refers to the Automotive ECU Development introduction).

A

  • ADAS (Advanced Driver Assistance Systems): 28.00
  • ADR (Architecture Decision Record): 33.03, 99.02
    • Template: 99.02
    • SWE.2 usage: 06.02
  • AI Automation Levels (L0-L3): 01.04, 03.01
    • Level definitions: 99.03
  • AI Code Generation: 06.03, 14.01
  • AI Tool Comparison: 35.04, 99.04
    • Code generation: 99.04
    • Requirements: 99.04
    • Static analysis: 99.04
  • ASIL (Automotive Safety Integrity Level): 25.00, 99.05
    • Coverage requirements: 99.05
    • Mapping to ISO 26262: 99.05
  • ASPICE Capability Levels: 02.03, 12.01
  • ASPICE Process Groups: 02.00
    • Quick reference: 99.03
  • AUTOSAR: 25.00, 25.02

B

  • Base Practices (BP): 02.01, 05.01, 06.00, 11.02
    • AI integration per process: 05.01, 07.01, 11.02
    • Traceability to outcomes: 17.02
  • Baseline Management: 09.03, 13.01, 18.02
    • Configuration management (SUP.8 BP3): 09.03
    • Requirements baselines: 13.01
    • Safety standard requirements: 09.03
  • BMS (Build Management System): 16.00, 16.06
  • Branching Strategy: 09.03, 19.02, 31.00
    • Git workflow: 31.00
    • Release branching: 31.03
    • CI/CD integration: 16.02, 16.03

C

  • Capability Levels (CL0-CL5): 02.03
  • Case Studies: Part V (25-28)
  • CI/CD Pipelines: 16.00, 34.04
  • Clean Code Principles: 34.01
  • clang-format Configuration: 99.01
  • Claude Sonnet: 35.04, 99.04
  • Code Coverage: 06.04, 16.04, 99.05
  • Code Review Checklist: 99.02, 99.06
  • Copilot (GitHub): 14.01, 35.04, 99.01
  • cppcheck Configuration: 99.01

D

  • DO-178C: 99.05
  • DOORS (IBM): 13.01, 99.01, 99.04
  • Doxygen: 99.01

E

  • ECU Development: 25.00
  • Embedded C Coding: 06.03, 34.01

F

  • FMEA (Failure Modes and Effects Analysis): 25.06, 26.01, 27.03
    • AI-assisted generation: 27.03
    • Common cause failure analysis: 25.06
    • Medical device software: 27.03
    • SOTIF integration: 28.02
    • Tool qualification: 18.05
  • Functional Safety: 01.01, 03.04, 21.00
    • Automotive (ISO 26262): 25.00, 21.01, 99.05
    • Engineer qualifications: 03.02
    • Industrial (IEC 61508): 26.00, 21.02
    • Management plan: 03.02
    • Standards mapping: 99.05

G

  • GitHub Actions: 16.02, 31.02, 99.01
  • GitLab CI: 16.03, 31.02, 34.04, 99.01
  • Google Test: 34.02, 99.01

H

  • HARA (Hazard Analysis and Risk Assessment): 25.01
  • Hardware Engineering (HWE): 07.00
  • HIL (Hardware-in-the-Loop): 25.04
  • HITL (Human-in-the-Loop): 03.02, 29.02, 35.03

I

  • IEC 61508: 26.00, 21.02, 99.05
  • IEC 62304: 27.00, 99.05
  • Industrial Controller: 26.00
  • ISO 21448 (SOTIF): 28.00, 28.02
  • ISO 26262: 25.00, 99.05

K

  • Key Performance Indicators (KPIs): 23.04, 11.03
    • ASPICE certification coverage: 23.04
    • Code coverage metrics: 23.04
    • Defect density: 23.04
    • Measurement process (MAN.6): 11.03
    • MISRA compliance rate: 23.04
    • Requirements traceability coverage: 23.04
    • Velocity stability: 23.04
    • Work product completeness: 23.04

L

  • Liability: 04.01, 07.05, 18.05, 29.04
    • AI vendor disclaimers: 29.04
    • Safety manual accountability: 07.05
    • Tool selection impact: 14.00
  • LLM (Large Language Model): 03.00, 03.04, 14.01
    • Code generation: 06.03, 14.01
    • Non-determinism challenges: 03.04, 14.01, 18.05
    • Requirements analysis: 13.02
    • Technology-agnostic design: 04.02
    • Tool qualification: 03.04, 18.05

M

  • Machine Learning Engineering (MLE): 08.00
  • Management Processes (MAN): 11.00
    • See also: MAN.3, MAN.5, MAN.6 in 99.03
  • MC/DC Coverage: 99.05
    • ASIL requirements: 99.05
    • SIL requirements: 99.05
  • Medical Device Software: 27.00
    • IEC 62304 mapping: 99.05
  • MISRA C:2012: 06.03, 34.01, 99.01, 99.05
    • PC-lint configuration: 99.01
    • Checklist: 99.06

N

  • NLP (Natural Language Processing): 13.02, 05.02, 06.00
    • Ambiguity detection: 13.02
    • Quality analysis: 13.02
    • Requirements classification: 13.02
  • Non-Determinism: 03.03, 03.04, 14.01, 18.05
    • Flaky test detection: 15.05
    • LLM output variability: 03.04, 14.01
    • Semantic validation: 03.04
    • Tool qualification challenges: 03.04, 18.05

O

  • ODD (Operational Design Domain): 28.00, 28.02, 28.03
    • Boundary testing: 28.03
    • Definition and scope: 28.00
    • SOTIF integration: 28.02
  • OTA (Over-the-Air) Updates: 05.01, 10.00, 25.02
    • AUTOSAR Adaptive: 13.05, 25.05
    • CI/CD deployment: 16.03
    • Cybersecurity requirements: 10.00
    • Pipeline patterns: 16.06
    • UNECE WP.29: 05.01

P

  • PC-lint Plus: 99.01, 99.04
  • PLC (Programmable Logic Controller): 26.00
  • Process Quick Reference: 99.03
  • Prompt Templates: 32.00, 35.01
  • PyTorch: 28.01

Q

  • Quality Assurance (SUP.1): 09.01, 12.03
    • AI-assisted audits: 09.01, 09.06
    • Checklists: 99.06
    • Continuous compliance: 22.03
    • NLP-based verification: 09.02
    • Process improvement: 12.03
  • Quality Gates: 14.04, 16.00, 18.04
    • ASPICE-compliant configuration: 16.00
    • CI/CD integration: 16.00, 34.04
    • SonarQube configuration: 14.04
    • Static analysis thresholds: 14.04
    • Tool qualification evidence: 18.04

R

  • Requirements Engineering: 33.02
  • Requirements Tools: 13.00
  • Risk Management (MAN.5): 11.02

S

  • Safety PLC: 26.00
  • Safety Standards Mapping: 99.05
    • ISO 26262: 99.05
    • IEC 61508: 99.05
    • IEC 62304: 99.05
    • DO-178C: 99.05
  • Security Processes (SEC): 10.00
    • See also: SEC.1, SEC.2, SEC.3 in 99.03
  • SIL (Safety Integrity Level): 26.00, 99.05
    • Coverage requirements: 99.05
    • IEC 61508 mapping: 99.05
  • SOTIF: 28.02
  • Static Analysis: 14.04, 99.01
    • cppcheck: 99.01
    • PC-lint Plus: 99.01
  • Support Processes (SUP): 09.00
    • See also: SUP.1, SUP.2, SUP.8-10 in 99.03
  • System Engineering (SYS): 05.00
    • See also: SYS.2-5 in 99.03
  • Systems Engineering Mindset: 33.01

T

  • TDD (Test-Driven Development): 34.02
  • TensorRT: 28.03
  • Test Specifications: 99.02
  • Tool Configurations: 99.01
  • Traceability: 13.03, 33.04
  • Traceability Script: 99.01

U

  • UML (Unified Modeling Language): 05.03, 06.02, 13.04
    • Architecture tools: 13.04
    • MBSE platforms: 13.04
    • SWE.2 architectural design: 06.02
    • SysML relationship: 05.03, 13.04
  • Unit Testing: 06.04, 15.00, 34.02
    • AI-generated test cases: 06.04, 15.00
    • Code coverage: 06.04, 15.04, 99.05
    • Google Test framework: 34.02, 99.01
    • SWE.4 unit verification: 06.04
    • TDD approach: 34.02

V

  • V-Model: 01.03, 33.00
  • VectorCAST: 15.01, 99.04
  • Verification (SUP.2): 09.02

W

  • Work Product Templates: 99.02, 20.00
    • Architecture templates: 20.02
    • AI-generated work products: 20.00
    • Completeness KPI: 23.04
    • Process assessment model: 02.02
    • Requirements templates: 20.01
    • Review and report templates: 20.04
    • Sprint work products (Agile): 22.02
    • Test specification templates: 20.03
Previous
Appendix I: Bibliography