I have about 4 years of experience in siebel as a developer and slowly from last 6 months started taking up business analyst tasks. Usually when we get a requirement, i talk to my client do the requirement gathering and list out all the requirements and prepare Use case diagrams and activity diagrams and give KT to the developer. the developer would prepare the detailed design document/technical design. I never felt any difficulty in analysing the requirements and getting to know where it has to be implemented because i was in the same project and have been a developerand know most of the functionality.

I had an interview yesterday and they asked me how do you map the requirement to the siebel solution. For example you have a requirement which says "Implement the mobile number portability" How would you map that particular requirement to the siebel solution?

I was not able to effectively answer this question. I told her about the requirements gathering, conducting discussions with the client, and getting the final list of requirements etc.. But she was more specific and asked me How would you map that particular requirement to the siebel solution?

Now my questions are:

Who is responsible to map the requirements to the solution?

How would you map that particular requirement to the siebel solution?

Thanks for your reply Anthony.  May be they were looking for an architect+Analyst.

Hi Kimbo:

I agree with you in that the issue hear is tracability:  The ability to trace from higher-level, often very abstract, business requirements, down to specific detailed requirements - mapping at this level directly to solution components.

The real work here is effective decomposition, especially as business systems tend to be complex.    Problem:  Use Cases offer no guidance on how to proceed in decomposition.

Tony