Submitted Questions

  • How do you resolve issues?

    Star Read Best Answer

    Editorial / Best Answer

    Ravindra_munaganti  

    • Member Since May-2008 | May 31st, 2008


    Dear Friends
    I have read most of the answers and I am impressed the way people resolve the Issues...But I am sorry to say most of the people forgot that they are attending this question in a Business Analyst interview.

    The meaning for this question is as a business analyst how do you resolve issues?
    not only in your team but the problems faced while you were at clients place( while gathering requirements)

    Lets take an example of improper requirements: If two department people are giving the requirements and if they have some common resources to use...so one department people wants the application in some way and the other department wants in otherway...If they are adament on their statements and wants the application to be developed in their way....which is not feasible ...then we have to follow these steps
    1. Explain them clearly what we can not build an application until and unless they agree and stick to single opinion.

    2. If they still do not understand tell them about the time constraint. man hours wastage and money loss for their own company if they try to prolong the issue.

    3. Even if they donot agree then report this issue to the your higher authority which is project manager or Principle BA to look in to this matter which he inturn speaks to the client regarding this issue.

    similarly if you have any issues regarding communication and it is better you convince your client if you can use any recorder to record the requirements which you can later analyse or ask for the help of interpreter.
     

    so these are all the steps usually a BA should follow to resolve any issue.

    please do correct me if anybody disputes with my opinion.

    Best Regards

    Ravindra Munaganti

  • How would you transform business requirements to functional requirements?

    Star Read Best Answer

    Editorial / Best Answer

    prsh_patel  

    • Member Since Mar-2007 | Mar 27th, 2007


    while preparing Business requirements documents you mention why you need to bulit a system, i.e. problem statement. What you need to do while creating functional requirements is you have to specify is, solution of the problem. Specify thorugly business problem and explain solution for the same.

    Business requirement documents does not necessarrily contains solution part, functional requirement may contain it how end user wants the system to perform. Dont forget to add non-functional requirements same doc.

    Following is the instance of Business Requirement, Functional Requirement and Non-Functional Requirement.

    Business Requirements :- sales order is made against customers purchase order. Sales order is given for approval to upper authority

    Functional requirement:- Sales order shall be made with reference from Purchase order and it should be approved from upper authority.

    Non-Functional Requirement:- Sales order should be in proper format (Specify format) and six copy of sales order should be printed from printer in 1 minute.

    Nasir

    • Oct 28th, 2015

    BRD depicts the business challenges and problem statements. where as FRD depicts how the solution has been defined for the problem statement. As we all know BRD is source for FRD we can elaborate and detail the requirements textually, flow diagrams, and use case models.

    Abdul Salam

    • Jun 24th, 2015

    Business Requirement: In short word its an event the end user do on daily basis such as adding money on account by bank tellers or adding your name in waiting list while placing a call to customer c...