Sign inCreate free account

Industries

Requirements traceability for automotive systems and functional safety

An automotive team can trace a safety goal down through functional and technical safety requirements to hardware and software requirements and their tests in OpenV, and see which have no test or no result. An attribute on each requirement holds its ASIL. OpenV does not run a hazard analysis and risk assessment or check an ASIL decomposition, so those stay in the method and tool you use for them.

Updated by Desktop Machine Shop, the makers of OpenV.

What these teams keep

ISO 26262 asks for safety goals from the hazard analysis, refined into functional and technical safety requirements and then into hardware and software requirements, each traceable and each verified. Automotive SPICE assesses the same chain from the process side: requirements at system and software level, bidirectional traceability, and consistency between the levels.

Where it goes in OpenV

  • Hazards are their own artifact type. Design items mitigate them, and a hazard nothing mitigates is on the gap list.
  • Requirements link to the requirement they derive from or refine, so a safety goal can be followed to every requirement under it.
  • A project defines its own attributes, so ASIL, variant or responsible supplier is a field on each requirement that filters and exports with it.
  • The traceability matrix and seven gap reports show what has no parent, no test or no passing result.
  • When a requirement changes, its links are flagged for review until someone confirms them.
  • An ECU supplier works in a child project and its test results count toward the vehicle-level requirement.

A first project

Start with one item definition: its hazards, the safety goals as top-level requirements, and one branch refined to a software requirement with a test case. Record a test run and read the coverage for the safety goal. If the chain reads correctly there, the rest of the item follows the same pattern.

What OpenV does not do

  • No certification, no tool qualification kit and no claim of compliance with any standard named on this page. OpenV holds the record; your process and your assessor decide whether it is enough.
  • No hazard analysis and risk assessment method built in: severity, exposure and controllability are fields you define, and OpenV does not derive an ASIL from them.
  • No check that an ASIL decomposition is valid.
  • No variant or product-line management beyond attributes and separate projects.
  • No electronic signatures, and no separate approver role: any project editor can approve, including their own change.
  • OpenV is in alpha: screens still change between releases, though data, exports and the API stay compatible across stable releases.

Read more