As organizations pursue ASPICE compliance, verification activities often become increasingly requirement-centric, resulting in repetitive test execution, duplicated data collection and extensive use of costly validation resources. This presentation introduces architecture-based testing, an innovative methodology that separates test execution and data acquisition from requirement verification. By treating captured test data as reusable verification evidence, a single test campaign can support multiple independent requirement assessments while maintaining full traceability and compliance. The approach improves failure isolation, reduces test bench utilization, accelerates debugging and enables scalable, automation-ready verification architectures. A real-world automotive electrification case study demonstrates the benefits and implementation strategy.

• Why traditional ASPICE can unintentionally create repetitive testing, duplicated data collection and inefficient use of validation resources
• How architecture-based testing separates physical test execution from requirement verification to reduce redundancy while preserving traceability
• How reusable test data can support multiple independent requirement assessments from a single test campaign
• How the approach improves failure isolation, preventing one failed verification step from incorrectly failing multiple linked requirements
• How this method enables scalable, automation-ready verification for complex electrification platforms and product variants