DO-178C

Articles, guides, and products tagged "DO-178C" — a combined view of every catalogue resource on this topic.

User guide

E-scooter Configuration Management engineering as the 34th engineering axis: configuration-discipline meta-axis — ISO 10007:2017 + IEEE 828:2012 + SAE EIA-649C + DO-178C SCM + ISO 26262-8 + ITIL 4 + CMMI v2.0 + NIST SP 800-128

Engineering deep-dive into configuration management (CM) engineering as the 34th engineering axis and 7th process meta-axis. Describes the systematic discipline that answers the question "what exactly is installed in this specific physical and digital product at this specific moment, how do we know, how can we change it under control, and how can we prove it after the fact?" Covers: ISO 10007:2017 *Quality management — Guidelines for configuration management* (non-prescriptive guidance above all other CM standards, aligned with ISO 9001:2015); IEEE 828-2012 *Standard for Configuration Management in Systems and Software Engineering* (minimum requirements for CM processes, CM Plan structure, life-cycle integration); SAE EIA-649C:2019 *Configuration Management Standard* (5 CM functions + 37 principles, national consensus standard); SAE EIA-649-1A:2020 *Configuration Management Requirements for Defense Contracts*; DO-178C airborne software SCM (Section 7 + Table A-8 with 6 SCM objectives applicable to software levels A/B/C/D); ISO 26262-8:2018 automotive functional-safety supporting processes (clause 7 configuration management + clause 8 change management + clause 9 verification + clause 10 documentation); ITIL 4 *Service Configuration Management* practice + CMDB (Configuration Management Database) + CMS (Configuration Management System); CMMI v2.0 *Configuration Management* practice area (2 capability levels); NIST SP 800-128 *Guide for Security-Focused Configuration Management of Information Systems* (SecCM); MIL-STD-973 (cancelled 2000) + MIL-STD-3046 (interim, US Army); ISO/IEC/IEEE 24765:2017 vocabulary; CM principal artifacts (CMP / configuration item / configuration baseline / change request / CCB / SCAR / FCA / PCA); CM concepts (identification / change control / status accounting / verification + audit / build management / release management); e-scooter-specific concerns (firmware versioning of BMS + ESC + display controller + companion app + OTA-update integrity; BOM revisions + part interchangeability matrix; serial number / lot number → BOM revision lookup; recall management workflow per NHTSA + EU Safety Gate + UK PSD; TSB (Technical Service Bulletin) lifecycle; software bill of materials SBOM per NTIA + EO 14028 + EU CRA Annex I § 1.2.f). A 33-row cross-axis matrix maps the CM concept to each of the 33 prior engineering axes (battery cell lot traceability + brake-pad compound revision + motor stator winding revision + tire compound revision + EMC pre-compliance vs production unit + cybersecurity firmware signing + DPIA-relevant data-processor changes + V&V test-report revision); 8-step DIY owner CM "tells" checklist (firmware-version visibility in display/app + serial-number sticker location + BOM revision letter on the PCB silkscreen + recall lookup via VIN/serial + service-manual revision date + warranty BOM verification + change-log discipline for OTA updates + spare-part interchangeability documentation).

15 min read

User guide

E-scooter functional safety engineering: safety integrity as the sixth cross-cutting infrastructure axis — IEC 61508:2010 (E/E/PE safety-related systems, SIL 1-4) + ISO 26262:2018 (automotive FuSa, ASIL A-D) + ISO 13849-1:2023 (safety-related parts of machinery, PLr a-e, Cat B/1/2/3/4) + IEC 62061:2021 (SIL CL for machinery E/E/PES) + EN 17128:2020 Annex G (PLEV functional safety requirements) + IEC 60812:2018 FMEA + IEC 61025:2006 FTA + IEC 61709:2017 reliability data + MISRA C:2023 software safety subset + ISO/PAS 21448:2022 SOTIF + IEC 61511 process industry + IEC 60730-1:2024 controls + UL 991 + UL 1998 + DO-178C analogy

Engineering deep-dive into e-scooter functional safety as the sixth cross-cutting infrastructure axis — parallel to [fastener/joining](@/guide/fastener-and-bolted-joint-engineering.md), [thermal management/heat-dissipation](@/guide/thermal-management-engineering.md), [EMC/EMI/interference-mitigation](@/guide/emc-emi-engineering.md), [cybersecurity/interconnect-trust](@/guide/cybersecurity-engineering.md), and [NVH/acoustic-vibration-emission](@/guide/nvh-engineering.md). Covers: 10-row standards matrix (IEC 61508, ISO 26262, ISO 13849-1, IEC 62061, EN 17128 Annex G, IEC 60812 FMEA, IEC 61025 FTA, IEC 61709, MISRA C, ISO/PAS 21448 SOTIF); SIL/ASIL/PL/SIL CL cross-mapping; 6-row hazard-by-subsystem matrix (motor controller throttle-stuck, brake actuator loss, throttle position drift, BMS thermal runaway, display HMI critical info, lighting fail-dark); FMEA worked example for BLE throttle injection scenario; FTA worked example for wheel lock at speed; FMEDA with PFD/PFH calculation, Safe Failure Fraction, Hardware Fault Tolerance; risk reduction equation R_residual = R_unmitigated × (1 - RRF); 6-row mitigation matrix; ALARP principle; software safety V-model + MISRA C:2023 + formal methods; SOTIF (ISO/PAS 21448) as extension to IEC 61508; HIL testing + fault injection; 8-row real-incidents timeline (Lime brake recall 2019, Ninebot ES2 throttle creep 2020, Apollo Pro firmware bug, Boosted board fire, Bird scooter rear-wheel hub crack, Tier scooter motor-stuck); 8-step DIY safety check; 6-step DIY remediation; industry shift 2020→2026; 16 numbered sections.

