I have an upcoming interview with IBM end of the August, 2010. where a group case study would be thrown at me so that I can procure the requirements based on that example? Can any of you help me out how a BA or is supposed to go about asking questions digging for information from the client?This, 'course involves two scenarios where the BA has either domain knowledge(or product knowledge based on experience) or not.Let's just go with NOT.
I am confused about the approach method to any case study, let's say a loan management sstem, or a traffic management applciation, or an online shopping portal.On the top of my head, I would start with questions related to the users/stakeholders involved etc?But I reach a mental block beyond the obvious questions.Is there a more sustainable approach like a tree structure or something?
The question is pretty high level, i guess a lot will depend on what is in the case study as that itself will give you an idea on what really needs to be asked. I am thinking out loud here but obvious thing will be
Scope - what is the high level requirement
Stakeholders - who is going to use it and does their behavior defer based on their needs
High level tangible pieces of requirements - i like to call them components that make the application/system and then you have to drill inside each of them
Example: Scope - build a Patient Information System that can help a hospital manage patient records/appointments etc. Stakeholders - Doctors/Nurse/Hospital Admin (finance & services etc.). Components: Patient Data/Doctor Data/Room Data etc etc. One approach could be to ask what is the current process and then identify needs that require further analysis to gather discrete requirements. Identify gaps that can be addressed by automation, i.e. system.
The above is just a stab, basically u start at a higher level and dig deep.
good luck.
thanks
brought to you by enabling practitioners & organizations to achieve their goals using: