-
-
How do you resolve issues?
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 Munagantidody1108
- May 14th, 2010
As Business Analyst what we may face (or, what I have faced), issues could be different types e.g. Requirement/ technical issues Communications issues Difference of opinion amongst team membe...
rrouniyar
- Dec 20th, 2008
When ever we have issues First what is the cause fo the issuesSecond what is the soulations 3rd what is the best soulations
-
Non Functional Requirements
What are the Non Functional Requirements and what factors make them a good NFR?
-
What are skills required for business analyst?
Read Best Answer
Editorial / Best Answer
nehasahu- Member Since May-2007 | Jan 4th, 2009
Skills required for business analyst:
1)Analytical skills
2)Technical skills
3)Manegerial skills
4)Negotiation skills
5)excellent communication and writing skillsmanikandan
- Oct 17th, 2011
Why ? ITIL certification is required for BA
gabriel
- Oct 3rd, 2011
This is young business analyst your response toward this question has lead me to successful returns thanks! keep it up.
-
Explain how you organize or prioritize your workload.
How do you know when you are successful?
Aniruddha
- Jul 6th, 2017
For prioritization of the task there is an activity known as BA governance wherein we can select the task which needs to be done first based on the stake holders requirement, timeline given or is there any dependency in that particular task.
nissyec
- Mar 12th, 2016
Make a list. Work out what order to do things in by thinking about which tasks are urgent and how important each task is. If not sure whats urgent and what isnt, or how important different tasks...
-
What problems did you run into while gathering requirements?
Read Best Answer
Editorial / Best Answer
andar777- Member Since Aug-2007 | Aug 30th, 2007
Helping users to explain their requirements.
First and for most, you must understand that for the most part, users do not understand what is happening behind the forms they are inputting data into. A Business Analyst needs to be able to view the system through the eyes of a user and though the eyes of the developer. Then negotiate a compromise that will meet the user’s needs and also maintain system integrity.
You have to peel back the onion with the users by asking leading questions, such as, If you select this value from the list box, what would you like to see happen on the screen.
If you forget about the code and focus on the behavior of the form, you'll get a lot further with users. In addition, users tend to get there backs up when they are approached by someone from IT because they tend not to feel that the IT rep understands what they are saying and they get very frustrated. If they are frustrated, then gathering solid requirements goes out the door.
I was a user before I became a BA and I'm proud of it. :-)himansnu gaur
- Oct 11th, 2011
The major problem is faced when the user is not empowered enough to take decisions. In most of the case the business requirements are changed by the bosses of the business user. Such scenario are very...
dody1108
- May 14th, 2010
Difference of opinions between business usersFrequent changes in requirements, business rulesUndocumented business rulesManaging number of requirements within available time frame
-
-
-
What is the difference between BRD, SRS and Use Case documents?
patelmitesh07
- Sep 20th, 2014
Use case : A use case is a methodology used to identify, clarify, and organize system requirements. The use case is made up of a set of possible sequences of interactions between systems and users in ...
Moeen khan
- Jun 21st, 2014
BRD : It documents all the high level requirement , business users needs .i . e. , what all the application has to perform to satisfy user needs . SRS : It documents all the features of the system th...
-
How would you transform business requirements to functional requirements?
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...
-
-
BRD & FRD
what is the difference between business requirement document(BRD) and functional requirement document(FRD)?
Read Best Answer
Editorial / Best Answer
swapnil2882- Member Since Apr-2012 | Apr 18th, 2012
BRD: Business Requirement document states about the high level business requirement along with the business need and business problem FRD: Functional Requirement document states about the functionality required in the application designed for the business problem and need mentioned in the Business requirement document. It mentions the Functional as well as Non functional requirements. Functional requirement are described with the help of Use case description and Use case diagram where as Non functional requirements like capacity, performance etc. are also mentioned. Hope this will help you.
faraz
- Apr 12th, 2017
BRD : Its simple means What exactly customer wants this high level requirement maintain in docs called BRD.
FRD: How this high level requirements as BA we are going to achieve with functional and non-functional requirements maintain in docs is called FRD.Srikumar Menon
- Mar 31st, 2017
BRD: The key or the moto of a project
FRD: How the key or moto can be achieved -
How would you handle a scenario when requirements change midway in the project?
kavisekhar
- Sep 16th, 2010
The RCA need to be known.The extent of deviation need to be analysed.Accordingly the technical requirements need to be reviwed.
snehasudhir
- Sep 1st, 2009
Yes there are all possibilities that requirements can change midway and of course we need to remember that we are always trying to customize a product to our client so this is very possible to occ...
-
-
Hello,I would like to know about where to start get familiar with this field as i would like to start my career as Business Analyst and i hold M.B.A in information Technology but still some new concepts are there i am absolutely not familiar with.Can some suggest me any case study or project i should start from and get familiar with each and every steps involved in this with the help of developing that project/case study by myself. One more thing i would like to know that all the use cases/activity diagram/requirement document gathering are done in MS office package.Please suggest me any project name/case study with a little synopsis which i can develop by myself and can link all required phases involved in SDLC steps by steps and what about those phases where testing is involved as i do not have any testing software installed in my PC.Please help me.Thanks
Read Best Answer
Editorial / Best Answer
jaysan- Member Since Sep-2006 | Mar 18th, 2007
Hi,
After reading your mail I could guess that you are completly new in this field. I could advice some tips to you to get into BA Role.
i) Equipped yourself with some business domain like banking,insurance etc.
ii) Learn any technolgoy which we use to prepare case studies like Rational suit etc. it's not mandatory but it will help you in launching yourself.
iii) Expertise yourself in Word,Excel,Power point, Visio, MS-Project as these are the tools used in day to day activities.
iv) Find any case study on internet and go through some Business Requirement documents(BRD) as you need to prepare the same.
v) Equipped yourself with some technologies falvour as well it will help you in coordinating with development teams and conveying your requirements clearly and understanding their difficulties as well.
vi) Study some effort estimation techniques like FPA etc. as you need to know to prepare effort estimation as part of your job.
Last but not the least also go through testing terminologies as you need to do testing yourself and involed with users, also communication is Big factor as you will be communicated with Business users and markets and senior management.
I hope this will help you and you can get case studies on internet.
regards,
SanjaySANJAY AHUJA
- Jun 12th, 2013
Hi Sanjay
Please advice me how i can find project stories for an upcoming interview in the Pharma field.They need somebody with Blueprint Requirement center exp and working with GxP implementationLuan Nguyen
- Mar 10th, 2011
If you are new to SDLC in general I strongly recommend Software Engineering a Practical Approach by Pressman. It has 2-3 chapters on reuirements and covers all the bases for a BA. It has good contents...
-
Business Analyst
What are the tools used by Business Analyst to gather requirements. Do they do it using, MS Word, Visio, MS Project or are there any specific tools?
fattyreflyer
- Sep 8th, 2009
Another good tool that is not tied to any particular (read: proprietary) process or method is Enterprise Architect.
feverx4u
- Feb 1st, 2009
Few more 1 Test Director: Requirements traceability tool. 2 IRise Manager (This is an excellent requirement Gathering tool, go to irise.com to get more info about this) 3 Rational Suite (used to...
-
Difference between PM and BA
What is the difference between a project manager and a Business analyst ?
IT_Engineer
- Feb 23rd, 2013
When the project originates within the business unit, the Business Analyst writes the Business Case which funds the project. The Project Manager is brought in later to lead the implementation of the ...
Deepthi
- Sep 18th, 2012
Project Manager: The PMO (The Project Management) office assigns the Project Manager in the initial phase of the product development. The PM does all the Enterprise analysis which include the Feasibil...
-
High Level Use Case?
What is high level use case? What are the list of documents a business analyst should maintain?
Vishal Dholariya
- Jun 20th, 2011
I would consider high level use case as a detailed use cases.It contains, Name of use case Unique ID &nbs...
rachel123
- Jun 18th, 2008
A high level use case tends to be more narrative.It would be description in a paragraph or two depicting the high level requirements relative to the application
-
How do you come up with non-functional requirement?
Read Best Answer
Editorial / Best Answer
amarchis- Member Since Jun-2007 | Jun 9th, 2007
There are a variety of methods to elicit non-functional requirements. One method that I use is to identify upfront (before the project even starts) the main categories of non-functional requirements as well as a standard set of questions to ask for each type of non-functional requirements.
Here are some key categories of non-functional requirements:
1. GUI look and feel requirements
2. Performance requirements
3. Availability requirements
4. Security requirements
5. Capacity requirements
6. Exception Handling requirements
7. Logging requirements
8. Extensibility requirements
9. Data Retention requirements
etc.
Then for each type of non-functional requirement you could develop standard questions or just as more general questions such as: "Data Retention: do you have any requirements related to how long data (or certain types of data) should be retained by the system?"
Hope this helps!
- Adriansandhya001
- Sep 3rd, 2007
Functional Requirements are MUST-TO-HAVE (without these requirement the system or part of the system will not function)Non-Functional Requirement are NICE-TO-HAVE (without these requirement the system...
sandhya001
- Sep 3rd, 2007
The simple method is:Functional Requirements are MUST TO HAVE (The system will not function without these requirements)Non-Functional Requirements are NICE TO HAVE (The system will work however, NFR will increase the usability or performance related issues.)
-
What analysis and modeling techniques do you use to translate business objectives into system requirements?
Read Best Answer
Editorial / Best Answer
srikanthpullikanti- Member Since May-2008 | May 16th, 2008
When the Business Obectives are set then BA makes a Requirements documentation in which the analysis is done by various techniques like
Stakeholder interview,Goals,JRD sessions ,prototypes,usecases,SRS,Stake holders intrest and issues and Attempted soltions.
MOdelling techniques is the next step after the requirements is done by UML used for functional or logical view, code view,or development or structural view.dody1108
- May 14th, 2010
The analysis techniques that I have used:Lay out business problemsDepicting business problems by grapical structures using MS visio, rational s/w tool, simple flowchartsWell organized JAR sessions wit...
srikanthpullikanti
- May 16th, 2008
When the Business Obectives are set then BA makes a Requirements documentation in which the analysis is done by various techniques like Stakeholder interview,Goals,JRD sessions ,prototypes,usecas...
Business Analyst Interview Questions
Read Best Answer
Ans