DXCAutomotiveRisk ManagementAI and Machine LearningProductivity ImprovementRisk ReductionSpeed to Market2025DXCDXC#5f249fAutomotiveGermanyCARIAD needed a faster and safer way to validate automated driving functions across large numbers of traffic, weather, and road scenarios, because proving reliability, functional correctness, and regulatory readiness…Apr 16, 20255Risk ManagementstiEF · verification and validation framework02025-04-165
CARIAD needed a faster and safer way to validate automated driving functions across large numbers of traffic, weather, and road scenarios, because proving reliability, functional correctness, and regulatory readiness for automated vehicles is difficult with manual or fragmented testing approaches.
CARIAD made automated-driving validation faster and more collaborative, improved confidence that automated systems behave safely across diverse scenarios, and supported more efficient regulatory-approval work for Volkswagen Group automated driving programs.
Productivity Improvement
Risk Reduction
Speed to Market
Solution
CARIAD and DXC built a verification and validation framework to industrialize testing for Volkswagen Group automated driving functions. The framework creates realistic virtual driving scenarios so engineering teams can test how automated systems behave under varied road, traffic, and weather conditions before vehicles reach the road. A domain-specific language called stiEF gives users a natural-language editor for describing scenarios such as stopping at a red light or reacting to sudden lane changes, and the editor translates those descriptions into visual simulations. This lets development and test teams collaborate on the same scenario definitions instead of working through separate specialist workflows. By turning scenario creation and execution into a repeatable digital process, the platform helps CARIAD validate automated driving behavior faster, improve safety confidence, and make regulatory approval work more efficient.
Data flow
Engineers describe driving situations in the stiEF editor using natural language, and the editor converts those inputs into visual simulations. The verification and validation framework then runs the scenarios against automated driving functions under different traffic, weather, and road conditions so CARIAD teams can review safety and functional behavior before release.
Solution architecture
2 components · 2 layers
Serving
stiEFLets users describe driving scenarios in natural language and converts them into visual simulations for testing.
Orchestration
verification and validation frameworkOrchestrates realistic virtual driving scenarios to test automated driving functions under different operating conditions.
Architecture clues
Scenario coverage explicitly includes traffic, weather, and diverse road conditions.
The framework uses realistic virtual scenarios to test automated driving functions in real time.
The workflow is designed to improve collaboration between development and testing teams.
stiEF is a domain-specific language editor for specifying scenarios in natural language.
Evidence from the source
"The new framework makes software validation faster and more collaborative, enabling the CARIAD teams to iterate quickly and improve system reliability."
"The testing framework uses a domain specific language called stiEF that allows users to specify driving scenarios in natural language through an editor."
"These innovations include a verification and validation framework that makes it easy for engineers to create realistic, virtual scenarios that test how automated systems respond in real-time."
"This editor translates natural language inputs such as 'stopping at a red light' or 'reacting to sudden lane changes' into visual simulations."
"This kind of testing is critical to ensure the technology behaves as expected — not only to meet stringent regulatory standards but also gain end-user trust."
Review how this reference was scored and trace each normalized claim back to its documented source.
01
Scoring methodology
How scores are calculated
Customer Reference Value measures usefulness as a customer reference. Evidence Confidence measures the quality and traceability of available evidence, not independent verification.
Customer reference value75/100
Problem clarity20/20
Measures whether the customer's operational problem is specific enough to compare.
Implementation depth25/25
Rewards named components, data flow, integrations, and architecture detail.
Outcome specificity20/20
Measures whether the reported benefit is concrete rather than a generic claim.
Quantified impact0/25
0 metrics describe measurable impact.
Deployment scale10/10
Rewards evidence of a live or scaled deployment and meaningful integration scope.
Evidence confidence91%
Source authority20/25
The main evidence is an official vendor-published customer story.
Claim traceability23/25
11 of 12 key fields link to a named source.
Direct evidence20/20
5 direct source quotes retained.
Date provenance10/10
The publication date comes from the source page or publisher.
With your OK, we use Google Analytics cookies to see which pages and searches are useful. No ads, no profiling, and
nothing is loaded until you accept. You can change this any time under “Cookie settings” in the footer.