Hey

I am looking forward to carry out my B.A learning from an MBA background, so I am in the new team as well. learning this  could help me get detailed information for my BA preps

For those interested in taking this example a bit further, I've created a new thread:

Use Case Model: Bank ATM Example

- Adrian

Ashwin_Mohan wrote   I feel from the start an important phase was missed(which will help in grouping functionalities). There was no discussion as to create an AS and TO process models. This would then in turn result in multiple use cases for each of the process. Just my cents worth.

Dear Ashwin,

You're correct: we did not do an AS-IS vs. TO-BE analysis.  We wanted to keep the role play simple.  Also, in real life, we don't always get the luxury of time to be able to create every single type of artifact and model which we might want.

Part of the value that a senior business analyst brings to the table is the ability to decide when an artifact is needed and when it's not.  While our job is to analyze, to much analysis is not good either.  There are many business analysts who, if allowed to, would never complete the task at hand but instead continue to create models after models and documentation after documentation.

We work for real companies and on projects with real budgets so we need to always think about doing "just enough" (no more, no less) in order to achieve the goals of a given project.

Hope this helps!

- Adrian