DVAR ReflexLoop · In development
Requirements, generated code, physical testing and traceable evidence. Connected in one intelligent engineering workflow.
DVAR is building ReflexLoop to connect the work that usually sits in separate tools and test benches. The ambition is shorter feedback cycles, less repetitive engineering and a clearer path from a requirement to the evidence behind it.
Follow the intended workflow from the first requirement to a reviewed engineering handover.
Load the product requirements, interfaces and applicable assurance objectives. Establish a versioned baseline and the acceptance criteria that the work must meet.
Evidence carried forwardRequirements baseline + review decisions
Generate proposed firmware, application code and test specifications around that baseline. Connect each change to the requirement it is meant to satisfy.
Evidence carried forwardCandidate revision + requirement links
Run unit tests, static checks and model-in-the-loop simulation where applicable. Keep engineer-reviewed test expectations and independent checks alongside generated tests.
Evidence carried forwardSoftware checks + simulation evidence
Compile an approved candidate and flash the device under test. Connect the build identity to its DUT, fixture map and controlled operating limits.
Evidence carried forwardBuild identity + DUT configuration
The PinMatrix rig applies a configured test programme: normal behaviour, boundaries, selected fault conditions and regression checks. Capture measurements against expected outcomes.
Evidence carried forwardTest cases + physical measurements
Failures inform proposed corrections. Repeat the relevant software, simulation and hardware checks, while linking revisions, results and unresolved issues for engineer review.
Evidence carried forwardTraceable revisions + release evidence
Acceptance criteria, safe test limits and release authority remain explicit. Requirement changes are versioned and approved, not silently rewritten to make a failing test pass.
The physical side of intelligence
A configurable test-rig architecture connecting the software loop to real electrical behaviour.
1,000+
analogue inputs and outputs
in DVAR's test-rig architecture
Map selected microcontroller, ASIC and connector interfaces through a configured probe fixture. Link stimulus, measurements and expected outcomes to the same requirements baseline.
Channel configuration, probing access, signal loading and electrical limits are defined for each device under test. Detailed rig specifications are available through a technical discussion.
Discuss your DUTStandards-aware planning, traceability and documentation. The applicable requirements depend on the product, its risks and its intended market.
Scope functional-safety evidence against applicable ISO 26262 objectives and automotive cybersecurity work against ISO/SAE 21434. Tool confidence and assurance remain project-specific.
ISO 26262 supporting processes ↗Connect software lifecycle work with applicable IEC 62304 processes and ISO 14971 risk management. Final device validation and market-specific regulatory obligations remain separate responsibilities.
IEC 62304 scope ↗Support secure-development evidence, including applicable IEC 62443 objectives for industrial automation and control products. Define the threat model and assurance scope for the actual system.
IEC 62443-4-1 scope ↗Plan around programme-specific assurance, contractual requirements and information-handling rules. Human oversight, quality, safety and security stay part of the engineering process.
MOD AI assurance guidance ↗Generated tests and documents support an assurance process; they do not, by themselves, establish certification or regulatory approval.
Deployment choice is part of the product architecture, not an afterthought.
The platform is being designed around controlled model execution, rather than copying project material into public chat tools. Hosting location, tenant isolation, training permissions and retention are separate choices to agree for each deployment.
Model specialisation and fine-tuning are part of the development programme, with task-specific evaluation before use.
Carry requirement relationships through code revisions, builds, test cases, results, exceptions and review decisions. Keep the reason for a change beside the evidence for it.
Polarion and SpiraTest are integration targets. Artifact mapping, permissions and synchronisation are scoped to the tools and versions your team uses.
Integration roadmap, not a claim of certified or already validated vendor connectors.
DVAR Intelligent System
The DVAR Intelligent System answers questions about the workflow, test rig, traceability and deployment options. For project-specific engineering, contact the DVAR team.
Reading your question against the ReflexLoop product brief.
This automated DVAR Intelligent System guidance is not a test result, engineering approval or a live connection to a DUT.
Discuss this with DVARReflexLoop is in development. Talk to us about the platform, your test requirements and potential pilot opportunities.
info@dvar.co.uk