Achieving compliance with low-fidelity migrations
One concern that many customers have is end-to-end traceability for compliance reasons. In many highly-regulated industries, you have to provide end-to-end traceability for all requirements and final functional tests. The problem with low-fidelity migration is that you will get a cut in that traceability chain.
But that does not mean that the only solution is high-fidelity migration. You can still do a clean cut-over and keep the old systems in read-only mode running for as long as necessary. In the new system, you must achieve end-to-end traceability anyway. To stay compliant, you need a mapping of the old system identifiers to the new system for the requirements that span both systems.
In the case of an audit, you can provide reports from both systems – both the old and the new. For some requirements, you might have to look at both reports, but that will still provide valid traceability if you have identifiers that allow...
