Q1) What is the % of BA in Team Size and Project Duration?

A Business analyst works along with the technical team and acts as a liaison between stakeholders client
and the technical team. He is the face of the technical team to the client and all clients communications
will happen through a business analyst. He/she will elicit, analyze, communicate and validate
requirements for changes to business process, policies and information systems in the exiting business
proves of the client. The business analyst understands business problems and opportunities in the
context of the requirements and recommends solutions that enable the organisation to achieve its
goals.

The BA’s involvement in project is 12% to 16% in the team size i.e. 2 BA's in 12 to 13 team members or 4
BA's in 24 to 25 team members.

The allocated time for BA for each project is 15% of the project i.e. 2 months time period in 1 year of
project.

Q2)What is the role of BA in a product development IT Company ?

A BA is typically involved in analyzing the structure of the business, its processes and determining areas in which
technology or alternative solutions can add value. Business analysts often work together with system analysts, who also act
as link between business challenges and technology solutions.

In product development company BA's responsibilities are

a) first understand the product domain thoroughly

b) understand the product features
c) understand where product fits in to domain
d) understand clients requirements for the product
e) and study what all customizations are required for the product to fit into clients requirements

Q3. Explain Agile & Scrum Process?

Agile process

Agile means light so here agile means easy to model maintain and track. Agile process is used or
implemented when faster delivery is required. In agile no documentation is required since there is no
documentation customer retention is possible as there is no documentation code itself becomes the
documentation and SDLC life gets shorter by employing seasoned developers

Scrum process

Scrum process is used or implemented when project is falling behind the schedule. It is to get the
project on fastrack pace to reach the specified delivery time of the project. Here a scrum master
administrates the project with scrum team around 7 to 8 members team including developers technical
team and BA's scrum master resolves issues and gets the allocated work done in decided sprint, here
sprint is of 2 weeks but may get stretched to 4 weeks.

Q4) List all diagrams of UML and draw samples ?

Unified modeling language is used to specifying designing simplifying and understand the software
system.

UML : The industry-standard language for specifing, visualizing, constructing and documenting software
sysytem design and communication about the design.

A) Static-5 Diagrams B) Dynamic-4 Diagrams

1. Use Case 1. Sequence
2. Class 2. Activity
3. Component 3. State Chart
4. Package 4. Collaboration
5. Deployment

 use case diagram : This is a high level diagram and mother of all diagrams. The main focus
of this diagram will be on “how external interfaces” (End users, support sysytems, special
database and internet connectivity to third party) will be interacting with the proposed IT
System. This interaction will be initiating District Business function called a Use Case and
show with an ellipse symbol.

Use Case Diagrams can be used to describe the functionality of a sysytem in horizontal way.
That is, rather than merely represnting the details of individual features of your system,
UCD’S can be used to show all of its available functionality. It is important to note, though
the UCD’S are fundamentally different from Sequence Diagrams or Flow Charts because
they do not make any attempt to represent the order or number of times that the system
actions and sub-actions in order to complete a task.

Example of use case diagram on next page

Q5)Explain Abstraction, encapsulation, polymorphism, Inheritance?

These steps are used to implement object oriented application

Abstraction:

abstraction means to filter out the properties and opportunities of the project until thr required one's
are remaining i.e. filtering out the required ones and ignoring the not required one's. It is most difficult
task to do for a modeler. The techniques used for this are

pareto principle-

80-20 or 20-80 technique where it is said that when 20% of the requriements are achived than 80% can
be achieved.

MVP-

Minimum value product

Gold plating-

It is the technique where making changes to the project outside the agreed scope. It takes time for
practice. It is used to enhance the product by adding extra features to it which were not asked by client
but to impress the client fot the same. It is vary rarely seen in practice.

Encapsulation
This is the information hiding technique, it is used to hide the complex internal structure or working of
the project.

In login system when we enter the submit button by entering userid & password it gets logeed in but in
background it follows commands to call the logged to in page only if the userid & password matched this
background hidden process is encapsulation.

Inheritance

whenever we have child class it inherits the parent class properties

Polymorphism

This means in simple language “one instruction-multiple operations”

sometimes single command can be used for multiple operations for ex. when we are shopping with
debit or credit cards we swipe at same swiping machine but the data will be sent to the concerned
banks .

Q6)what steps you follow to draw a use-case diagram from a Case study?

1) First we do not consider manual or physical action while drawing use-case.

2) No negative flow i.e. error or failure can be shown in use-case diagrams.
3) Information which we do not model in use case are
Names of the systems(laptops, desktops, workstations)

Databsase names( SQL server, DB2 etc.)

Networks(LAN WAN Internet)

Brand names(HP,INTEL,WIPRO,etc)

Technology names(Java,.net etc.)

4) different information against actions

5) Writing all the sequence of actions
6) find all the actors
 7) finding out which action is performed by which actor
8) finding which is essential cases and supporting cases
9) identify the modules with respect to functionality or usage
10) draw the relationships between identified actors and use cases

Q7) Why MVC Architecture is used? What are MVC Rules in identifying classes? What guidelines will
you follow to place the classes on a three tier Architecture ? What are persistence and Transient
classes?

