|Re: Why is Formal Requirements Tool is Needed? [message #901694 is a reply to message #900990]
||Tue, 14 August 2012 07:56
|| Michael Jastram
Registered: April 2010
Location: Düsseldorf, Germany
The short answer is, that professional RE tools can give you features that are mandatory to support your processes, but that do not exist in the tools you mention. Such features include:
* Linking: Creating traces between requirements and other artifacts
* Versioning / Baselining: Tracking the history of individual requirements and creating a baseline that groups a set of requirements together
* Collaboration: Teams working on the same requirements model at the same time
* Setup of a data model: Providing the typed attributes (description status field, severity, importance, etc.) that allows the classification of requirements
* Analysis: Specific tools for analysing the requirements (i.e. identifying unrealized or untested requirements, performing impact analysis, etc.).
These are just a few, and which ones you really need, depends on your process.
Feel free to post follow-up questions, but please be aware that this forum is not quite the place to get answers, as it is specific to the Eclipse Requirements Modeling Framework. A good place to look for experts on this topic is, for example, the following LinkedIn Forum:
Powered by FUDForum
. Page generated in 0.02278 seconds