1) Explain Waterfall model:

Ans: This is the most common and classic of life cycle models, also referred to as a linear-
sequential life cycle model. It is very simple to understand and use. In a waterfall model,
each phase must be completed in its entirety before the next phase can begin. At the end
of each phase, a review takes place to determine it the project is on the right path and
whether or not to continue or discard the project.

2) Explain V Model:

Ans: The V model SDLC methodology would be best for this project. This is a small project and V
model works well for small projectIn this project the requirements are very well understood and in
the V model in each phase testing and reviewing done, this is how we will know that this project will
be going on correct path or not.
Advantages
>Simple and easy to use.
>Easy to manage due to the rigidity of the model - each phase has specific deliverables
and a review process.
> Phases are processed and completed one at a time.
>Works well for smaller projects where requirements are very well understood.
Disadvantages
> Adjusting scope during the life cycle can kill a project
>No working software is produced until late during the life cycle.
>High amounts of risk and uncertainty.
>Poor model for complex and object-oriented projects.
>Poor model for long and ongoing projects.
>Poor model where requirements are at a moderate to high risk of changing

3) Explain Iterative - RUP (Rational Unified Process)

Ans: The Rational Unified Process (RUP) is an iterative software development process
framework created by the Rational Software Corporation, which was acquired by IBM in
February 2003.
RUP is based on a set of building blocks, or content elements, describing what is to be
produced, the necessary skills required and the step-by-step explanation describing how
specific development goals are to be achieved. The main building blocks, or content
elements, are the following:
Roles (who) - A Role defines a set of related skills, competencies and responsibilities.
Work Products (what) - A Work Product represents something resulting from a task,
including all the documents and models produced while working through the process.
Tasks (how) - A Task describes a unit of work assigned to a Role that provides a
meaningful result.
Design Tech Team - Sol Arch, NW Arch,
DB Arch, GUI Designer
HDD / ADD Solution Document
Development
-
coding
Programmers Developers LD /CDD Application
Testing Testers Test Documents
Application with less Errors
Resources Artifacts
StagesWithin each iteration, the tasks are categorised into nine disciplines:
Six engineering disciplines: Business Modelling, Requirements, Analysis and
Design,Implementation, Test and Deployment.
Three supporting disciplines: Configuration and Change Management, Project
Management and Environment.

Four Project Life Cycle Phases:

Inception : agreement among the team and customer as to what will be built
Elaboration: agreement within the team as to the architecture and design needed to deliver
the agreed system behaviour.
Construction: the iterative implementation of a fully functional system.
Transition: delivery, defect correction, and tuning to ensure customer acceptance.
Six best practices
• Develop iteratively, with risk as the primary iteration driver
• Manage requirements
• Employ a component-based architecture
• Model software visually
• Continuously verify quality
• Control changes

4) Explain Spiral model

Ans- The spiral model gives more emphases placed on risk analysis.
The spiral model has four phases: Planning, Risk Analysis, Engineering and Evaluation.
A software project repeatedly passes through these phases in iterations (called Spirals in
this model). The baseline spiral, starting in the planning phase, requirements are gathered,
and risk is assessed. Each subsequent spiral builds on the baseline spiral.
Requirements are gathered during the planning phase. In the risk analysis phase, a
process is undertaken to identify risk and alternate solutions. A prototype is produced at
the end of the risk analysis phase. Software is produced in the engineering phase, along
with testing at the end of the phase. The evaluation phase allows the customer to evaluate
the output of the project to date before the project continues to the next spiral.
In the spiral model, the angular component represents progress, and the radius of the
spiral represents cost.

Advantages
a. High amount of risk analysis.
b. Good for large and mission-critical projects.
c. Software is produced early in the software life cycle.
Disadvantages
a. Can be a costly model to use.
b. Risk analysis requires highly specific expertise.
c. Project's success is highly dependent on the risk analysis phase.
d. Doesn't work well for smaller projects.

5) Explain Agile - Scrum

Ans: Agile Light weight can be implemented where faster delivery is required.
No documentation
Customer retention - since there is no documentation.
The code in itself forms as documentation
Not support scalability and extendibilitySDLC life cycle cut down by employing seasoned
DEVELOPERS
Four main Values
Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan
Twelve Principles of Agile Software
1. Satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness
change for the customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with
a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support
they need and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a
development team is face-to-face conversation.
7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and
users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity--the art of maximising the amount of work not done--is essential.
11. The best architectures, requirements, and designs emerge from self-organising teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and
adjusts its behaviour accordingly.
SCRUM can be implemented either at the beginning of the project or when you sense that
project is falling behind schedule. This model exercises full Admin Power.

