ASPICE - Compliant Application Development Use Case
i5 Systems – ASPICE-Compliant Application Development Use Case
This document describes an Automotive SPICE (ASPICE) compliant application development use case delivered by i5 Systems. It outlines the end-to-end workflow, technical architecture, toolchain, compliance mapping, and delivery methodology used to successfully develop and validate an automotive embedded software application for an OEM/Tier-1 customer.
❖ Business Context & Objective
Customer Objective :
- Develop a safety-relevant automotive software application compliant with ASPICE Level 2/3
- Reduce development risk and audit findings
- Ensure traceability, quality, and predictable delivery
i5 Systems Objective :
- Deliver a fully ASPICE-aligned application development lifecycle
- Provide tooling, process definition, execution, and audit-ready evidence
❖ Application Overview
- Application Type Automotive Embedded Control Application
- Target ECU Body Control / Gateway / ADAS Supporting ECU
-
Standards
AUTOSAR (Classic)
ISO 26262 (supporting)
Automotive SPICE v3.1
❖ ASPICE Scope Covered
Primary Process Areas:
- SYS.2 – System Requirements Analysis
- SYS.3 – System Architectural Design
- SWE.1 – Software Requirements Analysis
- SWE.2 – Software Architectural Design
- SWE.3 – Software Detailed Design & Unit Construction
- SWE.4 – Software Unit Verification
- SWE.5 – Software Integration & Testing
- SWE.6 – Software Qualification Testing
- SUP.1 – Quality Assurance
- SUP.8 – Configuration Management
- SUP.9 – Problem Resolution Management
❖ Technical Architecture
Layered Architecture:
- Application Layer - Feature logic, state machines
- Middleware Layer - AUTOSAR RTE, BSW services
- Hardware Abstraction Layer (HAL)
Communication:
- CAN / LIN / Ethernet
- Diagnostic Services (UDS)
❖ Toolchain Used (i5-Delivered)
- Requirements Management M DOORS / Polarion
- Architecture & Design Enterprise ArchitectMATLAB / Simulink
- Implementation EB tresos / DaVinci DeveloperC / Embedded C
- Unit Testing & Verification TESSY (Unit Testing & Coverage)Vector CAST (optional)
- Static Analysis Polyspace / QAC
- Integration & Testing CANoe / CANalyzer
- Configuration & Change Management Git / SVNJIRA
- CI/CD JenkinsPython-based automation scripts
❖ ASPICE-Compliant Workflow
01 Requirement Intake & Analysis (SYS.2 / SWE.1)
- Bidirectional traceability established
02 Architecture Design (SYS.3 / SWE.2)
- Logical & technical architecture baselined
03 Detailed Design & Implementation (SWE.3)
- Coding guidelines (MISRA-C)
04 Unit Testing (SWE.4)
- Automated test execution using TESSY
- Statement, Branch, MC/DC coverage
05 Integration & System Testing (SWE.5 / SWE.6)
- SIL/HIL-based validation
06 Quality Assurance & Reviews (SUP.1)
- Work product reviews and audit preparation
❖ Deliverables Provided
- ASPICE-compliant requirement specifications
- Architecture and design documents
- Source code with version control
- Unit test cases, reports, and coverage evidence
- Integration & qualification test reports
- ASPICE assessment-ready evidence package
❖ Business Value Delivered
- Reduced audit findings
- Faster development cycles via automation
- Improved software quality and coverage
- Audit-ready documentation and traceability
❖ Why i5 Systems
- Proven ASPICE delivery experience
- Strong automotive toolchain expertise
- Scalable offshore-onshore delivery model
- End-to-end ownership