Automotive & Mobility

V-Model Testing, ASPICE & Functional Safety

Verification and validation across the full V-Model — MIL, SIL and HIL testing, structural coverage, ASPICE process capability and ISO 26262 functional safety work products.

Overview

Every left-hand branch gets a right-hand one

Part of our Automotive & Mobility Engineering practice.

The V-Model is not paperwork. Its point is simple: every specification activity on the left has a matching verification activity on the right, and if one is missing you find out late and expensively.

We staff both sides — reviewing requirements for testability before they are baselined, building the rigs and automation that verify them, and producing the safety and process evidence an assessor will actually accept.

Capabilities

What we deliver

MIL / SIL / HIL testing

Model-, software- and hardware-in-the-loop environments on dSPACE, Vector and NI platforms. Restbus simulation, plant models, fault injection and automated overnight regression.

Test strategy & architecture

Master test plan, level definitions, entry and exit criteria, and traceability from requirement to test case to result in Polarion, DOORS or Codebeamer.

Structural coverage

Unit and integration testing with statement, branch and MC/DC coverage scaled to the ASIL of each component, using VectorCAST, Tessy or Cantata.

ASPICE process capability

Gap assessment against Automotive SPICE 4.0, process definition and template packs, and coaching across SYS.1–SWE.6 plus the SUP and MAN process areas.

ISO 26262 functional safety

HARA and ASIL determination, functional and technical safety concepts, FMEA, FMEDA, FTA and DFA, and quantitative metrics (SPFM, LFM, PMHF).

Assessment support

Mock assessments, evidence packaging, finding remediation and engineer preparation ahead of an external ASPICE or ISO 26262 assessment.

How we work

A predictable path from first call to handover

No two engagements are identical, but the shape is consistent — so you always know what happens next and what you get at the end of each stage.

Engagement models

Plan

Test strategy, levels, environments and tooling agreed and written down, with coverage targets tied to the risk and ASIL of each component.

Design

Test cases derived systematically — equivalence partitioning, boundary analysis, state and decision coverage — and traced to requirements as they are written.

Execute

Automated runs in CI plus exploratory testing where judgement beats a script. Defects raised with reproduction steps, logs and a measurement trace.

Assess

Coverage, pass rate, defect trend and open-risk reporting, then a mock assessment before the real one.

Outcomes

What changes for you

  • Defects found at the cheapest possible level rather than at system test.
  • Regression suites that run overnight and report before the team logs in.
  • Coverage and traceability evidence that satisfies ASPICE SWE.4/SWE.5 and ISO 26262.
  • A release decision based on data instead of optimism.

Tools & standards

What we work with

  • dSPACE SCALEXIO
  • Vector CANoe / vTESTstudio
  • NI TestStand / VeriStand
  • VectorCAST
  • Tessy
  • Cantata
  • Polyspace
  • Automotive SPICE 4.0
  • ISO 26262
  • ISO 21448 (SOTIF)
  • IBM DOORS
  • Polarion
  • Codebeamer
  • medini analyze

Questions

Frequently asked

Can you set up a HIL rig from scratch?

Yes — requirements, hardware selection, restbus and plant model configuration, test case migration and operator training.

How long does an ASPICE uplift take?

Realistically six to nine months to move a team from ad-hoc to a defensible Level 2 across the core process areas. A gap assessment in the first three weeks gives you a firm number.

Do you test non-automotive software too?

Yes. The same discipline transfers to medical and industrial software, and our enterprise QA work sits with the Web and Cloud pillar.

Let’s scope your next build.

Tell us what you are trying to ship. We will come back with an approach, a team shape and an honest estimate — we aim to reply within two working days.