-
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
-
How do you manage risk for a project?
skba07
- Sep 9th, 2011
We can prepare risk register (through extensive brainstorming) to manage risks. This will contain - Risk (uncertainties) and its reasons Its impact (Low, Moderate, High) Probability (High, Medium ...
nehasahu
- Jan 5th, 2009
We can manage Risk by analysing the requirements and system. Compatibility of requirements with system(i.e databases, procedures, workflows)
-
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
-
Requirement Capturing
What is your experience with writing Use Cases? What methods you have used for capturing requirements?
Sowmya Vasisht
- Mar 11th, 2011
The different methods of requirement gathering depends on the client location.Via Conf calls, emails, Prototypes or onsite one-on-one communication with client.Also there are different methodologies used according to the project and client requirement1. Waterfall2. Agile3. Iterative and incremental.
veronica1988
- Sep 14th, 2010
Used case diagrams can be created using tools such as MS Visio and Rational Rose. Also writing use case specifications is an essential part as they can be later used for preparing test cases during th...
-
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...
-
What is the carreer path for a Business Analyst?
Read Best Answer
Editorial / Best Answer
Answered by: Lon Harvey
- Jan 25th, 2007
A Business Analyst in the IT field has many varied directions among which to choose a career path. The most direct would lead to a Lead Business Analyst position and then Project Manager whereby the incumbent manages projects through the entire lifecycle from inception to post-implementation including the management of business analysts, system analysts, quality assurance analysts and most likely development project managers or team leads. That path would then lead to Program Management, perhaps PMO management or Product Manager and on to Directorship.In addition, a good Business Analyst may find they are heading toward a Customer Relationship Manager position whereby they become the primary IT interface to a given Business Unit (BU). This role most often leads to a position within the BU as a Manager of Applications or a Process Management role. Process Management opens many jobs including process re-engineering, quality program development, and large scale or enterprise process management programs such as ITIL or Six Sigma initiatives. These roles will continue to proliferate as companies realize the benefits of having a SME in process and quality.And still many Business Analysts find their understanding of business process entirely portable into purely system related positions in the business side that are only peripherally related to IT. These of course may lead to quantitative roles, manager roles or operational roles such as supply chain, logistics et cetera.Of central importance to a successful Business Analyst is the interest in speaking to people. Face to face verbal communication is paramount to support other tools such as surveys and diagrams. Incumbents must be interested in understanding not only the pieces that comprise a system, but the people that comprise it and the realities that embrace the system. Briefly, the Business Analyst must understand and not judge the "what should be" and the "what is".
dmitra
- Jul 9th, 2010
When you have about 3+ months of BA experience, you will understand the path you should take from there..Business Lead is awarded to you based on your ability to perform as a leader..otherwise, BSA- B...
Lon Harvey
- Jan 25th, 2007
A Business Analyst in the IT field has many varied directions among which to choose a career path. The most direct would lead to a Lead Business Analyst position and then Project Manager whereby the i...
-
What are the list of documents that a Business Analyst needs to maintain?
dmitra
- Jul 9th, 2010
As a Business Analyst, your BA life depends and revolves on the following documents (better known as Deliverables in the BA world):BRD-Business Requirement DocumentURD-User Requirement DocumentFRD- Fu...
deepankar_joshi
- Sep 26th, 2007
Depends on what methodology you follow.For a SDLC cycle : you would idealy prepare :BAD/BRD, then SRA then SDS and TSD.You might need to maintain the Change Request Forms as project progressesFor a DS...
-
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
-
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
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...
-
Business processes
Business processes and finance operating model within the Domestic arena...means what..? Please explain
vasudeo007
- Oct 12th, 2008
Ok. It seems that you are working for some Indian company.Domestic arena means within India or US wherever. The opposit of domestic is international. So international arena means that the software may...
-
What types of requirements should not be documented in use cases?
megrath
- Sep 30th, 2008
Any non- functional requirements[example:usuability,design,performance..] that cannot be directly realted to the usecases should not be documented in Usecases. These non-functional requirements are documented in Supplementary Specification Document.
chrisraeht
- May 19th, 2008
Use cases should be written from the user point of view. How should the system function when using it. So don't include "behind the scenes" specifics like what is stored in t...
-
Stake holder's mind
How do you handle a stakeholder who changes his mind in the middle of the project?
willsmith3
- May 23rd, 2008
Need to consider following steps to handle "Change in Requirements" by Stake Holders- Why do need to change requirements?- Who has raised the change of request and how im...
-
Role of Test Manager
What are the duties or role of a test manager?
priyankam9
- Apr 27th, 2008
To ensure that requirements are tested and entered into their testing m/c.To ensure that Test Cases and Test Scripts are developed properly and are linked to requirementsFrom time to time work with BA...
-
Explain how RUP is used and its different from Agile?
Rams235
- Feb 6th, 2008
on the commonalities and differences between agile methods and the Rational Unified Process (RUP): “At their root, the RUP and agile methods share a number of common values: the primacy of execu...
Rams235
- Feb 6th, 2008
The Rational Unified Process (R) is a Software Engineering Process. It provides disciplined approach to assign tasks and responsibilities within any Software Development Organization. Its goal is to e...
-
How do you handle the situation when users are not co-operative while gathering the requirements?
deepankar_joshi
- Sep 26th, 2007
At the first place you don't want to be in that situation as its is a difficult situation to be in.So you need to set the expectations right when you meet first.Meet the business users face to fac...
-
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.)
Business Analyst Interview Questions
Read Best Answer
Ans