The Model-View-Controller (MVC) architectural pattern is used in software engineering to allow for
the separation of three common features of GUI applications

The data access (typically via a database)

The business logic (how the data will be used)
~ The user interaction (how the data and actions will be visually presented)

MVC rules identifying the classes

1) combination of one actor and one use case result into one boundary class.
2) Combination of two actors and an use case result into two boundary class.
3) Combination of three actors and an use-case result into three boundary class.
4) Use case will result into controller class
5) each actor will result into entity class.

Guidelines to follow to place the classes on three tire architecture

1) Place entity classes on DB layer

2) Place primary actors associated boundray class in application layer
3) In governing body influence or re useability is there with any of remaining boundary classes,
place them on business logic layer, else place them on application layer.

Persistent class
Persistent classes in an application that implement the entities of the business problem.

It includes entity class.

Transient class

It includes boundary classes and controller classes

Q 8) What is a Requirement? How many types of requirements are there? Explain them with examples

A requirement in the context of Business Analysis is simply a statement provided by a stakeholder

about what they believe they need in order to solve a particular business problem or respond to a
specific business need. Once this requirement has been raised by the stakeholder it is the business
analyst’s role to further define, analyze, validate and prioritize the requirement statement as it is now
included within the business analysis context of requirements management. In real life, the stakeholder
will typically state their business problem or need and then provide a whole range of individual
requirements throughout the requirements management process managed by the business analyst.

An important point about Requirements Analysis

Before we start defining the different types of requirements it is important to point out that during the
Requirements Analysis phase of the project the Business Analyst starts with a broad and general
description of the what is required to be done (often a business need or problem description) and then
start working with the key stakeholders within and surrounding the project to define the Scope (what is
included and excluded in the project’s deliverables), Business Requirements (high-level requirement
statements), Stakeholder Requirements (which becomes more specific describing ‘what’ is required) and
finally delving into specifics of how to implement (with Solution Requirements and finally transition
requirements). It is therefore a journey working from a concept level right down towards a detailed and
specific requirements level.

Types of Requirements

1 ) Business Requirements 2 ) Stakeholder Requirements

3 ) Solution Requirements

There are two sub-types of Solution Requirements:

a ) Functional Requirements

b ) Non-functional Requirements
4 ) Transition Requirements

1 ) Business Requirements : The 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 enterprise analysis.

Business Requirement Example:

1)Build a family home to replace the home that was burnt down including the addition of a garage.

2)Reduce incorrectly processed order by 50% by the end of the next quarter.

2 ) Stakeholder Requirements: The stakeholder requirements are statements of the need 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 various classes of solution requirements. They are developed and define
through requirements analysis.

Stakeholder Requirement Example:

1) “We need a family house with four bedrooms so that each child has their own bedroom”

2) “We need the house to have two separate bathrooms to ensure the parents have their own
bathroom separate from the children”

3) “We need the house to be protected against future bush fires so that we don’t have to fear loosing
our house again”

These examples are requirements, which are describing “what” the family need the new house to have.
It is important to understand here that this type of requirement, the stakeholder requirement is not
stating how they want these requirements to be implemented, they are simply stating what is required.
As a Business Analyst you must guard against requirement statements at this early stage of the project,
which describes “how” to deliver the requirement. In the context of this example an example of a
requirement, which describes “how” rather than “what” is needed would be this: “The family’s little girl
states that she wants her bedroom to be painted pink with butterflies on the wall.” There are many
stakeholders that will do exactly what the little girl has done and tell you as the business analyst how
they want the solution to work before they have stated what exactly they are in need of. The little girl is
assuming that you know that she needs a bedroom and all she is concerned with is how the bedroom
will look.
3 ) Solution Requirements : 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.

Solution Requirement Example

1) “I want my bedroom to be painted pink so that everyone will know it is my room” – Stakeholder who
raised this requirement is the little girl.

2) “I want my bedroom floor space to be at least 30 square meters so that I can practice my skateboard
tricks in the bedroom” – Stakeholder who raised this requirement is the teenage boy in the family.

3) “Every bedroom must have an air-conditioning unit implemented so that the family can stay cool
during the summer” – Stakeholder who raised this requirement is the father in consultation with the
architect.

The solution requirements describe how the stakeholder wants to implement their stakeholder
requirements. In this example, the stakeholder requirement relating to having four bedrooms has been
expanded upon with more specific solution requirements describing how that stakeholder requirement
must be implemented (Solution requirements 1, 2 and 3 are expanding on that stakeholder
requirement). Take note here that as you progress with your Requirements Analysis you are delving into
more specific and detailed requirements

a ) Functional Requirements: Functional requirements describe the behavior and information that the
solution will manage. They describe capabilities the system will be able to perform in term of behaviors
or operations-specific information technology application actions or responses.

b) Non-Functional Requirements: 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.