6) BA's Role in Agile Scrum:

Ans: To Start with, once a project is kicked off, BA does the requirement Planning, then
conducts various requirement gathering sessions and analyses the requireent.
Finally, the requirement is listed as 'FEATURE LIST.' This Feature list is drafted by BA and
discussed with Product Owner. This feature list will have all enhancements and existing
features (If it is a migration project).
From the Feature List, BA identifies the Epic and breaks them as Themes and then to User
Stories.
User Stories will have below Information:
As a <User>
I Want to
<What is the Purpose>
So that
<What you gain by this story>
Eg: As a Customer
I want to
Login to the net banking site
So that
I can perform banking activities

7) Difference between waterfall and V model

Waterfall V-Model

Cost low Expensive

Testing activities start at the later stage Testing activities start with the rst stages

Move in linear way Dont move in linear way

Less customer involvement More customer involvement

8) Share your knowledge on Fixed Bid model and Billing Model.

Ans:

Fixed Bid: A fixed bid project is one in which the service provider agrees to deliver a
specific scope of work for a fixed price. The scope of work, deliverables and timelines are
agreed upon upfront and the service provider assumes the risk for any cost overruns or
delays. For an example our project budget is 2 cr and time is 18 months.

Billing Project: A billing project is one in which bills the client for the actual time and
materials expended on the project. The client pays for the service provider’s time and
fi
expenses and the scope of work can be adjusted as needed throughout the project. So in
billing mode sponsor will give funds as per the working hours completed in each stage or
on weekly, monthly basis.

9) Explain and illustrate 3-tier architecture?

Ans. 3-tier architecture is a well-established software application architecture that organises

applications into three logical and physical computing tiers, The business logic layer, the
application tier, where data is processed and the data tier , where the data associated with the
application is sorted and managed.
Application Layer: Agricultural mobile app screen, login page, functionality
Business logic layer: Payment methods, Agricultural company’s details, specific rules
Database layer: Company’s details, product details data, farmer’s data.

10) As a Business Analyst, What Elicitation Techniques you are aware of?
( BDRFOWJIPQU)

Ans. Elicitation Technique

1. Document Analysis - Document analysis is done through reading document and understand
the product, process and project. This analysis is helpful to validate the implementation of
current solutions and also helpful in understand the business needs. It includes reviewing the
business plans, problem reports, existing requirement documents, technical documents, etc.
This technique is important in identifying the gaping the systems i.e. to compare the AS-IS
with the TO-BE process. This analysis helps when the person who has prepared the existing
documentation is not present in the system.
2. Reverse Engineering - It is also called back engineering, is the process of extracting
knowledge or design information from anything man-made and reproducing it or reproducing
anything based on the extracted information.
3. Focus Group - A focus group means to elicitate ideas and attitude about a specific product,
service, opportunity in an interactive group environment.
4. Observation - Observing, shadowing users or doing a part of their job, can provide information
of existing processes, inputs and outputs.
5. Workshop - A workshop is a structural approach to capture requirements. A workshop maybe
used to scope, discover, define, prioritise and reach closure to the requirement to the target
systems.
6. JAD - Joint Application development. Application develop through JAD has higher customer
satisfaction and less numbers of errors as users are directly involved in the development
process.
7. Interview - An Interview is a systematic approach where the interviewee is going to ask
relevant questions related to software and documenting the response. There are two types of
Interview. - One to One, - Group
8. Prototyping - Prototyping is an attractive idea for complicated and large system for which
there is not manual process or existing system to help determining the requirements. In these
techniques frequent demos are given to the client by creating the prototypes so that the client
can get an idea of how the product will look like. It describes the process using diagrams.
9. Survey/ Questionnaire - Questionnaire can be useful for obtaining limited system requirement
details from the users or stakeholders, who have minor input or are geographically remote.
10. Brainstorming - it’s an effective way to generate lots of ideas on a specific issue and then
determine which idea is the best solution. This session is generally conducted around a table
discussion. All participants should be given n equal amount time to express their ideas. Below
questions are used for brainstorming techniques.
1. What is the expectation of the system,
2. What are the risk factors which affect the proposed system development and how to
avoid.
3. What are business and organisation rules required to follow.
4. What are options available to resolve the current issue.
5. Managing issue logs for future perspective.

11) Make a note of the Tools.

