Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Requirements  Who is responsible to map the requirements to the solution?
Previous Previous
 
Next Next
New Post 6/29/2012 9:49 AM
Resolved
User is offline siebel_ba06
3 posts
No Ranking


Who is responsible to map the requirements to the solution?  

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?

 
New Post 6/29/2012 10:16 AM
Accepted Answer 
User is offline Anthony Chen
63 posts
8th Level Poster


Re: Who is responsible to map the requirements to the solution?  
Modified By Anthony Chen  on 6/29/2012 12:18:16 PM)

 It sounds like they were looking more for a configuration engineer. Someone who knows how to configure siebel. In that case either you know siebel or you dont. 

There are many types of projects such as greenfield, enhancements  and commercial off the shelf implementation. In a COTS implementation (like siebel) there is a blurry line between the people that configure siebel and the people that collect the requirements. 

 

Personally I would side with you on this, but I  recognize in many organizations the people who gather the requirements are also the people who configure the system.

 

Let me add that for a system like siebel, one of the easiest ways to make a link from requirements to a COTS system is to map screen shots directly to the requirements. Get the developers to make screen captures and then show which fields on the screen map or are influenced by the requirements.

 
New Post 6/30/2012 3:08 AM
User is offline siebel_ba06
3 posts
No Ranking


Re: Who is responsible to map the requirements to the solution?  

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

 
New Post 7/2/2012 1:48 AM
User is offline Kimbo
442 posts
5th Level Poster


Re: Who is responsible to map the requirements to the solution?  

They were probably looking for you to talk about requirements traceability matrices, etc. You said you developed use cases. Simplest thing to do is to map your requirements to the use case to which it applies.

Kimbo

 
New Post 7/2/2012 9:13 AM
User is offline Tony Markos
493 posts
5th Level Poster


Re: Who is responsible to map the requirements to the solution?  

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

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Requirements  Who is responsible to map the requirements to the solution?

Community Blog - Latest Posts

Nick Stowers
Nick Stowers
Introduction   When I was introduced to scrum, the burndown chart was a tool that was highly emphasised however I feel the purpose has changed from it being a tool to predict (to a certain level) timescales for delivery to a tool that measures a team’s productivity…..in other words, the focus is on the number of points cleared w...
0 Responses
Jason White
Jason White
New technology is in trend every day and striving to make its mark to be the best. It is not optional to stay exceptional, technology has made lives easy and uncluttered in so many ways that cannot be comprehended. With the latest technologies in the headlines every day, it is Artificial intelligence that is leading the race and being incorporated ...
0 Responses
Digvijaybook
Digvijaybook
The role of a business analyst is to manufacture a piece of art; the piece of art varies depending upon the methodology and techniques being used. Business analyst serves the project all through the beginning until the end and comes up with different pieces of art. It all depends on the case, the business analyst gets involved from the beginning of...
0 Responses






Latest Articles

A Practical Guide to Transition from Waterfall to Agile
May 25, 2020
0 Comments
The transition from Waterfall to Agile is never easy – especially for a business analyst who must go through this journey. This document has com...
Copyright 2006-2020 by Modern Analyst Media LLC