Skip to content
03 · Embedded SW practice

Model-based + handwritten C/C++ for safety-critical ECUs.

Our founder introduced Model-Based Development at Siemens-VDO in 2001 and later co-built a commercial formal-methods verification toolchain. Model-based systems engineering in SysML and UML, with IBM Rhapsody (Harmony method) and Sparx Enterprise Architect, ties requirements to executable architecture. Today STS delivers MISRA-clean, AUTOSAR-conformant embedded software with the V&V evidence required for ASPICE CL2 / CL3 and ISO 26262 ASIL-D.

Stack baseline
Matlab · Simulink · Stateflow TargetLink · Embedded Coder Formal verification · model checking · back-to-back testing AUTOSAR Classic + Adaptive Vector CANoe · CANalyzer dSPACE SCALEXIO · HIL DOORS · Polarion · PREEvision · IBM Rhapsody · Enterprise Architect

What we cover

Requirements & architecture (ASPICE SYS.2, SWE.1, SWE.2)

  • System requirements analysis & architectural design (SYS.2 / SYS.3).
  • Software requirements analysis (SWE.1), refinement from system requirements, formalisation, traceability.
  • Software architecture design (SWE.2), static + dynamic views, interface specifications, technical resource dimensioning.

Implementation (SWE.3, model-based + handwritten)

  • Model-based design in Simulink / Stateflow / TargetLink, autocoded with full traceability back to architecture.
  • Handwritten C / C++ for hardware-near, AUTOSAR-BSW, complex device drivers, secure-boot & bootloader code.
  • MISRA C:2012 / MISRA C++:2008 compliance with documented deviation justifications. Static analysis via Polyspace, LDRA, Cppcheck.
  • AUTOSAR Classic configuration (RTE, BSW config) and AUTOSAR Adaptive (POSIX-based, service-oriented).

Verification (SWE.4, SWE.5, SWE.6)

  • SWE.4 Unit testformal verification, model-level + code-level coverage, automatic back-to-back testing.
  • SWE.5 Integration testsoftware unit integration; HIL/SIL/MIL test benches.
  • SWE.6 Qualification testblack-box validation against software requirements; ASIL-graded structural coverage targets.
  • Tool qualification evidence per ISO 26262-8 §11 for any tool we apply to safety-relevant artefacts.

System integration & vehicle-level test

  • HIL integration on dSPACE SCALEXIO racks (we run our own bench in Brașov for development support).
  • Vector CANoe scenarios for bus-level integration testing & diagnostic protocol validation.
  • ASAM/MDF measurement-file analysis for HIL bench recordings & vehicle test results.

Diagnostic services (UDS)

ISO 14229 UDS implementation for safety-relevant ECUs, service catalogue, security access, routine control, data transfer for OTA, calibration access. STS India plus a dedicated UDS delivery partner give us sustained diagnostic capacity.

Embedded SW project, ASPICE CL3 target, or both?

Tell us what you’re shipping and what level of process discipline the customer expects. We’ll know in 30 minutes whether we can plug in.