Lessons Learned: Traceability on the Run, the Plan First
Last month I had a not so pleasant experience regarding a (misdone) traceability, in the sense not done in time! I always preach that, when you are deriving requirements for whatever next level, the link to the higher level your requirement satisfies should be done right on the spot, immediately! That applies for requirements, standards, legislation, or whatever source a requirement might have. That way the effort for generating traceability becomes negligible. It’s not a separate dedicated activity anymore, a task that is excruciating, but an integrated activity of requirements development you barely notice. But we are just talking here about a certain approach to it that is best, in my opinion. So, that’s exactly what has not happened. We were reusing some old project requirements, on all levels. Time was short, higher level hasn’t started right away updating formalized requirements. But the SW developers need requirements to start implementation. So, I’ve written the requirements fo...