How often do we hear “Create a data model? That’s not BA work,” or “Prototyping? Our developers do that.” Or “Use cases? Why won’t they just go away?!” Many organizations think that business analysis is all about asking questions and documenting the requirements. Although important, those skills are not enough. If we want a complete set of requirements, we need to model them. This presentation provides the key modeling techniques and tips for using them for project success.
During this presentation we cover the top models business analysis practitioners can use in their “toolkit” for complete requirements analysis. We will review each of the models by category and discuss the importance of modeling to getting the requirements right, emphasizing the relationship between elicitation and modeling.
This presentation focuses on:
The importance of modeling in getting requirements right
How models work together to reduce analysis time and provide complete requirements
When to use data, process, use case and prototypes models
Which models to use during major stages of the project lifecycle
The iterative nature of requirements elicitation and modeling
5 Ways to Increase Production in Your Business
API quota exceeded. You can make 500 requests per day.Is Your Company Throwing Away Millions Each Year?
Lesson Plans On Organizational Skills – Key To Success
A Complete Inventory Management System Built With Excel
Top 7 Reasons for Giving Employee Awards