Which annoying requirements / V&V task would you automate first?
I've been working with requirements and V&V workflows, and there are a few repetitive tasks I keep finding frustrating:
- figuring out what requirements/tests are impacted after a change
- reviewing whether requirements are actually well written and testable
- checking whether requirements are properly covered by test cases
- finding gaps or inconsistencies in requirement → test traceability
I'm thinking about building a small open-source plugin around one of these problems, mostly as a side project and to contribute something useful to the community.
For those working with DOORS, Polarion, Codebeamer, Jama, etc.: which of these is the most painful in practice?
Or is there another boring/manual task in your day-to-day workflow that you'd automate before any of these?
I'm especially curious about the things you currently solve with Excel, scripts, manual reviews, or just lots of clicking.