M
My client maintains a SW application which can be described by approx 100 high-level requirements (market requirements specification). At the next level of detail there may be about 500-1000 software requirements.
The existing specification is out of date and needs to be re-written.
There will also be traceability to test cases needed.
Once the specifications are written, they do not anticipate too much change over the years, only minor additions.
What is your recommendation for managing this amount of requirements?
- Word: Looks nice, easy to add descriptive text. A pain to maintain?
- Excel: Easy to get started with. Easy to expand with new coumns if new attributes are invented. Can easily be turned into a poor man's database. Lacks backup and history features. Easy the corrupt information by mistake.
- One of the commercial entry level requirements management systems out there. They always lack some features...
- Going with a mid-range system. For installation and maintenance see below, and license fee's may be in the k$ per seat per year.
- Going all the way to a full-blown system. My client has a license for Microsoft Team Foundation Server, but the installation and maintenance efforts are not trivial.
They definitely do not have the manpower to spend on server maintenance for the higher range systems.
Why can't I find the holy grail of requirements management systems???
The existing specification is out of date and needs to be re-written.
There will also be traceability to test cases needed.
Once the specifications are written, they do not anticipate too much change over the years, only minor additions.
What is your recommendation for managing this amount of requirements?
- Word: Looks nice, easy to add descriptive text. A pain to maintain?
- Excel: Easy to get started with. Easy to expand with new coumns if new attributes are invented. Can easily be turned into a poor man's database. Lacks backup and history features. Easy the corrupt information by mistake.
- One of the commercial entry level requirements management systems out there. They always lack some features...
- Going with a mid-range system. For installation and maintenance see below, and license fee's may be in the k$ per seat per year.
- Going all the way to a full-blown system. My client has a license for Microsoft Team Foundation Server, but the installation and maintenance efforts are not trivial.
They definitely do not have the manpower to spend on server maintenance for the higher range systems.
Why can't I find the holy grail of requirements management systems???