| || |
Tools to manage the development process
something I've been thinking about for a while, and would like to know what people think and what experience they've had where they work.
I believe there are probably a number of tools around that attempt to provide the following:
- an area to document requirements
- an area to document test cases/scenarios and link them to the requirements
- an area to document test results and defects, that link back to test cases, which in turn link back to requirements
If such a tool is designed properly, it should enable you to produced reports that tell you such things as:
1. how many test cases you have for particular requirements
2. how many defects have been logged in relation to particular requirements
In addition to the above I think such a tool should:
1. Enable you to flag a particular requirement or group of requirements as being the responsibility of a particular person. (It should be easy for someone to quickly mark a group of requirements as being the responsibility of a particular person, rather than mark each individual requirement. Eg, you're building an application that has an 'administration' area which has, say, 30 requirements within it that one developer (named Fred) is responsible for building. It should be easy to mark all requirements in that category as being the responsibity of Fred.)
2. it should be easy to mark a particular requirement or group of requirements as completed (if all requirements are flagged in the system down to a detailed level, and are marked as either 'incomplete' (the default) or 'completed', this should enable you to easily produce reports on the percentage of requirements complete/incomplete. It also should prevent the situation of requirements simply being missed altogether, and only being found (hopefully) in testing. I've found that when extremely detailed requirements are simply contained within huge blocks of text, they can easily be missed. If all requirements are pulled out and flagged in a system such as this, the problem shouldn't occur (or at least it should be greatly reduced).
3. Similarly, there should be the ability to mark particular test cases as being the responsibility of particular people to execute.
We use Test Director, but whilst it should be able to do the above, I believe it doesn't do it, or at least doesn't do it effectively.
What do people think? Is anyone using a system that provides the above functionality? Or something similar?
Re: Tools to manage the development process
e-Manager Enterprise from Empirix is designed to do what you have described.
I have used it in the past, pretty much as you have indicated.