BA Skill Assessment C

Chandra Sekhar

Q1. What are BA Thumb rules ?

Ans. The following are the thumb rules :

1. Never criticize any stakeholder ever. Appreciate them even for their smallest favors.

2. Never take tension, pass it on. The client never intends to offend anyone, since the BA is the only
point of contact to the client, so the client shells out all their concerns on this contact.

3. Solve the client solutions through IT solutions.

4. Be focused on your work just like the lotus in the mud, free from opinions, viewpoints
disputations and arguments.

5. Do not haste while gathering the requirements due to the stress levied. The basic idea of
gathering the requirements is to realize the organizational goals. So it is very important to gather the
correct and consistent requirements.

Q2. Write about a relationships in OOA ?

Ans. Relationships exists between classes or between objects, but not between class and an object.

There are 4 types of relationships.

▪ Association- has a relationship

Unary- One Way

Binary- Two Way

Multiplicity- 1 to Many, Many to 1 or Many to Many

Reflexive- Single class with multiple role & one role is directed to itself.

▪ Generalization The Generalization relationship indicates that one of the two related classes
(the subclass) is considered to be a specialized form of the other and superclass is considered as
'Generalization' of subclass. In practice, this means that any instance of the subtype is also an
instance of the superclass.

▪ Aggregation Aggregation represents the set of Main Classes that are dependent on Sub-Classes,
the Main class cannot exist without Sub-Class but the Sub-Class can exists without the Main Class.

▪ Composition Composition represents the set of Main Classes that are dependent on Sub-Classes,
the Main class cannot exists without Sub-Class and the Sub-Class cannot exists without the Main
Class. The Sub-Class can represent only one composite relation with the Main class.
 Q3. What is RTM? Give a sample RTM and how it is managed through SDLC?

Requirement Traceability Matrix (RTM) is a document that maps and traces user requirement with
test cases. It captures all requirements proposed by the client and requirement traceability in a
single document, delivered at the conclusion of the Software development life cycle. The main
purpose of Requirement Traceability Matrix is to validate that all requirements are checked via test
cases such that no functionality is unchecked during Software testing.

A simple way is to trace the requirement with its corresponding test scenarios and test cases. This
merely is termed as ‘Requirement Traceability Matrix.’

The traceability matrix is typically a worksheet that contains the requirements with its all possible
test scenarios and cases and their current state, i.e. if they have been passed or failed. This would
help the testing team to understand the level of testing activities done for the specific product.
Which Parameters to include in Requirement Traceability Matrix

 Requirement ID
 Requirement Type and Description
 Test Cases with Status
REQUIREMENTS TRACEABILITY MATRIX  
Project Name:      
Reviewer/Approve
   
r
Technical Test
Traceability # Requirement ID
Requiremnt ID Case ID
a B1 T94 1
b B1 T95 2
c B3 T96 3
d B4 T97 4
       

Q4.What are different Documents that can be used in a project ,you are aware of ?

There are a number of documents, which can be created by a business analyst. Here is a
comprehensive list of such documents.

 Business Case
 Business analysis plan
 Business requirements document (BRD)
 Stakeholder Management Plan
 System Requirements specification document (SRS)
 Functional/process document
 Gap Analysis Document
 Solution Approach Document
 Requirements traceability table (RTT)
 Change request logs
 Impact analysis document
  System test Plan
 System test cases
 UAT progress report

Q5.Why Projects fail?

Ans. 6 reasons why projects fail

(i)Lack of resource planning

(ii)Unclear Goals and Objectives

(iii)Lack of project visibility

(iv)Communication gaps

(v)Scope creep

(vi)Unrealistic expectations

Q6. How a BA handles Business Requirements, User Requirements and Functional Requirements

Ans. Business requirements describe why the organization is undertaking the project. They state
some benefits that the developing organization or its customers expect to receive from the product.
Business requirements may be delineated in several documents such as a project charter, business
case, or in a project vision and scope statements. Business requirements bring the project owner,
stakeholders and the project team on the same song sheet.  But you can’t build software from such
high-level information. In the En-focus Requirement Suite, we consider the following business
requirements.

 Problem Statement
 Project Vision
 Project Constraints (Budget, Schedule, and Resources)
 Project Objectives
 Project Scope Statements
 Business Process Analysis
 Stakeholder Analysis

