- Requirements Tree Diagram provides systematic approach in capturing requirements. Using Requirements Tree Diagram, one can drill down from top level requirement to more specific, detailed requirements. Moreover this diagram encourages capturing input, processing logic and expected output for each and every requirement leaving hardly any space either to miss out any requirement or for ambiguous requirement.
- Requirements Tree Diagram completely avoids bulky paragraphs that are used in traditional approach of gathering requirements. This drastically increases the clarity of requirements.
- Drilled down approach from top level requirement to more specific requirements provides the user a direction in which requirements can be gathered reducing the efforts involved in gathering requirements.
- Requirements Tree Diagram, due to its unique structure, provides inbuilt traceability matrix for requirements making the tracing of requirements a simple task.
- Due to tree structure, Requirements Tree Diagram reduces the chances of capturing one requirement at multiple places. This avoids inconsistency that may occur whenever there is a change in the requirement.
- Requirements Tree Diagram encourages reusability of requirements with the support of variety of relationships between requirements.
- With a variety of relationship between requirements, Requirements Tree Diagram helps in identifying the impact of changing one requirement onto other requirements and on entire system.
- Requirements Tree Diagram provides grouping facility for requirements using constructs like packages and system boundaries. This simplifies the task of visualizing and understanding the requirements.
- Requirements Tree Diagram provides a crystal clear picture of requirements. This diagram encourages capturing all the possible inputs, processing logic and desired outputs for all the requirements. With such a high visibility and clarity of requirements, this diagram drastically reduces number of change requests in requirements that are very common in traditional approach of gathering requirements.
- Due to very high clarity of requirements, efforts required for implementing the requirements can be accurately estimated.
No comments:
Post a Comment