Requirements Under Control: How Traceability Helps Avoid Confusion

In software development projects, requirements last a long time and change frequently. Businesses shift their priorities, regulators impose new constraints, teams refine functionality, and at some point, it becomes unclear what affects what. 

In my talk, I will discuss requirements traceability as a practical tool for change management. I will illustrate the real problems it addresses, the types of traceability that exist, where it is justified, and where it may be excessive. I will use a requirements model as an example to explore the various connections between artefacts and some common pitfalls in implementing traceability in projects of varying maturity. 

I will also demonstrate how AI helps identify missed connections between artefacts, while CI/CD enables automatic verification of compliance with traceability rules when requirements change.