Requirement Management Tools
Autor: Jibin John Jackson • July 19, 2016 • Exam • 673 Words (3 Pages) • 722 Views
INFO6215 51849 Business Analysis & Info Eng.- Summer Full 2016
Assignment 9
-Jibin Jackson John
What are the main principles to selection criteria development described in the whitepaper?
The One size fits all approach does not work in case of requirements management tool and the principles needs to be modified according to the organizations needs.
The main principles to develop tool selection criteria include:
• Support for storing specified requirements and their related artifacts, such as models
• They should allow links between requirements objects in the tool
• It should support reviewing and tracking changes to requirements
• It should also back the importing and exporting of requirements
There is one consistent party performing the evaluations across all tools to ensure standardization of the selection criteria. Also multiple people in an organization need to evaluate the same set of criteria across the various tools reducing the risk of interpreting the criteria differently.
The evaluation is followed by informally looking at demos of approximately ten tools, and then narrowing down to three tools selected for further analysis.
What was the process and approach for evaluating requirement management tools?
Process and approach to evaluate requirement management tools:
- Creating a complete list of possible requirements tools for evaluation followed by a prioritized list of criteria for the tools.
- The follows selecting a shorter list of first pass criteria from the full set of the listed criteria.
- Then filter the list developed for strict requirements management tools, excluding those for requirements definition, prototyping, and agile-specific projects.
- Publish the tools criteria and tool list for industry review and evaluate the full list against the first pass criteria.
- Then evaluate top 15 tools from first pass evaluation against full criteria list and have the top 15 tool vendors evaluate their tools against the same criteria, looking for discrepancies.
- Implement and evaluate top three tools from the full evaluation on actual projects
- Finally publish results for industry review then implement and evaluate top three tools from the full evaluation on actual projects.
- Once a full set of criteria is established, the use cases and criteria can be prioritized using this scale: High, Medium and Low priority
Write a concise report to describe the 5 tips on requirements traceability.
If managed poorly, change will wreak havoc on even the most talented and experienced development teams. If managed skillfully using tools like traceability, teams are better equipped to assess the impact of changes, track the full history, keep everyone in sync and (deep breath) consistently improve the quality of the products being built – every project, every release.
...