4 ) Transition Requirements : Transition requirements describe capabilities that the solution must have
in order to facilitate transition from the current state of the enterprise to a desired future state, but that
will not be needed once the transition is complete. They are differentiated from other requirements
types because they are always temporary in nature and because they cannot be developed until both an
exciting and new solution are defined. They typically cover data conversion from existing systems, skill
gaps that must be addressed, and other related changes to reach the desired future state. They are
developed and defined through solution assessment and validation.
Transition Requirement Example:

1)The floors in the house must be covered with sheets to protect the carpets when the moving company
moves the furniture into the house.

Q 9. Write usecase specification for withdraw cash use case in an ATM ?

Usecase Specification : Allows any bank customer to obtain cash from their bank account from any ATM
machine. Any Customer can able to withdraw, Depositye, Transfer and Inquiry cash using ATM Card issues by
the bank. Customer can withdraw money only if money is available in a ATM Machine. Money can be withdraw
by few ways like Withdraw cash, Fast Cash. Customer can able to withdraw money according to his/her choice
(amount of money). For money withdraw customer need to insert ATM card inside the ATM machine. After the
card is inserted into the slot , customer need to enter his/her 4 digit ATM PIN, if the PIN is correct ATM will
allow to do a trasaction or else transaction will be canclled. Customer need to select few options like selecting
the account type, withdrawal type etc. If customer enter three times wrong pin then that card will be blocked by
his/her bank itself and he/she will not able to use that card. Customer should able to deposite cash in the ATM
viya CDM. After withdrawing the cash from ATM, customer get sms notification on his/her registered mobile
number and it also shows available balance. The system sends the transaction to the financial system for
verification. If the financial system approves the transaction, the machine dispenses the appropriate amount of
cash and issues a receipt. The dispensing of cash is also recorded in the ATM’s log.

Q 10.Draw a Use case Diagram and Activity Diagram.

 Q11. What are the roles and responsibilities of Business Analyst in givin phases ?

Phases Task of BA & Contributions Resources Associated & Artifacts

Pre-Projects - Market & Competetor Analysis - Artifacts: SWOT Analysis
and Research, report,
- Pre sales demo, - Available documentation
- Stakeholder Analysis, about the project,
- Feasibility of the - Tools : MS Suite,
solution/Product/Project, Cummunication tools.
- Helping PM in cost-benefit
analysis of the project.
Requirements - Selection of right method to - Artifacts : Project Charter
Planning gather requirement and - Tools : MS Suite
stakeholder communication,
- Stakeholder communication
planning and management,
- Help PM in formulating the
project management plans,
- Help in finding the project’s
Scope, constraints, assumptions
& risks.

Requirements - Requirements gathering ( by - Artifacts : Raw requirements,

Gathering client visit or virtual ), MOM, Documentation shared
- Liaise and enhance by clients
communications with - Tools: MS Suite, Virtual
stakeholders, meeting tool (Teams, Zoom,
- Getting signoff from clients on Skype,Webex)
gathered requirements.
Requirements - Eliciting the requirements, - Artifacts : BRD, FRD, SRS, USE
Analysis - Analyze, organize and CASE, FLOWCARTS
documenting requirements - Tools : MS Suite, JIRA or any
- Assess proposed solution, PM tool.
- Liaise and enhance
communication with
stakeholders.
Designs - Manage requirements by - Artifacts : Prototype, use
creating use-cases, Requirements cases, flowcharts, activity
tracebility Matrix, BRD, SRS, diagrams.
Flowcharts, Activity diagrams - Tools : Visio, MS Suite,
which will helpful to various Balsmic, PM tools such as JIRA.
stakeholders.
Coding/Developm - Communicating the requirements - Artifacts : Screen design
ent to internals stakeholders, documents for dev. Team,
- Clarify doubts, concerns RTM, maintain project
regarding the requirements and backlog.
proposed solution to be - Tools : JIRA, MS Suite
developed,
- Discuss and prioritized project
scope changes and gain
agreement,
- Creat beta test scripts for initial
testing,
- Sharing the developing module
with stakeholders and solicite
their fedback,
- Following deadlines and manage
stakeholders expectations,
- Resolving conflicts and mange
communications with the project
team
- Monitor the development of the
change request and verify their
implementation as per the
projec’s objective.
-

Testing - Discuss and prioritized project - Artifacts : Test cases, Project

scope changes and gain backlog, bug report, UAT
agreement, session invitation and UAT
- Creat beta test scripts for initial feedback report, MOM, sighoff
testing, from the client.
- Sharing the developing module - Tools : MS Suite, JIRA
with stakeholders and solicite
their fedback,
- Following deadlines and manage
stakeholders expectations,
- Resolving conflicts and mange
communications with the project
team,
- Developing test scripts and
 conducting comphrehensive
module and integration testing,
- Conducting UAT (use
accecptance testing) and creating
testing reports,
- Gain acceptance/approval of the
deliverables from the clients,
- Explain the change request to the
dev team.
Development and - Presenting the completed project - Artifacts : User training
Implementation to the client and gain their material.
acceptance, - Tools : MS Suite, JIRA
- Creat user-training manuals,any
functional materials and other
instructional guides,
- Conduct elaborate intigration
testing in production
environment,
- Create final product
documentations, document
project lessons learned,
- Exporing new opportunities in
future and managing change
request.