| chetan_s2 wrote
Hi all,
Can any body please elaborate the BA workflow. For example 1st step is requiremnt gathering....then what??? when are the use cases, activity diagrams, sequence diagrams.. prepared etc.... i want the specifc flow.
|
The answer is more involved than what I can communicate here. But here are a couple of links and a brief attempt.
Here is a blog post that I think addresses where to start with modeling
http://requirements.seilevel.com/blog/2006/03/people-systems-and-data-analysis.html
This has some whitepapers with processes, they are a bit high level.
http://www.seilevel.com/resources/whitepapers.php
When we start on a project, the first thing we try to understand what are the measurable business objectives. In concrete terms how will the project help to drive revenue or reduce costs. What are the high level features that the executives have conceptualized that feed into those. So I would say first is
1) Identify single business owner - who is the one person with the vision and the budget who can break all ties
2) Identify business case - at the level of 10-20 features identify how the business will save or make more money.
3) Identify the users and create an org chart to make sure you dont miss any
4) Identify the systems in the eco system - system context diagram
5) Identify the business data and diagram the relationships between the data (business data diagram - looks like an entity relationship diagram but is for the business)
6) start creating process flows, create L1 and L2 process flows by talking to users
7) begin generating requirements based on the functions and business rules and organize those requirements according to the steps in your process flow
8) create data flow diagrams based on information flowing through the system
9) create data dictionaries which identify all the data
10) etc etc
There is a lot more, but these are the basics to get you started