Standards and Software Processes
AUTOSAR, ISO 26262, ASPICE, cybersecurity, UNECE R155/R156 and OTA lifecycle.
Related records are ordered by brand and name.
From vehicle to technical value: model, generation, engine and transmission identity matrix
Explains how model family, generation, chassis, market, engine code, transmission code and controller software connect to one technical record.
Automotive SPICE
Assessment of automotive system and software development processes through capability, traceability and continual improvement.
AUTOSAR Adaptive Platform
A platform approach for vehicle computers that require high processing power, service-oriented communication and dynamic software lifecycles.
AUTOSAR Classic Platform
Standardised application components, RTE and basic software layers for resource-constrained, real-time embedded ECUs.
ISO 26262 functional safety
Hazard analysis, ASIL, safety goals, architectural mechanisms and verification for automotive electrical and electronic systems.
OEM ECU software development lifecycle
The path from system requirements and architecture through coding, calibration, integration, vehicle testing and production release management.
OTA and software version management
Remote packaging, dependency control, secure deployment, rollback and fleet tracking of vehicle software.
UNECE R155/R156 and vehicle cybersecurity
Cybersecurity and software-update management systems, risk assessment and lifecycle evidence.
V-model and automotive validation
Traceability between requirement levels and the corresponding unit, integration, system and vehicle tests.
Move from vehicle class to technical system
After choosing brand and model identity, use engine, transmission, DTC, electronics and service guidance in the same technical context.
Sources & freshness
Exact technical values, prices and failure rates are not invented without verified vehicle/manufacturer evidence.