Reds Posted September 23, 2015 Report Share Posted September 23, 2015 I'm curious to hear what tools you guys are using to write and track software requirements/specifications. I'm especially curious to know if any of you have a workflow that can not only track requirements, but also document pass/fail test results for a given requirement in a given software release. For myself, I'm using Microsoft Word and FogBugz....i.e. I write the requirement in Word and then if it doesn't work, log it as a defect in FogBugz. However, there is a really naÃ¯ve underlying assumption to this workflow: namely, that I would never release software that doesn't meet a requirement or pass a test. That's obviously a bogus assumption. A defect logged in FogBugz also doesn't have any sort of link back to the original requirements document for future reference. Most importantly, this workflow doesn't allow me to run a report which says something like: "show me all unmet requirements in release 3.2" or "show me which requirements have never actually been tested in release 3.2". I think (know) that it's important to track which requirements are actually implemented and actually pass tests in a given software release. This type of tracking would require some sort of relational database, and my existing workflow just isn't up for it. So, how many of guys are more sophisticated than Microsoft Word? Quote Link to comment
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.