Register  |  Login

Use the ReqDb as your authoritative list of all requirements that define your system.


Typically a requirement emerges in one or more descriptions. The existence of a requirement means that it must be built (coded) and tested. Thus the requirement is (should be) allocated in test scripts, component designs, code, i.e. across several artefacts.


To allocate, you could repeat the text of the requirement at all those locations or you can just refer to it by a unique number. The latter is of course much easier to maintain. For example, it is a common practice to add the requirements text at the end of the UseCase descriptions. However in many cases a particular requirement may emerge in two or more UseCases descriptions and perhaps in a design document as well. To have the requirements text in several places would create a maintenance nightmare. How would you keep a requirement definition text identical across different artefacts?


Clearly the easy way is to keep the requirements definition in one location, i.e. the ReqDb-list. Thus this list becomes the definitive source of all your requirements.


Wherever this requirement applies in a document, e.g. a UseCase or design, you can add the unique requirements identifier immediately following the text to which it applies {PR_16}. Like this. And, wherever you encounter an identifier, you can look up the exact meaning in the ReqDb list {SR_23}, as shown below:



Where PR is a process requirement and SR is a software requirement.


With ReqDb you no longer have to capture requirements statements in the text of UseCase descriptions etc. By having all requirements in one singular list, acceptance becomes crystal clear (does it meet the requirements or not) and scope and expectations can be managed by prioritising these requirements. And when things change, all you need to do is use Windows Explorer to find the relevant requirement reference identifiers.


Of course, there remains the issue of how to get the requirements right in the first place but that is a validation issue, and is addressed by a good software development process, like the SmartMethod.


Further information

       To download ReqDb’s latest version go to the Downloads>Freeware page.

       The ReqDb does not provide linking or traceability of requirements to specifications, tests and code, completeness checking, etc. If you need linking, sets, traceability, and more, please look at ScopeTracker.

       To learn more on how to write good requirements, please get the free Requirements standard and browse the Requirements management Tips & Traps pages.


 mail to colleague



Your Rating: 0.0   Average Rating: 0   Ratings: 0
Site Software v2.2.0, 26 Oct 2016