Company: XYZ IT Company
Role: Business Analyst
Type: Full Time
Location: Houston, TX
Joining: 0 to 30 days / Immediate Joiners preferred
pay rate: $45 per H/R
Business Analyst interview experience
Q)What are skills required for business analyst?
Skills required for business analyst:
1)Analytical skills
2)Technical skills
3)Manegerial skills
4)Negotiation skills
5)excellent communication and writing skills
Q)Sequence to write a test case?
Test script, test data, test scenario, use case. - given sequence From the Use Case, you derive a Test Scenario, Design it in a functional flow, author test matrix if necessary, then write a test script, and supporting information is the Test Design. - the sequence to be followed
Q)Business Rules ?
The Business Rule the Functional Requirement satisfies as the IT solution to the need identified in the BRD is documented and mapped in the Functional Requirements document
Q)Difference between PM and BA ?
BA - Business Analyst studies the requirement of the client and make documents like - BSD(Business Specification Document), FSD(Functional Specification Documents). He also discusses the technical feasibility of the requirements with developer.
PM - Project manager - The project manager plays a very significant role in the initial planning, finalizing project requirements, and resource allocation. A project manager has to assess what the client demands, what all resources he has, what has to be added to the resources, and how the project work is to be carried out.
Q)How you proceed to convert Business Requirement till the signoff on the documents?
Once the project is initiated, its Scope is defined. Analyze the project scope and its dependent applications within the system and find out the impact analysis. Do some homework on gathering the requirements to achieve the project goal.This can be done by identifying the stakeholders, end-users and brainstorming,taking interviews,conducting meetings or JAD and document the Business Requirements.
Once the requirements are gathered, review the document,make appropriate changes,take the sign-off from the project stakeholders and freeze the requirements. Any new requirements after freezing the document will go into traceability matrix and accordingly the deadlines will be changed. Once the BRD is clearly defined, go for the next step viz, functional requirements gathering and documentation.
This document tells what technology needs to be used and how to implement the requirements specified.It contains the details regarding the platform used, memory space required, technology, performance impacts,etc. Once FRD is done, jot down the positive and negative test cases, test criteria, test data. Testing criteria will also aid in development of the product in an efficient manner.
Once development is started, unit testing will be carried out by Developers and system integration testing will be carried out by testing team. UAT will be done by end-users. Performance or load testing is carried mostly after the end-user testing.
Defects found during testing needs to be documented and fixed as per the timelines. once the defect fixing is done, the product is ready to go live. There can be production issues during delivery of the product, these defects need to be identified and fixed. After go-live stage, the project comes under maintenance support.
Q)What is the difference between BRD, SRS and Use Case documents?
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 that is to be developed i.e., how the application is to be developed.All the features are related to BRD needs.
UCD: it is diagramatic representation of the features documented in SRS
Q)Business Analyst Domain Expertise
Does a Business Analyst need domain expertise? Justify.
The answer is NO, because every BA had to have started somewhere!
The best way to answer this question..is questioning how well you can adapt and your research and understanding ability...remember, this is an interview process...the decesion is made on your best ability to answer the question..so when this is asked and you do not have a specific domain experience, talk about your "fast learner" and possessing the skills of ADAPTATION to the limit
Q)Business Rule & Business Validation
What is the difference b/w Business Rule & Business Validation ?
The business rules are the core rules and regulations of a business which have to be considered wherever the business is impacted . Be it a change or an enhancement or deletion .Business validation is a procedure of measuring or assessing a business in terms of its market impact and value . It is mostly used in finance environments .
Q)How will a BA gather requirements if the business object is to build equity trading system?
Techniques for Requirement Gathering:
1) Requirement Walkthrough or Discovery Session with Business Stakeholders (or SMEs)
2) Brainstorming
3) Interview
4) Questionnaire / Survey
5) Document Analysis
6) Observation such as Job Shadowing
7) Prototyping
8) Interface Analysis
9) Focus Group
Q)Requirements
How a BA handles Business Recks, User recks, Functional recks?
Business requirement is most important part of the organisation.
In particular Software company Requirements and development both are two side of coin.
So if requirement specifies quickly and efficiently than Development of product or project is also start quickly and effectively.
There are certain types of requirements like software or Business both consist their different different importance.
Business requirement documents consist code of policies, cost of project, terms and conditions , understanding, and over all Business approval and acceptance documents.
while Users requirement refers need of User, what actually wants the User and all, It consist Purpose and features that he wants.
Q)If you are asked to include particular requirement in current requirements ,what will you do ?
for BA it is always a tough job when it comes to change s in requirements when the project is in ongoing process,but as a BA we have to do it ,analyze those proposed requirements and find if any impact is they on related tasks,so on after that we will inform the client about it if we have to change requirements then automatically budget and schedule will increase if the client agrees for that we will proceed by discussing with my project manager
Q) How would you transform business requirements to functional requirements?
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.
Q)Evaluating existing processes ?
Describe your experience evaluating existing processes and recommending updates or enhancements?
For most of the Change Management procedures, the evaluation of existing system has to be done with an AS-IS process analysis. This may be done with document analysis or by other requirement eliciting methods. Once the analysis is done, the evaluation should be done by cause-effect or SWOT methods
Q)How do you handle User Conflict ?
I think the best way to handle user conflicts is to document all the user requirements and send a copy to the user via email and ask for his sign off. This way you will have proof of what you (BA and User) initially agreed upon while gathering the requirements. So if at all user changes his word at the end, you have the proof and you can show him what you initially agreed on.
Q)BRD & FRD
What is the difference between business requirement document(BRD) and functional requirement document(FRD)?
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
Q)Non Functional Requirements
What are the Non Functional Requirements and what factors make them a good NFR?
Non-functional requirements are requirements that captures the condition which describe environmental condition under which. The solution must remain effective or qualities that the system must have
Post a Comment