Business Analyst

1. Business Analyst
Companies:
There are two types of companies.
1. Product based company:
 Product based company develops the applications for Global clients i.e. there is no specific
clients.
 Here requirements gathered from the market and analyzed from market.
2. Service based company:
 Project based company develops the applications for the specific client.
 Here requirements gathered from the client and analyzed with the client.
How the project comes to company and the process to developing the software
project?
 Client will prepare and distribute for Request for Proposal (RFP) to selected vendors (software
companies).
 Software companies respond to RFP with the proposal about the company information, Technical
tools, Technical solution, Delivery schedule budget, timeline and deliverables. It comes to RFI and
RFQ.
 If client likes proposal from any vendor then they will sign the statement of work (SOW) with the
vendor (Work order).
 Conduct project Kick-off Meeting. It is high level meeting between the senior manager, project
manager and chief technical officer.
 Project manager will prepare the Project management plan.
 After high level meeting with the customer Business team will prepare the Business Requirement
Document (BRD).
 BRD is a high level document containing project requirements from customer.
 Functional expert will convert the document from BRD to SRS (Software requirement
specification).
 Based on approved SRS software architecture will design the model of the project. It contains
Modules, DB design, UI design, UML diagrams.
 Review and approval of design of project documents mapping design documents with
requirements.
 Based on approved design documents developers are going to convert the logic specified in the
design document in to coding as per chosen programming language and they will release the
code (LOC).
 Perform code reviews.
 Once code is approved developers perform UNIT LEVEL TESTING.
 Once approved the UNIT LEVEL TESTING, developers will integrate the units and releases the
code to testers to testing the project.

2. Business Analyst
 Testers write the test case executions and writes test results with pass and fail.
 Testers perform Functional testing, Non Functional testing, Retesting and Regression testing.
 Once integration testing approved, perform system level testing.
 Again perform Retesting and Regression testing.
 If a tester raises any issues developers are going to fix the defects which are reported by testing
department.
 Once system testing is approved, releases the application for UAT (User acceptance Testing).
 Once UAT approved, release the application for production.
 Provide support to the customer for defects/issues and future enhancement.
Process of developing:
RFP
RFI & RFQ
Kick-off Meeting
BRD
SRS
Design
Developers Testing
Coding
Unit level Testing
UAT
Production
Support/Maintanance

3. Business Analyst
Roles and Responsibilities of a BA:
 Identifying stake holders
 Gathering requirements from stakeholders
 Preparations documentation on BRD, FSD etc...
 Preparation of proto types
 Clarifying Issues raised by Technical Team
 Preparing User manuals documentation
 User training to end User Product
Skills required for a BA role:
 Excellent communication skills
 Good assertive skills
 Good negotiation skills
 Good documentation skills
 Management skills is plus
 Understanding on the technical side is a plus
Documents prepared by BA:
Business Requirement Document:
A business requirements document (BRD) details the business solution for a project including the
documentation of customer needs and expectations.
The BRD process can be incorporated within a Six Sigma DMAIC (Define, Measure, Analyze, Improve, and
Control) culture.
Business Requirement Document should talk about the following features
 Introduction:
The purpose of this document is to describe business requirements of an Application completely.
Use case / Designer approach are used in modeling the business requirements in this document. The
major goals / objectives to be achieved with the implementation of the Business Requirements . Major
assumptions that were made prior to or during the Business Requirements gathering and documentation.

4. Business Analyst
 Requirement scope (features & time lines):
In this shows what business functionality is in scope and out of scope for Implementation.
In Scope:
Which is in requirement it implements and need delivered to client.
Out Scope:
This is in requirement it is not to implement and need not deliver to client.
 Functional Requirements (behaviour).
These requirements specify and how the system behaves in terms of functionality.
Example: Login, Write & Edit mail in function requirement.
 Non Functional Requirements (other aspects).
These requirements specify the other aspects such as response time and performance the system.
Example: How much time should be taken to login is the nonfunctional requirement.
 User Interface (look & feel, drop down menu, check boxes).
BA actually gives shape, present the requirements in a user friendly interface. The process can be started
by initial level of wireframes preparation by BA himself and later on converting them into HTMLs with the
help of web designers.
 Appendix / Business Glossary (terminology).