The results from the business process analysis and stakeholder analysis activities are also considered
business requirements. The purpose of the business process analysis is to determine how the
business process will work.  It is often necessary to resolve deficiencies in the business process
before trying to automate it.  Not dealing with the business process design first is like trying to pave
a cow path; it might get you there, but it certainly won’t be the straightest most direct path. The
 stakeholder analysis is needed to determine who will be impacted by the system and how to engage
the impacted people to get their user requirements.

User requirements, often referred to as user needs, describe what the user does with the system,
such as what activities that users must be able to perform. User requirements are generally
documented in a User Requirements Document (URD) using narrative text. User requirements are
generally signed off by the user and used as the primary input for creating system requirements.

An important and difficult step of designing a software product is determining what the user actually
wants it to do. This is because the user is often not able to communicate the entirety of their needs
and wants, and the information they provide may also be incomplete, inaccurate and self-conflicting.
The responsibility of completely understanding what the customer wants falls on the business
analyst. This is why user requirements are generally considered separately from system
requirements. The business analyst carefully analyzes user requirements and carefully constructs
and documents a set of high quality system requirements ensuring that that the requirements meet
certain quality characteristics.

Functional requirements are the building blocks developers use to build the system. These are the
traditional “shall” statements that describe what the system “shall do.” System requirements are
classified as either functional or supplemental requirements.  A functional requirement specifies
something that a user needs to perform their work.  For example, a system may be required to enter
and print cost estimates; this is a functional requirement.  Supplemental or non-functional
requirements specify all the remaining requirements not covered by the functional requirements. I
prefer to use the term supplemental requirements instead of non-functional requirements; who
wants to be termed nonfunctional? Supplemental requirements are sometimes called quality of
service requirements. The plan for implementing functional requirements is detailed in the system
design. The plan for implementing supplemental requirements is detailed in the system
architecture.  The list below shows various types of supplemental requirements.

 Accessibility
 Accuracy
 Audit, control, and reporting
 Availability
 Backup and restore
Q7. Draw a sequence diagram for payment done by Customer through Credit Card
 Credit card User Library Account Details Trasaction details receipt details

Credit Card details Card Verification Process transaction

Verification Failed Generate receipt

apalogy Transaction Failed

Update account

Q 8. Explain all elements of an Activity Diagram and What is the difference between Fork, Join and
Branch , Merge in an Activity Diagram? What is difference between Guard Condition and Event?

Ans. An activity diagram visually presents a series of actions or flow of control in a system similar to a
flowchart or a data flow diagram. Activity diagrams are often used in business process modeling.
They can also describe the steps in a use case diagram. Activities modeled can be sequential and
concurrent. In both cases an activity diagram will have a beginning (an initial state) and an end (a
final state).

Initial State or Start Point A small filled circle followed by an arrow represents the initial action state
or the start point for any activity diagram. For activity diagram using swimlanes, make sure the start
point is placed in the top left corner of the first column.

Activity or Action State

An action state represents the non-interruptible action of objects. You can draw an action state in
SmartDraw using a rectangle with rounded corners.
Action Flow
Action flows, also called edges and paths, illustrate the transitions from one action state to another.
They are usually drawn with an arrowed line.

Object Flow
Object flow refers to the creation and modification of objects by activities. An object flow arrow
from an action to an object means that the action creates or influences the object. An object flow
arrow from an object to an action indicates that the action state uses the object.

Decisions and Branching

A diamond represents a decision with alternate paths. When an activity requires a decision prior to
moving on to the next activity, add a diamond between the two activities. The outgoing alternates
should be labeled with a condition or guard expression. You can also label one of the paths "else."

Guards
In UML, guards are a statement written next to a decision diamond that must be true before moving
next to the next activity. These are not essential, but are useful when a specific answer, such as "Yes,
three labels are printed," is needed before moving forward.

Synchronization
A fork node is used to split a single incoming flow into multiple concurrent flows. It is represented as
a straight, slightly thicker line in an activity diagram.
A join node joins multiple concurrent flows back into a single outgoing flow.
A fork and join mode used together are often referred to as synchronization.

Merge Event
A merge event brings together multiple flows that are not concurrent.

