Application requirement or project requirement?
Our company is using Test Director since 1999, but we don't use the requirements feature that has been recently added to the product (we now have TD 7.5). Recently our ISO-9000 Quality team has prescribed a rule that imposes to all projects to record requirements in TD and link them to the tests in order to have a criterion to verify the completeness of the tests planned.
I think that this is a very good decision, but now a methodological problem faces us. Let's suppose the following scenario.
We have completed the development of a large application. We have a set of requirements that are now "incorporated" into the application. Every requirement is linked to the tests that verify that the application satisfies it. The requirements may have been updated during the development process, but this is not relevant now.
Now we start the maintenance of the application. Maintenance activities - except the ones aimed at fix bugs - are composed of a set of projects. Many of them are very small (less than 20 gg/u, but we still call them projects), but there may be maintenance projects up to 100-200 day/person (and even more).
The question is:
"Should we record in TD the application requirements or the (maintenance) projects requirements?"
In other words, as we start a maintenance project should we create a new set of indipendent requirements (using a separate folder) or update the original ones.
I prefer the first way (application requirements), but I have some doubts, so I would like to understand what others are doing. All material I could find on requirements seems to be talking about the development of new applications.
I think that both options have some advantages (but also some disandvantages). To semplify we can consider only the advantages:
- Requirements perfectly states what the application (should) do
- What we record in TD is exactly what is written in the project document we agreed with the users
- Link these requirements to the tests is (maybe) easier.
I would greatly appreciate if someone of the members of this forum could help me with reference to resources (books, internet resources, etc.) or even with their own experiences and ideas.
Thank you in advance,
Re: Application requirement or project requirement?
I was involved in something similar, but using Rational tools, ReqPro for requirements.
One option would be to build another set of requirements, with links to addressed req. from the application, bug reports,..., to which you can add the changes, comments,... Of course you also could take the corespondent test cases, which will be adapted to fit your new changes, and add some new ones if required. (what we have done)
Or you can replicate the needed req. from the application, with test cases into anather database, where you will do all the neccessary changes.
Or you can see the small projects as next version of application, and you'll add new requirements to the existing one: what you have extracted from bug reports, customer change requests,...
If you need a reason to be happy - FIND IT, don't wait it !