Acknowledgments


A book of this scope cannot be created in isolation. Many individuals, organizations, and communities have contributed to the knowledge captured here—whether directly or through the foundations they have built.


Standards Bodies and Organizations

The frameworks at the heart of this book exist because of the dedicated work of standards organizations:

VDA QMC (Automotive SPICE)

The German Association of the Automotive Industry Quality Management Center maintains ASPICE, providing the process reference model that structures much of this book. Their work in updating ASPICE 4.0 to include Machine Learning Engineering processes was particularly forward-thinking.

ISO Technical Committees

  • ISO/TC 22 (Road Vehicles) for ISO 26262 Functional Safety
  • ISO/TC 65 (Industrial Automation) for IEC 61508 Integration
  • ISO/SAE 21434 Joint Working Group for Cybersecurity Engineering

intacs (International Assessor Certification Scheme)

For maintaining the assessor certification program that ensures consistent application of ASPICE worldwide.


Open Source Communities

Modern development would be impossible without the open-source communities whose tools power our workflows:

CI/CD Platforms

  • Jenkins Community: For over a decade of continuous integration innovation
  • GitLab: For their integrated approach to DevSecOps
  • GitHub: For democratizing version control and collaboration

Testing Frameworks

  • Unity Test Framework: For enabling rigorous embedded testing
  • Google Test: For C++ testing infrastructure
  • pytest: For Python testing excellence

Static Analysis

  • SonarSource: For SonarQube and quality analysis
  • Clang/LLVM: For analyzer infrastructure
  • Cppcheck: For accessible C/C++ analysis

Documentation

  • Obsidian: For the knowledge management platform that organized this work
  • Markdown Community: For enabling portable, readable documentation

AI Tool Providers

This book extensively covers AI tools. Thanks to the teams building them:

  • Anthropic: For Claude and responsible AI development
  • GitHub/OpenAI: For Copilot and AI-assisted coding
  • Google: For Gemini and AI innovation
  • JetBrains: For AI integration in development tools
  • CodeRabbit, Codacy, SonarQube: For AI-powered code review

Industry Practitioners

The practical guidance in this book draws from the collective experience of thousands of engineers who have implemented these processes in real projects. While individual acknowledgment is impossible, this book stands on the shoulders of:

  • Automotive OEMs and Tier 1 suppliers who pioneered ASPICE implementation
  • Industrial automation companies who bridge IEC 61508 and software practices
  • Medical device manufacturers who navigate complex regulatory requirements
  • Aerospace organizations whose DO-178C practices influenced the field

Professional Network

To the colleagues, mentors, and collaborators who shaped my understanding over the years:

  • Those who challenged me when I was wrong
  • Those who supported me when I was uncertain
  • Those who shared their expertise generously
  • Those who trusted me with their projects

You know who you are. Thank you.


Tools Used in Book Creation

In keeping with the book's themes, the following AI and automation tools were used in its creation:

Tool Use
Claude (Anthropic) Content generation, editing, research
Claude Code Repository management, file operations
Obsidian Knowledge organization and linking
Git/GitHub Version control and collaboration
Draw.io Architecture and flow diagrams
Pandoc + LaTeX PDF generation

A Note on AI Attribution

Some readers may wonder about the ethics of using AI in book creation. My position:

  1. Transparency: I acknowledge AI assistance openly
  2. Responsibility: I take full responsibility for all content
  3. Human Value: AI augmented but did not replace human judgment
  4. Quality Standard: Every section was reviewed, verified, and refined by human expertise

This approach mirrors the HITL (Human-in-the-Loop) patterns advocated throughout the book. AI is a tool; the human remains responsible.


Supporting the Community

A portion of any proceeds from this book will be contributed to:

  • Open-source projects used in development
  • Engineering education initiatives
  • Safety engineering professional development