CODE B

Submitted by Ashutosh Ghule

Answer 1-
Business Analyst is the mediator between client and technical team. He is the face to technical team and
understand the client requirements. All the communication happen through BA. He understand,
communicate and analyse the requirements. That requirements pass to the technical team for IT solution.
Do’s and Don’t for BA
1. Never say no to client
2. There is no word called “By Default”.
3. Never assume anything while meeting with client.
4. GO with fresh mind to understand the requirements.
5. Never imaging anything in terms of “GUI”
6. Every client problem is unique.
7. Never interrupt client while talking. Let him complete and then ask doubt regarding requirements.
8. Never try to give solution to client problem with your experience and assumptions.
9. Always maintain record for what you learn from past project.

Answer 2-
Business Process model has
1. Specific goal
2. Input and output
3. Specific resources
4. Number of activities performed
5. Create value for customer.
A business process has some activities that is need to be performed in order to generate specific goal and add
some value to the customer. A process has ordering of activities with time and budget, input and output and
resources.

Answer 3-
Challenges of BA
1. Lack of training
2. Coordination between client and technical team
3. Coordination between developers and testers
4. Arrange the meeting
5. People management
6. Requirement gathering and documentation as per client
7. Sign off on document from client
8. Drive client for UAT
9. Make sure status reporting is effective
10. Change management

1
Answer 4-

Documentation tools MS office

Thinkfree
Adobe buzzword
Zoho writer

UML drawing tool MS visio

StarUML
ArgoUML
Rational Rose
Smart Draw

Prototyping Pidoco
Pencil

Screen Capturing Snagit

Software development process model RUP

Brainstorming Evernote
Free mind

Meeting minutes Meeting sense

Database tools MS access

SQL server

Testing Win Runner

Load Runner
Test Runner
Enterprise analysis TOGAF
ProVision

2
Answer 5
Actor generalization-
In actor generalization, Actor A performing certain activities and there is special actor/ VIP actor who
performed all activities of Actor A but has special features which can be added.
For example- Student receive book from library also read the book. But VIP actor- Toppers can read the
book, receive the book and can purchase the book also. This is called actor generalization.

Use case generalization-

Relationship can exist between two use cases where one use case(child) inherits the behaviour and properties
of another use case(parent).
For example- Student pay for registration either by phone and by internet.

3
Answer 6
Include used in use case diagram when use case and supportive use cases given or included in case study.
For example- Book online railway reservation-
In this date and time, class, birth are include because it is given in case study.

Exclude- if is not required.

For example- Online flight reservation system
Window seat/ middle seat, food called as a Exclude.
Example is drawn below----------------

4
Answer 7-
Follow the company standard for SRS document.
Subsections-
1) Introduction
Purpose
Scope
Definition
Reference
2) System requirements
System overview
Assumptions
3) Functional requirements
4) External requirements
Hardware, software and communication interface
5) Non-functional requirements
Performance, scalability, usability, packaging and security and safety requirements
6) Acceptance criteria
7) Post implementation
8) Annexure

Answer 8

5
Answer 9
1) What is the existing process you follow?
2) How customer login into system?
3) How e-ticket is generated?
4) Who is going to assess this system?
5) Where customer makes a complaint?
6) How you going to handle those compliant?
7) What are the feature and functionalities do you require?
8) Where this system implements? (environment)
9) How you monitor the system?
10) How do you see yourself after period of time?
11) How any user currently you are handling?
12) How many users will you handle?
13) How you protect this system?
14) Who is going to protect this?
15) What is the alternative solution if failure occurs?
16) What type of user interface using?
17) Where customer see their booking confirmation?
18) How you access the customer data?

Answer 10-
Role of BA in change request
BA will study and understand the feature and characteristics of requirements change. As it is dynamic in
nature, requirements need to managed throughout the project. People change their mind, prefarences and
taste, so as business changes and market also change accordingly.
BA will prepared change management . Whenever client comes up with change, BA analyse those changes.
He do feasibility study to accept those changes. Then BA do impact analysis to measure changes and then
effort estimation to implement those changes.
For this BA need to follow certain steps-
When client comes with change BA prepares change request document.
BA analyse the change request and understand whether it is really needed or discovered from previous need
communications.
Project manager approved the change request if analyst move forward.
Understand whether it is complex one or simple one.
If it is complex one then BA will help the stakeholder to understand the impact of change request on project
which will lead to increase in time.
Successful change request help BA to articulate a vision to stakeholders.

6
Answer11

7
8
Answer 12
Stages Activities Artifacts

 Enterprise analysis- Business case

Pre- project SWOT, gap analysis, Statement of work
feasibility study, Purchase order
strategy analysis and Sr.BA, Business Architects
decision analysis, risk
analysis
 Understand the
Requirement Planning assumptions and
constraints along with
business rules
 Plan package for big
project
 Understand the project Sr BA, PM
form PM
 Stakeholder analysis
 Plan BA approach
strategy
 Stakeholder identify BRD
Requirement Gathering and document
 Client gives BRD or
BA prepared BRD
 BA uses prototyping
for more specific
requirements
 Requirements gathered
 Prioritize the BA, PM
requirements -
MoSCoW
 Validate requirements
-FURPS
 Draw UML diagrams FRS
Requirements Analysis  Prepares functional SSD
from business SRS
requirements RTM
 Prepare SSD
 SRS will have
functional and BA, PM, Solution architect
technical requirements DB architect

 Take sign off from

client
 BA prepares RTM
from SRS before
design stage
 From use case HDD
Design diagram, BA prepare
test cases.

9
  Communicate with the BA, PM
clients on design. DB ,NW
 BA initiates end user GUI
manual
 Update RTM
 DB architect uses
persistence (entity
class) come up with
ER diagram

 BA organizes JAD
Coding session
 Clarifies the queries
with technical team
 Update end user BA, PM, Development team
manual
 Update RTM
 Regular status meeting
with technical team
 BA prepares test cases
Testing  BA perform high level
testing
 Testing requested by
BA from client
 Update end user
manual
 Update RTM
 Take sign off from
client
 Forward RTM to client
Deployment  Share end user manual
 Lessons learn from
project

10