Linkedin-inYoutube
logotype
  • Consulting
    • Automotive
      • Functional Safety
      • Cybersecurity
      • Autonomous Product Development
      • Electric Vehicle (EV) Development
    • Physical AI
      • Robotics Safety
    • Responsible AI
      • Responsible Artificial Intelligence
  • Training
    • Functional Safety
    • Cybersecurity
    • ADS and Responsible AI
  • Company
    • Why SRES Training
    • Leadership
    • Partnerships
    • Careers
  • Insights
  • Contact
Let's Talk
logotype
  • Consulting
    • Automotive
      • Functional Safety
      • Cybersecurity
      • Autonomous Product Development
      • Electric Vehicle (EV) Development
    • Physical AI
      • Robotics Safety
    • Responsible AI
      • Responsible Artificial Intelligence
  • Training
    • Functional Safety
    • Cybersecurity
    • ADS and Responsible AI
  • Company
    • Why SRES Training
    • Leadership
    • Partnerships
    • Careers
  • Insights
  • Contact
Let's Talk
  • Consulting
    • Automotive
      • Functional Safety
      • Cybersecurity
      • Autonomous Product Development
      • Electric Vehicle (EV) Development
    • Physical AI
      • Robotics Safety
    • Responsible AI
      • Responsible Artificial Intelligence
  • Training
    • Functional Safety
    • Cybersecurity
    • ADS and Responsible AI
  • Company
    • Why SRES Training
    • Leadership
    • Partnerships
    • Careers
  • Insights
  • Contact
logotype
logotype
  • Consulting
    • Automotive
      • Functional Safety
      • Cybersecurity
      • Autonomous Product Development
      • Electric Vehicle (EV) Development
    • Physical AI
      • Robotics Safety
    • Responsible AI
      • Responsible Artificial Intelligence
  • Training
    • Functional Safety
    • Cybersecurity
    • ADS and Responsible AI
  • Company
    • Why SRES Training
    • Leadership
    • Partnerships
    • Careers
  • Insights
  • Contact
Short series: documentation
09/28/23
161 Likes

Short series: documentation

Although documentation might be one of the least favorite activities for an engineer, it is extremely critical when we talk about safety, security and responsible AI. In some cases there are regulatory requirements, or in other cases a customer my require assessments. Assessors and auditors look for good documentation. High quality documentation is also important, so that we are driving actual outputs that support our activities.

Transcript (auto-generated)

I’m Jody Nelson at SRES Shorts and I’d like to discuss a little bit about documentation. I know for us engineers that’s like fingernails on a chalkboard for us because all we want to do is develop something, create something that we can touch and feel and see move. However, documentation, we talked about safety, security, responsible AI, is extremely critical. In some cases we’ll have regulations around documentation. Other cases we’ll have customers requiring external assessments, for example. We may have internal auditors reviewing our work. We need to create argumentations of why we think our product is safe, or why we think it’s secure, or why we believe we’ve been responsible when developing AI.

All these aspects have to be considered. And to do so, we need some kind of tool set. We need some kind of processes. In most cases, we can use whatever corporate tools that we’re already using. In other cases when we don’t have appropriate tools we should be discussing with our management or upper management to get these tools inside of the company. Now we do know a lot of assessors that we’ve worked with in the past really have a high level of focus on how we document things. When they see sloppy documentation things are located all over the place it looks like we’re scattered looks like we don’t know what we’re doing it looks like we’re not safe although the truth of it could be we are very safe underneath it but the appearance says a lot so it’s very critical that we create good documentation and don’t document just for documentation sake we should be creating high quality documents when we do safety analysis it’s just not to get a file to put into a folder to check a box.

That safety analysis should drive a safer product. It should find any kind of gaps we have in that product or it should argue why now this is why we believe we’re safe because look, we did the safety analysis and we don’t have any gaps. So, documentation overall is extremely critical in our development with safety, security, and responsible AI.

Short series: safety analysis (FMEA)

Short series: safety analysis (FMEA)

09/29/23

Short series: we want to hear from you

09/27/23
Short series: we want to hear from you

Insight Categories

  • Autonomous Systems18
  • Electric Mobility3
  • News11
  • Videos11
  • Functional Safety31
  • Responsible AI21
  • Cybersecurity5
Most Recent
  • CES Wrap-Up 2026: The Humanoid Robot Safety Question
    CES Wrap-Up 2026: The Humanoid Robot Safety Question
    01/15/26
  • Conversations on Randomness of Software
    Conversations on Randomness of Software
    12/16/25
  • ISO 26262 Edition 3: Part 3 and Part 4 – Item and System Level
    ISO 26262 Edition 3: Part 3 and Part 4 – Item and System Level
    12/10/25
  • Humanoid Robot Safety Comes Into Focus
    Humanoid Robot Safety Comes Into Focus
    11/25/25
  • The Governance Gap: Why Companies That Move Fast on AI Without Guardrails End Up Moving Slower
    The Governance Gap: Why Companies That Move Fast on AI Without Guardrails End Up Moving Slower
    12/09/25
logotype
  • Company
  • Careers
  • Contact Us
  • info@sres.ai
  • 358 Blue River Pkwy Unit
    E-274 #2301 Silverthorne,
    CO 80498

Services

Automotive

Physical AI

Responsible AI

Training

Resources

Insights

Video

Legal

Privacy Policy
Cookie Policy
Terms & Conditions
Training Terms & Cancellation Policy
Accessibility
Consent Preferences

© Copyright 2025 SecuRESafe, LLC. All rights reserved.

Linkedin Youtube