Ans: The tools used are listed follow:
- MS Visio is software for drawing variety of diagrams. These include flowcharts, org charts,
building plans, floor plans, data flow diagrams, process flow diagrams, business process
modelling, swim lane diagrams, 3D maps and many more. It can be utilised for building picture
like flowcharts, choice of graphs and network diagrams.
- Balsamic is a interface design tools for creating wireframes ( sometimes called mockups or low
fidelity prototype). You can use it to generate digital sketches of your idea or concept for an
application or website, to facilitate discussion and understanding before any code is written.
-
Draw.io is a simple but powerful tool mainly used for creating diagrams, although. It can be
used for wireframe, charts and more. You can use Draw. io's drag-and-drop interface to
create your wireframes from a variety of shapes, icons, and images

12) Explain UAT Acceptance process

Ans: > Planning - Planning is all about outlining the strategy for the UAT test that needs to perform
on the project. In this step blueprints are made to implement UAT and it will help to look at the
standard to accept the test.
> Designing - In this phase test cases are designed to collect acceptance criteria from the users.
Here in designing phase will check which test cases will be used in real world situation.
> UAT Testers - In this phase a testing team will run this test cases, testing team consists of end
users that meet the criteria of implementing testing. The end user must have expertise to identify
bugs.
> Bug Fixing - In this phase development team will get involved and whatever bugs are found in
UAT testing they should work on that and fix those bugs and make software error free.
> Sign-off - After removing all bugs when testing team indicates the acceptance of the completion
of bugs then as BA I will contact with clients and go to them to test the software that it is running
successfully for the users and ready to go-live and sign it off from client.

13) Explain the Type of requirements.

Ans: Types of Requirements -

1 Business Requirements
2. Stakeholder Requirements
3. Solution Requirements
a. Functional Requirements b. Non-functional Requirements
4. Transition Requirements

Business Requirements are higher-level statements of the goals, objectives, or needs of the
enterprise. They describe the reasons why a project has been initiated, the objectives that the
project will achieve, and the metrics that will be used to measure its success. Business
requirements describe needs of the organization as a whole, and not groups or stakeholders within
it. They are developed and defined through enterprise analysis.

Stakeholder Requirements are statements of the needs of a particular stakeholder or class of

stakeholders. They describe the needs that a given stakeholder has and how that stakeholder will
interact with a solution. Stakeholder requirements serve as a bridge between business
requirements and the various classes of solution requirements. They are developed and defined
through requirements analysis.

Solution Requirements describe the characteristics of a solution that meet business requirements
and stakeholder requirements. They are developed and defined through requirements analysis.
They are frequently divided into sub-categories, particularly when the requirements describe a
software solution:

Functional Requirements describe the behavior and information that the solution will manage. They
describe capabilities the system will be able to perform in terms of behaviors or operations- specific
information technology application actions or responses.
Non-functional Requirements capture conditions that do not directly relate to the behavior or
functionality of the solution, but rather describe environmental conditions under which the solution
must remain effective or qualities that the systems must have. They are also known as quality or
supplementary requirements. These can include requirements related to capacity, speed, security,
availability and the information architecture and presentation of the user interface.

14) Bond between Requirement and BA

The BA always ensure that the Client Requirements are properly gathered or collected,
communicates the same to the Technical Team in UML language which is more understood to
them.
He communicates to Client in Business language. BA nurtures these requirements into an IT
Solution with the help of the Technical Team. Generally, the technical Team will be headed by the
Project Manager (PM). PM takes care about the technical aspects of the Project, Team
management and delivery of the project within Time frames. BA will be in continuous track of the
Client Requirements through al the different stages of Project development Life Cycle. He helps
the technical team to understand the Requirements clearly and participates in UAT along with
Client. nI short, we can say that "BA takes the ownership of the Client Requirements”.

15) What is Business Process Modeling?

Ans: A business process:

1. Has a Goal
2. Has specific inputs
3. Has specific outputs
4. Usesresources
5. Has a number of activities that are performed in some order
6. Creates value of some kind for the customer. The customer may be internal or external.

A business process is a collection of activities designed to produce a specific output for a particular
customer or market. It implies a strong emphasis on how the work si done within an organization,
ni contrast to a product's focus on what. Aprocess si thus a specific ordering of work activities
across time and place, with a beginning, an end, and clearly defined inputs and outputs: a structure
for action.

16) Risk Analysis and Management

Ans: An uncertain event or condition which can have impact on either cost, time, scope or
quality Risk Analysis is done to determine if the proposed project carries more risk than the
organization's capacity to support

Risk Identification
It is the process to identify the business, financial, technological and operational risks

Risk Assessment
It is the process to identify the probability of occurrence of each identified risk. BA s have been
given tasks to arrive at a consensus for each identified risk item.

Risk response planning