5. Business Analyst
What is Requirement Elicitation?
A major goal of requirement elicitation is to avoid confusion between stakeholder and analys t.
Requirement Elicitation means extract the requirements.
• Interview:
Analyst discusses the desire product with different stakeholders and develops an understanding
requirement. An interview, generally conduct by an experienced analyst, who has generic knowledge on
application domain. Interview divided in to two groups.
Open-ended interview: In this we do not need do prepare predefined questions and the information from
stakeholders in open discussions.
Close ended: In this we have to prepare some predefined questions and to get answers for this question
for stakeholder.
• Questionnaire:
Questionnaire is one of the method to gathering requirements in less cost. Mainly it affects types of
requirements that has to be gathering depends on his respondent’s knowledge and background.
• Brainstorming:
Mainly in brainstorming concludes the requirements. In brainstorming stakeholders are gathering
together in a short time period, in short time they develop a large and broad list of ideas. “Out -of-box”
thinking encourages in brainstorming.
• JAD/RAD Sessions:
“I Will check with my boss should not heard in JAD session.”
JAD is conducted same as brainstorming except that the stakeholders and the users are also allowed to
participate and discuss on the design of the proposed system. The discussion with the stakeholders and
the users continues until the final requirements are gathered.

6. Business Analyst
What is Gap Analysis?
Gap analysis is the technique to identify the area of improvement. The areas of improvement doesn’t
mean any new enhancement, it is about finding a gap between what is expected and what is really done.
We have two things to compare against. The first thing is the current state and the next thing is the future
or expected state of the improvement.
For Example: Business Analyst work as an Enterprise BA and he is working on a Project plan. Now, as the
project plan gets extended into high level requirement document then this a perfect time when you will
have both current state and the future state. An Enterprise BA will then compare that Project Plan with
the Higher Level requirements, which is also called gap analysis and try to find out what are the gaps that
BA missed to include in the requirements.
What is SWOT Analysis?
A SWOT analysis is a structured planning method used to evaluate the strengths, weaknesses,
opportunities and threats involved in a project or in a business venture. A SWOT analysis can be carried
out for a product, place, industry or person.
 Strengths (Internal): Characteristics of the business or project that give it an advantage over
others.
 Weaknesses (Internal): Characteristics that place the business or project at a disadvantage
relative to others
 Opportunities (External): Elements that the project could exploit to its advantage
 Threats (External): Elements in the environment that could cause trouble for the business or
project
Methodology and Models:
Methodology can be defined as the concept for implementation or the concept behind
anything.

7. Business Analyst
Model is the output of mixed methodologies or implementing few methodologies results in a
model.
There are Six Types of Model:
1. Waterfall Model.
2. Spiral Model.
3. V Model.
4. Iterative model.
5. Validation and Verification model.
6. Agile model.
Now, Most of organizations are using agile methodology.
Agile Methodology:
What is Agile?
Agile is a time boxed, iterative approach to software delivery that builds software incrementally from
the start of the project, instead of trying to deliver it all at once near the end.
It works by breaking projects down into little bits of user functionality called user stories prioritizing
them, and then continuously delivering them in short two week cycles called iterations.
• The advantages of agile methodology are
i) Faster in terms of delivery
ii) This can be implemented even during the scope creep or even at the beginning of a project
• The agile methodology consists of Scrum Model and Extreme Programing

8. Business Analyst
 COMPOSITIONS OF SCRUM MODEL
a) Scrum master (Project Manager)
b) Product owner (Business Analyst)
c) Scrum meeting (Daily Stand up, achievements from last scrum to present)
d) Sprint meeting (functionalities have to be achieved in sprint durations)
e) Sprint backlog
f) Product backlog
g) Sprint retrospective meeting
EXTREME PROGRAMMING
• PLANNING
Requirements are gathered from different stake holders and written in the form of stories
and are prioritized.
• SIMPLE DESIGN
Writing the code in the most simple manner.
• PAIR PROGRAMMING
Two programmers working on one requirement.
• TEST DRIVEN DEVELOPMENT
Identifying the problems even before they are executed.
• REFACTORING
Continuous development and testing.

9. Business Analyst