Git

Articles, guides, and products tagged "Git" — 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

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