This includes the planning that reduces the
probability of occurrence of risk. the response
planning helps in determining the conditions against which the required actions can be
taken. tI helps the organization to deal with risk. This planning includes
• Acceptance
• Transfer
• Avoidance
• Mitigation

Risk Avoidance
It is the process of not performing risk causing activities. Risk Avoidance is defined as being idle
during the occurrence of risks and doing nothing to take advantage of the new opportunity.

Risk Rating
Each identified risk is rated before moving ti
to rectification process. This process si called
Risk ratings. The overall risk ratings are calculated ni terms of cost, time, Quality of the solution

RISK - Change in Requirements - Requirements are inherent to Change Always requirements are
prone to change

17) BA Thumb-rules

Ans : Solve Client Problem only by our IT Solution

As a Business Analyst, we should not probe into the reasons of the Business failure and advise
solutions to come out of it, instead we should concentrate more on providing the Client with an TI
Solution by considering the information available with the Client in different forms., through which
the Client will solve his problem.

Be like a lotus in the mud

"The one who wanders independent ni the world, free from opinions and viewpoints, does not
grasp them and enter into disputations and arguments. As the lotus rises on its stalk unsoiled by
the mud and the water, so the wise one speaks of peace and is unstained by the opinions of the
world." Buddha Saying. BA shines by making the development Team to deliver the right Solution on
time to Client. This can be done by bringing Clarity in Requirements and communicating the same,
in understandable format, to the Development Team. He should be influenced by the Client views
or the development Team views, his concentration should lie in molding the requirements to bring
out a perfect TI Solution.

Never take tensions but pass on the tensions

As a Business Analyst, you should not take tensions. Al that comes from the Client is in reference
only to the project. The Client never intends to say anything personal, since a Business Analyst is
the only point of contact to the Client, the Client tends to shell out all his concerns on this contact.
Business Analyst should be invincible to any of the Clients comments as it may affect the rest of
the projects that he is working on.

Requirements hurried - Project buried

Do not haste while gathering the requirements, giving in to due stress levied upon you by your
Manager. Project success majorly depends on the key requirements. The basic idea of gathering
the requirements is to realize the organizational goals. So, ti is very important to understand the
business process and its requirements but not on the individual requirements. We have to
document everything that we have gathered from the Client. Identify the right stakeholders, who
are going to proposed Solution. Gather requirements in Detail enough. Try to understand business
Goals and Objectives and not requirements alone. Document everything you find useful to the
project. Involve users - the actual users. See them at work. Look for the unhappy path. Get behind
the scenes. Observe them how they work when something unusual happens in the process. Pull
out those documents. Always try to build a new system- don't copy the old one. See the reports
and the folks who use them

Never criticize any stakeholder - appreciate them even for their small efforts
As a Business Analyst, you have to manage good public relationships along with Professional
relationships with all associates. To be recognized as a reliable and trust worthy Associate of the
organization, you should never speak il of any stakeholder to any stakeholder. If people start
trusting you, then your contribution will be easy.

18) Dos and Don'ts as BA

Ans: Never say NO to Client

There is NO word called as "BY DEFAULT"
Never imagine anything in terms of GUI
Question the existence of existence / question everything in the world
ex: what client gives is not always correct
Consult an SME for Clarifications in Requirements
Every Problem of Client is unique. No two problems of different Client are same. May be the
approach, technology, place of use, local laws may be varied to make them (Problems) to be
different.
Go to Client with a plain mind with no assumptions. Listen carefully and completely until Client is
done and then you can ask your Queries. Please do not interrupt the Client, when he/ She is giving
you the problem. Maximum Try to extract the leads to Solution from the Client itself. Never try to
give Solutions to Client straight away with your previous experience and assumptions. Try to
concentrate on the important and truly required Requirements. Don't be washed away by add on
Functionalities or don't imagine solutions on Screen basis.

19) What is SPRINT

Ans: Sprint
A sprint is a scrum-based agile methodology concept that is similar to an iteration. A sprint is time
boxed to deliver a specific set of user stories and produce working features within a set time
period. During sprint planning, the business customer or product owner specifies the user story
priority, and the development team commits to the scope for a given sprint. During a sprint, user
stories can be removed from the sprint scope, but new stories cannot be added; this allows project
teams to focus on the goals of the sprint and deliver rapidly.

20) What is Story points

Ans: A story point is a relative estimation method used to determine the size of user stories so
teams can determine how much work can be done during an iteration. Story points can be
expressed in a simple Fibonacci sequence, -t shirt sizes, or a relative number. By adding up the
number of user stories and associated story points, the project team can establish its velocity for
future iteration planning.