17 min read

User guide

Software and firmware engineering for embedded ECUs of an electric scooter as the 29th engineering axis: UN R156 SUMS + ISO/SAE 21434 + Automotive SPICE 4.0 + MISRA C:2023 + ISO 26262-6:2018 + AUTOSAR Classic R23-11 + ISO/IEC/IEEE 12207:2017 + ISO/IEC/IEEE 29148:2018 + ISO/IEC 25010:2023 + CISA SBOM Minimum Elements + CWE/CVE + CVSS v4.0

Engineering deep-dive into software & firmware engineering as the 29th engineering axis and the twelfth cross-cutting infrastructure axis — describes how firmware of e-scooter embedded ECUs (motor controller + BMS + dashboard + IoT gateway + charger MCU) is developed under MISRA C:2023, validated through the Automotive SPICE 4.0 V-model + SWE.1–SWE.6 + SYS.1–SYS.5 + HWE.1–HWE.4 + MLE.1–MLE.4, OTA-updated under UN R156 SUMS (L-category mandate: Dec 2027 new types / June 2029 existing types), traced through the ISO/IEC/IEEE 12207:2017 software lifecycle's 30 processes in 4 groups (Agreement + Organizational Project-Enabling + Technical Management + Technical), documented via SBOM per CISA Minimum Elements 2025 (Supplier + Component + Version + Unique-IDs + Dependencies + Author + Timestamp + Hash + License + Tool + Generation-Context) in SPDX 2.3 and CycloneDX 1.6 formats, versioned through the ISO/IEC 25010:2023 product quality model's 8 characteristics, qualified at the toolchain level per ISO 26262-8 Clause 11 (TCL1/TCL2/TCL3 + TD1/TD2/TD3), and monitored through CWE Top 25 + CVSS v4.0 (Base + Threat + Environmental + Supplemental). 18 numbered sections.

15 min read

User guide

E-scooter Verification & Validation (V&V) engineering as the 33rd engineering axis: verification-validation meta-axis — IEEE 1012:2016 + ISO/IEC/IEEE 29119 + 12207:2017 + 15288:2015 + IEEE 730 + 1028 + V-Model + W-Model + Boehm 1979 + IV&V + ISO 26262-8 + DO-178C

Engineering deep-dive into V&V (verification & validation) engineering as the 33rd engineering axis and 6th process meta-axis. Describes the systematic methodology for answering Boehm's 1979 two questions — verification ("Are we building the product right?" — does it conform to the requirements and specs) and validation ("Are we building the right product?" — does it satisfy real-world user need) — across all other axes. Covers: IEEE 1012:2016 *Standard for System, Software, and Hardware Verification and Validation* (V&V life-cycle processes for systems + software + hardware; integrity levels 1-4 with risk-graduated rigor; aligned with ISO/IEC/IEEE 15288:2015 + 12207:2017); ISO/IEC/IEEE 29119 family — a five-part testing standard (Part 1:2022 concepts/definitions; Part 2:2021 test processes; Part 3:2021 test documentation, replacing IEEE 829-2008; Part 4:2021 test techniques; Part 5:2024 keyword-driven testing); ISO/IEC/IEEE 12207:2017 software life-cycle V&V; ISO/IEC/IEEE 15288:2015 system life-cycle V&V; IEEE 730:2014 SQA Plan; IEEE 1028:2008 software reviews + audits with 5 types (management, technical, inspection, walk-through, audit) + Fagan inspection IBM 1976 origin; V-Model (Forsberg-Mooz 1991 + Boehm refinement; left-side requirements/design + right-side V&V mirror); W-Model (extension with V&V activities in parallel with development); Boehm 1979 verification-vs-validation seminal distinction; IV&V (Independent V&V) per IEEE 1012 with 3 independencies (technical + managerial + financial); test coverage criteria (statement, branch, decision, MC/DC, path); mutation testing DeMillo-Lipton-Sayward 1978; ISO 26262-8:2018 clause 9 verification of safety requirements + clause 10 software verification; DO-178C software considerations in airborne systems with 5 software levels A-E; traceability matrix RTM requirements → design → code → tests; risk-based testing ISO/IEC/IEEE 29119-2:2021 cross-link to risk-management EV; defect taxonomies; TMMi 5 levels. A 32-row cross-axis matrix maps the V&V concept to each of the 32 prior engineering axes (battery cycling chamber test + brake dyno + motor torque-loop verification + tire UNECE R75 validation + EMC chamber + IP-spray chamber + cybersecurity pen-test + functional-safety HiL); 8-step DIY owner V&V "tells" checklist (test reports availability + certification body + independent test lab marks + manufacturer field-issue track-record + traceability between datasheet specs and actual measurements).

15 min read