Requirements written in textual form found be to less understandable & create the chances of ambiguous requirements for stake holders, especially when the requirement is process related and have good amount of text involve, in that case Business Analyst must choose a requirement modeling technique that is best suited to model the specific requirement.
Some requirements can be model with Process Flow, some may require Use Case to become more understandable, and some may required ERD to understand the requirement.
All of them are requirement modeling techniques, and Business Analyst must choose the right modeling technique to make the requirement more understandable through diagrams.
For that purpose, I have found some useful diagram templates (Visio) & wanted to share the same with others, I'm sure those templates will give the head start to Business Analyst in creating requirement modeling diagram to make their requirement more understandable to stakeholders.
Other than that, there are many other requirements modeling technique available, please refer to IIBA Body of Knowledge Chapter "Requirements Analysis" for list of requirements modeling technique along with the usage instructions.
You can always ask me questions related to requirements modeling techniques. Other than that, I always welcome you to ask any queries related to business analysis, process improvement & re-engineering.
Download the requirements modeling diagrams template from the link below:
No comments:
Post a Comment