Dalus + MATLAB/Simulink
Simulink holds the behaviour and MATLAB holds the analysis, while the architecture, the interfaces and the requirements live in the system model. Run the tests you already have and tie the results to requirements, compare the block diagram's interfaces against the architecture, or measure a requirement by simulation. Your scripts are never rewritten and neither model is ever modified.
3 workflows
Run your MATLAB tests against the requirements
Your own tests, run unmodified, with every result tied to the requirement it verifies.
Simulink interfaces against the architecture
Where the block diagram and the architecture disagree about a signal, before integration finds it.
Verify a requirement by simulation
A measured value against the limit, with every assumption in one place and proxies named.
