Vendor Screening v1.

Tell me about yourself

I have been a business analyst for 6+ years

I have been involved in working with business users and understanding business needs and business objectives

I put together high level documentation geared towards the business including vision document, scope document and
feasibility document.

I have authored the business requirement document and helped transition the requirements into detailed design
oriented functional and technical specification; worked extensively with USE cases, activity diagrams, sequence
diagram, wire frame and prototypes in this process.

I have created source to target data mapping specifications and helped with data profiling and data quality
requirements

I have maintained the requirement traceability matrix and mapped requirements to USE cases and USE cases to test
cases.

I created test cases and test scripts and had a visible involvement in the change management process.

I also had responsibility with UAT and created user manuals to user acceptance tracing.

What were your responsibilities in your last project?

In the last project I worked as a Business Analyst for ________. The goal of the project was (read portion of the
project summary in the resume)
My responsibilities included

Acting as a liaison between the users and the project management group. Understanding the requirements and
constraints from both sides.

Interviewing the users about their existing and potential processes, which they are looking for in the new system.

Developing use case specification document and diagrams based on the interviews.

Gathering the requirements and to develop the functional specification document so as to list the features of the
system users are looking for.

Developing use case documentation, and conducting JAD sessions

Vendor Screening v1.0

Authoring the BRD and FSD

Developing the test plans and scenarios and recording the observations of the users about the test and release.

What is are the Phases of SDLC

How did you document the requirements?

In gathering requirement I start with the understanding the

Scope of the project.

Vision of the project.

Understanding the AS IS process and TO BE process

2

Vendor Screening v1.0

Using these methods I gain the preliminary understanding of the problem area and work with project management to
develop a strategy to elicit requirements. I understand who are the key SMEs and Stake holders
I use several different methods to elicit requirements; based on the kind of Project, complexity, and users I am working
with and their availability. If there are several different users of the same designation and performing same jobs, I prefer
to conduct certain group sessions, group interviews and focus interviews. In case if I have to interview a manager or a
VP I would take a one to one interview or if he is unavailable I would send him a questionnaire online or shall do a
telephonic interview. At certain points of the projects, I also facilitate JAD/JAR sessions, and Brain-storming sessions
between the technical and non technical groups.

What is a JAD session?

Joint Application Development (JAD) can be thought of as large meeting involving multiple attendees from different
areas of the business and the IT. JAD sessions can be used to elicit requirements and also to analyze requirements.

Who do you invite in a JAD session?

1. Sponsor- The one who provides resources and support for the project
2. Business users- There are the users of the system being designed
3. System Analysts- they provide non-technical explanations to help JAD members understand and fully utilize the

technology available
4. IT & QA as well

Have you ever worked with the management?

Yes, I have worked with the top-level management at many different occasions. 1) During the requirement-gathering
phase, I had the opportunity to do 1 on 1 interview with the business managers. 2) Kept good communication with the
management during the project phase. 3) Whenever there were any issues, I worked with the project manager to resolve
the issues. 4) I also had a chance to interact with the managers during the requirement and project review meetings. 5) I
made project presentations to senior management during project review meetings.

Vendor Screening v1.0

Use Case Specification Document

Use cases serve as a format to express functional requirements in sequence. A use case is a sequence of actions
performed by a system that yields an observable result (a work output) of value to a particular actor. Use cases are
especially good at documenting functional software requirements.

Functional Specification Document

A Functional Specification document is a blueprint for like how we want a particular project or application to look and
work. It also details what the finished product will do and how a user will interact with it. The Functional Specification
is in essence a contract between the business customer and the IT project team, describing from a technical view what
the customer expects.
We will translate the business requirements into system functionality in technical terms. I, personally, worked with tech
lead to come up with the high level architecture. This system architecture can be broken down in functional modules
based on the requirements. These functional modules are component of the system, which can be clearly distinguished
from the other system. In between, initial recommendation of the technology will also help in designing the functional
specification document. I documented the functional module behavior in use case diagrams and use case scenarios.

Have you worked on any Rational tools?

I am quite well versed with Rational Rose for making use case diagrams, use case documents, realizations etc. I have
used Requisite pro for managing and documenting the requirements and managing requirements tracibility. I have
worked with Rational clear case for repository functionality and clear quest for defect management.

How far were you involved in the testing phase?

During the testing phase I was responsible for:

Developing Test Cases and Test Plans.

Recording the observations of the users and reporting them back to my manager.

Discussing any changes and updates with the user and if need arises handling the Change Request procedures and
tracking.

Managing defects

Vendor Screening v1.0

What is your main strength or what do you think that you have accomplished in your last project with which
you are most proud of?

I think my strength is my ability to be organized and detail oriented. There are always times when there are disconnects
or constant changes in the project and in case if you are not organizing your information and documents properly it
might lead to a disaster and failure. I am also quite detailed oriented which helps me to list the use cases and
requirements properly and comprehensively so that there is minimum element of doubt.

Vendor Voice mail

If Employer sends your resume to Vendor:

Hello _______
My name is _______. I am a business analyst. My employer from TEKERP sent you my resume for a BA position at the
____________ location. I took a very careful look at the job description and I think I am an excellent fit. I have all the
required skills and qualifications. I was hoping to connect with you and discuss more about this position. When you get
chance please cal me back at ________ I repeat it ______. Have a nice day.

If applying thru DICE

Hello
My name is _______. I am a business analyst. I came across your requirement on dice, Project ID- _______. I took very
careful look at the job description and I think I am an excellent fit. I have all the required skills and qualifications. I was
hoping to connect with you and discuss more about this position and send you my resume. When you get chance please cal
me back at ________ I repeat it ______. Have a nice day.