|
|
|
|
|
|
Software Tools |
|
There are a number of tools that have been developed
to aid the requirements manager.
Index
Why use a Dedicated Tool?
Characteristics of Requirements Management Tools
How to choose a Requirements Management Tool
Why use a Dedicated Tool?
Due to the nature of requirements management, even relatively simple systems may be beyond the control and understanding of a single person.
Whilst the use and adaptation of standard software tools
to capture requirements information may be suitable for
small, short duration products, the use of a dedicated
tool should be considered early in a
project's life. The extra functionality of such a tool
can increase the consistency and quality of the requirements
management process, thereby increasing the likely success
of the project.
Characteristics of Requirements Management Tools
The majority of dedicated requirements management tools
available today focus primarily on the information management
aspect of requirements management. The strength of these
tools lies in the quality
and usability of their traceability, configuration, change
management functions and the
method by which they organise data.
Requirements Management tools often have additional characteristics and functionality available such as the following:
- Generation of customisable reports.
- Interfaces with other systems engineering and software engineering
tools.
- Graphical user interface.
- Scripting and automation tools.
- Multi-user working / shared documents.
- Distributed databases.
- Secure access / passwords, etc.
- Web Access.
- Export functions (e.g. to a document or spreadsheet).
How to choose a Requirements Management Tool
The choice of a dedicated tool is a subject that is open
to unlimited debate and will very much be a matter of
opinion. The tool should be applicable for its use and
the environment. The following are
some pointers that may help the decision making process
when comparing tools from the various
vendors:
- The tool should be aligned with, or tailorable to, the chosen Requirements
Management methodology or techniques to be followed.
The tool should aid, but not dictate the process or method.
- The tool should be effective for the necessary
phases of the project for which it will be used.
- The tool should incorporate the necessary functionality and characteristics.
- The tool should be as simple to use as possible.
Additionally, availability, support and price will need to
be considered. |
|