Final State or End Point

An arrow pointing to a filled circle nested inside another circle represents the final action state.

Q 9. What are the various international Bodies of Business Analysis? And what certifications on BA
is available? Name them along with Qualifications and Exam fees.

Ans. A business analyst blends data skills and business acumen to benefit the IT and analytics-driven
organizations. To become more competitive, business analyst certification help to increase your
earning potential and gives an edge over other competitors. 
 Below are four significant institutes which offer business analyst certifications you can earn.

International Institute of Business Analysis (IIBA

IIBA is a nonprofit organization which offers competency-based certification to the business analysis
profession. The firm follows defined knowledge standard and perspective, which should be known to
a business analyst.

Some of the certifications offered by IIBA are:

 Academic Business Analysis Certificate (ABAC): It is an entry-level certification which can be

obtained from an institute or college associated with IIBA. It helps prepare students for various
competency-based IIBA certification.
 IIBA Entry Certificate in business analysis (ECBA): It is the first-level certification and is
designed for entry-level or less experienced business analyst. You must complete 21 hours of
professional training credits, within the past four years to apply for the exam.
 IIBA Certification of competency in business analysis (CCBA): It is level two of IIBA
certification which showcases applicant’s ability to apply business analysis knowledge to practical
scenarios. Applicants need to have 3,750 hours of business analyst experience along with two
professional references and 21 hours of professional development training.
 IIBA Certified business analysis professional(CBAP): It shows the authority of business
analysis and the capacity to lead others. Candidates must have 7,500 hours of business analysis
experience along with the completion of 35 professional development hours in the past four years
with professional references.
 IIBA Agile Analysis Certification(AAC): This certification is designed to address the BA skillset
and to certify professionals working in an agile environment. It is offered through remote online
proctoring. There isn’t any eligibility criterion, but IIBA suggests for two-five years of elegant related
experience.
 International Qualification Board for Business Analysts (IQBBA) IQBBA is a globally
recognized certification body with an accredited exam and coaching centres all across the world. It
offers two certifications.

 IQBBA Certified foundation level business analyst(CFLBA): It is an entry-level certification

that will qualify to earn higher levels of certification. It is developed for the individuals in the field of
process improvement, modelling business and analyzing business processes.
 Certified Advanced Level Business Analyst (CALBA): Once you pass the above entry-level
exam, you can continue to CALBA, which focuses on business analysis process management skills.
 Project Management Institute (PMI)

It is a global nonprofit professional organization which offers best certification courses for project
management individuals. IT offers one business analysis certifications:

 PMI-Professional in business analysis( PBA) Certification: The PMI-PBA certification is

intended for business experts who work with programs or projects, or project and program
managers work with analytics. If you have earned a bachelor degree, you’ll need three years of
experience, or 4,500 hours, in business analysis within eight years to acquire this certification.
Without a bachelor degree, you’ll need five years or 7,500 hours experience along with 60
professional development units.

International Requirements Engineering Board (IREB)

The IREB is the holder for international certification for requirements engineering. It offers three
certifications:

 IREB Certified professional for requirements engineering foundation level( CPRE - FL): It is
the entry-level certification which exhibits a candidate’s knowledge of business analysis related to
requirements engineering. Candidates must pass written exam at a testing site.
 IREB Certified professional for requirements engineering advanced level( CPRE - AL): It is
an advanced level certification for candidates having advanced knowledge of requirements
engineering. Candidates must pass the CPRE-FL exam along with written exam at the testing site.
 IREB Certified professional for requirements engineering expert level( CPRE - EL): It is the
highest level of certification which showcases the mastery of requirement engineering techniques.
Candidates must have experience leading a team and must pass CPRE-AL exam along with a written
exam at the testing site.

Q.10 Railway Reservation System

 Railway Reservation System

Search ticket
availability
* *

«uses»
Book ticket
Fill Form
*
*
«uses» *

«uses» **
*
**
** Pay Amount * *
**
* *
«uses»
Website
Customer

Cancel Ticket
* *
*

«uses» «uses»

*
Refund Amount
Print Form
*
*
*
*

Clerk
Activity Diagram for Ticket Booking and Cancellation

Search Train

Fill Cancellation form

Check Availability

Submit form

[No]
[Yes Changes
Quit
]
[Yes] Modify Form
[No changes]

Book Ticket
Clerk enters details into system

Fill Form

Verify the details

[Not Ok
]
Submit Details
[Ok]

Calculate and Refund Amount

Make Payment

Print Ticket Print Cancellation Receipt

Q 11. What are the roles and responsibilities of Business Analyst in given phases?

ANS :

stages activities Artifacts and resources

Pre project Enterprise Analysis – SWOT Business Case
Analysis, GAP Analysis, SOW (Statement of Work)
Market Research, Feasibility PO (Purchase Order)
Study, Root Cause Sr. BA, Business Architects
Analysis, Decision Analysis, Pre sales Consultants
Strategy Analysis,
Enterprise Architectural
Frameworks, Project Scope
and Business case writing,
Risk analysis

Planning and estimations 1. Understand Assumptions PM

and assessment and Constraints along with Senior BA
Business Rules and Business
Goals
2. Plan Packages for Big
Project kickoff Projects
3. Understands the project
plan from PM
4. BA conducts stakeholders
Analysis
5. Plan BA approach strategy
(Req. gathering
techniques, communication,
Req. mgmt, Documents
to follow, Tools to use,
Change Request Handling
methodology )for this
Project

Requirements gathering 1. Stakeholders identify and BRD ( business requirements

document documents )
2. Client gives BRD or BA
prepares BRD by
interacting with Client –
Brainstorming ,
Document Analysis, Reverse
engineering,
Interviews, workshops,
Focus Groups,
Observation,
Questionnaires .
3. Prototyping can be used
by BA to make the
Client to give more specific
 requirements
4. Sort the gathered
Requirements (avoiding
duplicate Reqs , grouping
into similar
functionality or into
modules)
5. Prioritize requirements –
MoSCoW
6. Validate Requirements -
FURPS

Requirements analysis 1. Draws UML Diagrams FRS functional requirements

( Use-case and Activity specification
Diagrams)
2. Prepares Functional SSD supplementary support
Requirements from Business documents
Requirements
3. All Architects comes up SRS software requirements
with Technical Requirements specifications
(SSD)
4. SRS will have Functional RTM requirements
Requirements and Technical traceability matrix
Requirements
5. Takes Sign-off on SRS from
Client. SRS is the first legal
binding Doc between the
Business and the technical
Team
6. BA prepared RTM from
SRS before Design phase
starts.
(BA is the owner of RTM).
7. BA traces how
requirements are dealt in
each phase of
development life cycle from
Design till UAT

Design 1. From Use-case Diagram , Solution document

Test Manager or BA will
prepare Design document -- ADD&
Test Cases HDD
2. Communicates with Client
on the design and Solution
documents (updates Status
to Client and make them
understand how the solution
would look like to prepare
them to drive UAT)
3. BA will initiate the
 preparation of End user
manuals
4. updates RTM
5. From Use case Diagram
Solution-Architect
recommends
Architecture of the IT
solution
6. DB Architect uses
Persistence Classes (Entity
Classes) and
comes up with ER Diagrams
or DB Schema.
7. GUI Designer will look into
Transient Classes ( Boundary
Classes) and designs all
possible Screens for the IT
Solution

Coding 1.BA organizes JAD Sessions LDD-CDD

2. BA clarifies queries of
Technical Team during Application
Coding
3. Developers refer Diagrams
and Transient
(Controller Classes) of BA
and code their unit
4. Update End user manuals
5. Update RTM
6. Conducts regular Status
meetings with technical
team and the Client and
tuning Client for
participation
in UAT

Testing 1.BA- Prepares Test Cases Specific test concerning

from Use Cases or assists
Test Manager to do so Documents
2. BA performs high level
testing Application with less errors
3. BA prepares Client for UAT
4. Test Data is requested by
BA from Client
5. Updates End User
Manuals
6. Updates RTM
7. Take sign-off from Client
on Client Project
Acceptance form
Deployment and 1.Forwards RTM to Client or
implementation the PM which should be
attached to the Project
Closure Document
2. Coordinates to complete
and share End User
Manuals
3. Plans and Organizes
Training Sessions for End
Users
4. Prepares Lessons learned
from this project (to take
precautions for coming
projects)