BA Interview Questions

GENERAL QUESTIONS

1. What do you think are your strengths as a Business Analyst?

I would say my strengths are:
§ The right mix of functional and technical knowledge RMF/T
§ Ability to communicate effectively between the development team and the end users ACE
§ Strong levels of persistence and quick learning capability SP QLC
§ Adaptability to the work environment as desired AWE

2. What do you think are your weaknesses as a Business Analyst?

I would say my weakness is that I am a perfectionist and I want my work to be done perfectly. This I consider as
my weakness because most of the times I am not satisfied with what I have done because it is important for one
to be contented with himself.

3. Please tell something about yourself and your career background.

I have completed my bachelors in electronics and electrical Engineering and then went on with my intership with
leading telecom giant ericsson india. I have about around 1+ years of work experience in IT industry. I started
my career with cognizant india and I have been working as an Analyst in business analysia field for one of the
oldest and well known fortune 500 company The Hartford, US as our client. I have very good knowledge on
telecom, insurance Domains. I am a hard working individual and always give 100percent to my work.
Leverage
Embrace changes
Problem solver
International traveller and people
Extra mile
Happy
As far as my previous project is concerned….

Last but not least I am a person who believes in simple living and high thinking.

Develop personally and professionally

Domain industry international traveller people****
Explore new culture, tradition, other factors

4. What do you think is the most important responsibility of a business analyst?

In my opinion the most important responsibility of a Business Analyst is to understand the business needs of
their clients and how the client delivers value to their customers.

It is usually an activity that requires high energy, excellent time management and organization skills, and
an ability to learn new business and domains quickly.

BA’s role ranges from defining/identifying the scope of the project in business requirements document (BRD),
gathering the details of the requirements and creating functional design documents (FDD), handling change
requests, etc…

5. What can you do for us that other prospective candidates cannot?

In addition to be hardworking and dedicated I enjoy learning new things and can quickly grasp what I read. I
have a very good mode of communication and I feel as a BA this is very important between I have seen that in
many companies there is a communication gap between the business owners and the development team and
this kind of creates a vacuum. I am confident that I will be able to communicate the requirements to the
development team very effectively resulting in the successful implementation of the project.

6. What makes you the best candidate for this position?

In addition to be hardworking and dedicated I enjoy learning new things and can quickly grasp what I read. I
have a very good mode of communication and I feel as a BA this is very important between I have seen that in
many companies there is a communication gap between the business owners and the development team and
this kind of creates a vacuum. I am confident that I will be able to communicate the requirements to the
development team very effectively resulting in the successful implementation of the project.

7. What are your goals?

My short terms goals are basically to do my job well upto my satisfaction and long term goals I would like to go
for professional Business Analysis certifications such as ISEB and also for PRINCE 2 certification which would
help me grow as a BA.

8. Why do you want to work here?

This is a very well known organization and its principles are in line with mine and I believe that it will give me a
good platform with the right amount of support and motivation.

9. Why do you want to leave your current position?

I was done with my previous project about 6 months ago and I decided to take a short break because I have 2
kids and wanted to spend some time with them before I start looking for another project.

10. What is the motivating factor which you expect from your job?
Believing that the work done by me is contributing in the organizational growth and success is my utmost
motivation to work. It is a feeling that my work has contributed in the company’s success and that I am a part
of the achievement however small my role might be it still gives me a lot of pleasure.

11. What parts of your job do you like the most?

What I really like about my job is interacting with the business users and communicating their ideas across to
the development and make sure this is done correctly so as to be able to deliver best value to the clients. The
ability to analyze and research the various aspects and arriving at the solution so as to benefit the organization
gives me immense satisfaction.

12. What parts of your job do you dislike the most?

There is currently no part of my job that I dislike and I am glad I have chosen this career path.

13. Describe your ideal job.

I am happy with what I am doing right now and this I would say is my ideal job. I would like to continue to excel
in my field and grow as BA.

14. What made you apply for this job and why do you want it?
I have the right mix of functional and technical knowledge and the skills that are required to perform this job. I
liked the job profile a lot and felt I will be able to this job very well leading to the successful implementation of
the project.

15. If you are introduced to a new domain, how do you become familiar with it and start working on it?
I believe that the best way to get familiar with a new domain is by reading a lot about the technical aspects of
the domain and the rest by interacting with the other team members, asking the PM to give a detailed
description of the project and to understand it fully before starting to work on it.

16. Give an example when you successfully acted as an interface between the technology team and the
 business areas?

17. Give an example of a situation when you managed conflict effectively.

There was a conflict between dev and QA teams on a defect that QA team has raised. I have worked closely with
them; I have referred them to design documentation, reproduced the defect and resolved the issue.

18. What is your favorite mode of communication? Why?

While capturing requirements, I will normally communicate requirements through email and get confirmation,
since it a more formal process. However, If I need to clarify requirements or while I was working on XXXX
project which was a fast paced initiative, I would have a conversation with business users over the phone or
face to face, but I make sure that I send out an email confirming the same and get an approval before adding
req. or changing the req. in FDD.

19. Do you have any questions for us?

What is the main thing that the organization expects from the employees?
What are the measures used to judge how successful I am in the role?
What can I expect from you in terms of development and support?

20. How do you handle criticism of your work?

I handle criticism very constructively. Nobody is perfect and everybody learns only by making mistakes. So I
don’t take any criticism in a negative way and I would infact like it if I am corrected so that I can do the task
properly next time.

21. How do you ensure that you have focused on all the necessary details of a task?
I firstly try to completely understand the task and see what is expected out of it. I write down each and every
small detail of it and start check marking those details which I have covered. Incase I have any doubt I consult
my peers and hence ensure I have covered every single detail of it.

22. How do you handle stress at work environment? (Since you are married and have kids. How do you
manage your stress?)

Everybody does get stressed out at times when they are overloaded with work and when they have shorter
deadlines especially when they have kids too. When I have short deadlines and I see that I am getting stressed
out, I take a break for few minutes and try to calm myself down by listening to some music or reading books and
then get back to my work.

BA RELATED QUESTIONS

1. Are you aware of the various software methodologies? Name a few

A software development methodology refers to the framework that is used to structure, plan, and control the
process of developing an information system. A wide variety of such frameworks have evolved over the years,
each with its own recognized strengths and weaknesses. One system development methodology is not
necessarily suitable for use by all projects. Each of the available methodologies is best suited to specific kinds
of projects, based on various technical, organizational, project and team considerations
The framework of a software development methodology consists of:
· A software development philosophy, with the approach or approaches of the software
development process
· Multiple tools, models and methods, to assist in the software development process.
These frameworks are often bound to some kind of organization, which further develops, supports the use, and
promotes the methodology. The methodology is often documented in some kind of formal documentation. The
various methodologies are:
● Waterfall: linear framework type.
● Prototyping: iterative framework type
● Incremental: combination of linear and iterative framework type
 ● Spiral: combination linear and iterative framework type
● Rapid Application Development (RAD): Iterative Framework Type
● Agile Methodology: Iterative
● SCRUM
● Extreme Programming (XP)
2. What are the typical deliverables in business analysis?

§ Business Requirements constitute specifications of what the business wants, the purposes of
initializing a specific project (Project Initialization Document), what the needed achievements will be,
and the quality measures. They are usually expressed in terms of broad outcomes the business
requires, rather than specific functions the system may perform.
§ Functional Requirements describe what the system, process, or product/service must do in order to
fulfill the business requirements. Note that the business requirements often can be broken up into sub-
business requirements and many functional requirements. These are often referred to as System
Requirements although some functionality could be manual and not system based, e.g., create notes or
work instructions.
§ User Requirements are a very important part of the deliverables; the needs of the stakeholders will
have to be correctly interpreted. This deliverable can also reflect how the product will be designed,
developed, and define how test cases must be formulated. The Business Analyst will record
requirements in a Requirements Management Tool; this can be a simple spreadsheet or a complex
application.
§ Non Functional Requirements are requirements that do not perform a specific function for the
business requirement but are needed to support the functionality. For example: performance,
scalability, quality of service (QoS), security and usability. These are often included within the System
Requirements, where applicable.

3. What are the various testing stages in a software project lifecycle?

§ Unit Testing- done by the developers
§ Integration Testing- done by the QA or BA team to see if the integration units are working fine
§ System Testing- done by the QA or BA team to see if the system as a whole is working fine
§ Regression Testing- done by the analysts to see if the current parts and the new development are
synchronized and if it is having any impact on other systems.
§ User Acceptance Testing-done by the end users to make sure if the requirements specified are in
line with the developed system.
§ Stress/ Load Testing- done by the technical team to see if the system can handle heavy load and
usage.

4. What are some of the challenges that you have faced as a Business Analyst?
Some of the major challenges were that
- I had to make sure there is clarity of requirements as they lay the foundation of the business and in case of
any error they can lead to severe repercussions.
- There are several software methodologies, technologies and documentation standards in the market and
they keep on evolving. So it is important to be well versed with the current technologies.

5. What are the documentations that you have completed in your experience? Explain in detail.
The various documents I have worked on are:
§ Business Case document
§ Project Charter
§ Business Requirement Document
§ Functional Design Document
§ Change Management Document and Managed Change Management Process
§ Implementation Plan
§ Roll Back Plan
§ Various UML Diagrams (use case, activity, deployment etc…)
§ Test Approach Document
 § Test Plan
§ Project Plan Draft
§ Technical design Document

6. What is UML? What are the tools which are generally used by BA’s for UML diagrams?

The Unified Modeling Language (UML) is an open method used to specify, visualize, modify, construct and
document the artifacts of an object-oriented software intensive system under development. UML offers a
standard way to write a system's blueprints, including conceptual components.
BA’s usually use the following UML tools,
a. MS- Visio
b. Rational Rose
c. Sparx System- Enterprise Architect

7. What UML diagrams have you used in the past?

a. Structural Diagrams
i. Package
ii. Component
iii. Deployment
iv. Class
v. Object
a. Behavioral Diagrams
i. Use Case
ii. Activity
iii. State
iv. Communication
v. Sequence
vi. Interaction Overview
vii. Timing

8. What are non functional requirements?

Non Functional Requirements are requirements that do not perform a specific function for the business
requirement but are needed to support the functionality. For example: performance, scalability, quality of service
(QoS), security and usability, error and exception handling, external interfaces and integration, disaster
recovery and business continuity plan, user and training requirements. These are often included within the
System Requirements, where applicable.

9. What is the importance of a flowchart?

A flowchart is a common type of chart, that represents an algorithm or process, showing the steps as boxes of
various kinds, and their order by connecting these with arrows. Flowcharts are used in analyzing, designing,
documenting or managing a process or program in various fields.

10. What is a use case model? Explain in brief

A Use Case Model describes the proposed functionality of a new system. A Use Case represents a discrete unit
of interaction between a user (human or machine) and the system. This interaction is a single unit of meaningful
work, such as Create Account or View Account Details.

11. Have you used Use Cases/use case diagrams before and did you use any software for it?
Yes I have used and developed use case diagrams before I used the software enterprise architect to do that.

12. What is the importance of an activity diagram?

An activity diagram is used to display the sequence of activities. Activity diagrams show the workflow from a
 start point to the finish point detailing the many decision paths that exist in the progression of events contained
in the activity. They may be used to detail situations where parallel processing may occur in the execution of
some activities. Activity diagrams are useful for business modeling where they are used for detailing the
processes involved in business activities.

13. How many types of diagrams are there and what do you know about them?
UML Diagrams are of 2 types Structural diagrams like ….. and Behavioral diagrams like ….

14. What is meant by an alternate flow in a use case?

It is a flow which will come into picture when there is a failure in the system and the expected results did not
come.

15. What do you mean by extends and includes in a use case?

Extends mean that the task that has to be performed in the process is optional whereas in an include
relationship it is mandatory to perform the task.

16. What are the different documents that relate to a use case?
For a use case / requirement, I would start out defining the high-level requirement in BRD, created the FDD with
all the details and Development team will create the They are the Functional Design Document and the
Technical Design Document for the same requirement before implementing the requirement in the system.

Test team will be responsible for writing the test cases, log defects and track defects for each requirement.

17. What is meant by logical data model?

A logical data model is a representation of an organization's data, organized in terms of a particular data
management technology. Logical data models are graphical representation of the business requirements. They
describe the things of importance to an organization and how they relate to one another, as well as business
definitions and examples. The logical data model can be validated and approved by a business representative,
and can be the basis of physical database design.

18. What do you mean by high level and low level in use case?

A broad level of a business process is a called a high level use case. And if we divide the big view into smaller
sub use cases then it is called a low level use case.

19. What do you know about SDD?

The System Design Document (SDD) records the results of the system design process and describes how the
system will satisfy the Requirements Specification. The SDD interprets the requirements into a description of
the structure, components, interfaces, and data necessary to support the build process.

20. What do you understand by URS and FS?

User requirements Specification and Functional Specification. We generally use the Traceability matrix to keep
track of that. A functional specification is the documentation that describes the requested behavior of an
engineering system. The documentation typically describes what is needed by the system user as well as
requested properties of inputs and outputs.

21. How do you prepare use cases?

By using MS Visio and Rational Rose

22. How do you participate in testing as a BA?

In reviewing the test cases to make sure all the requirements have been met.
23. Where did you use rational rose and requisite pro?

24. What do you understand by version control and configuration management?

Revision control (also known as version control, source control or (source) code management (SCM)) is
the management of changes to documents, programs, and other information stored as computer files. It is most
commonly used in software development, where a team of people may be changing the same files. Changes
are usually identified by a number or letter code, termed the "revision number", "revision level", or simply
"revision". For example, an initial set of files is "revision 1". When the first change is made, the resulting set is
"revision 2", and so on. Each revision is associated with a timestamp and the person making the change.
Revisions can be compared, restored, and with some types of files, merged.
Version control systems (VCS) are most commonly stand-alone applications, but revision control is also
embedded in various types of software like word processors (e.g. Microsoft Word, [Link] Writer,
KOffice, Pages, Google Docs), spreadsheets (e.g. [Link] Calc, Google Spreadsheets, Microsoft
Excel), and in various content management systems. Integrated revision control is a key feature of wiki software
packages such as MediaWiki, DokuWiki, TWiki, etc. In wikis, revision control allows for the ability to revert a
page to a previous revision, which is critical for allowing editors to track each other's edits, correct mistakes, and
defend public wikis against vandalism and spam.
Configuration management (CM) is a field of management that focuses on establishing and maintaining
consistency of a system's or product's performance and its functional and physical attributes with its
requirements, design, and operational information throughout its life. For information assurance, CM can be
defined as the management of security features and assurances through control of changes made to hardware,
software, firmware, documentation, test, test fixtures, and test documentation throughout the life cycle of an
information system

25. What is meant by good documentation management system?

A good documentation management system is very important and some of its features are:
§ Continue the work started by a colleague if she’s gone on vacation, and respond to her customers if
needed,
§ Get hold of examples of all document types with just a few clicks, so that you can follow company
standards in such areas as order confirmation, price requests, meeting minutes, customer deliverables, contract
examples, and models for faxes and letters,
§ Retrieve procedures and other associated documents if you don’t know how to do a certain task – such
as things you should do when hiring a new employee, organizing a conference, or how to structure meeting
minutes,
§ Very easily reuse work done by a colleague to meet similar needs and build on all the individual work
done in your own company,
§ Find all the orders for a customer or from a supplier in just a few seconds to answer questions or two
continue a discussion when the initial contact point in your company is not available,
§ Build on your working methods and enable your colleagues to benefit from each improvement in a
document type or a procedure.

26. What is OOAD?

Object-oriented analysis and design (OOAD) is a software engineering approach that models a system as a
group of interacting objects. Each object represents some entity of interest in the system being modeled, and is
characterized by its class, its state (data elements), and its behavior. Various models can be created to show
the static structure, dynamic behavior, and run-time deployment of these collaborating objects. There are a
number of different notations for representing these models, such as the Unified Modeling Language (UML).
Object-oriented analysis (OOA) applies object-modeling techniques to analyze the functional requirements for a
system. Object-oriented design (OOD) elaborates the analysis models to produce implementation
specifications. OOA focuses on what the system does, OOD on how the system does it.

27. What do you mean by Data Mapping?

Data mapping is the process of creating data element mappings between two distinct data models.
28. Explain what are Interface / Integration mapping?
It is the mapping of individual fields of one system to another for communication.

29. What is black box testing?

Black box testing takes an external perspective of the test object to derive test cases. These tests can be
functional or non-functional, though usually functional. The test designer selects valid and invalid inputs and
determines the correct output. There is no knowledge of the test object's internal structure.

30. What is white box testing?

White box testing (a.k.a. clear box testing, glass box testing, transparent box testing, and translucent box
testing or structural testing) uses an internal perspective of the system to design test cases based on internal
structure. It requires programming skills to identify all paths through the software. The tester chooses test case
inputs to exercise paths through the code and determines the appropriate outputs.

31. What is a bug?

A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer
program that prevents it from behaving as intended (e.g., producing an incorrect or unexpected result). Most
bugs arise from mistakes and errors made by people in either a program's source code or its design, and a few
are caused by compilers producing incorrect code. A program that contains a large number of bugs, and/or
bugs that seriously interfere with its functionality, is said to be buggy. Reports detailing bugs in a program are
commonly known as bug reports, fault reports, problem reports, trouble reports, change requests, and so forth.

32. How do you measure the quality of a product?

A product which has minimum errors based on the quality standards of the company determines the quality of a
product.

33. What is RAD?

Rapid application development (RAD) refers to a type of software development life cycle which uses minimal
planning in favor of rapid prototyping. The "planning" of software written in RAD is interleaved with writing the
software itself. The lack of extensive pre-planning generally allowed software to be written much faster, and
makes it more flexible to change in requirement.

34. What is ETL?

Extract, transform, and load (ETL) in database usage and especially in data warehousing involves:
· Extracting data from outside sources
· Transforming it to fit operational needs (which can include quality levels)
· Loading it into the end target (database or data warehouse)

35. What is win runner?

Used for regression testing.

36. What is load runner?

Used for performance testing.

37. What is a business process?

A business process or business method is a collection of related, structured activities or tasks that produce a
specific service or product (serve a particular goal) for a particular customer or customers. It often can be
visualized with a flowchart as a sequence of activities.
There are three types of business processes:
1. Management processes, the processes that govern the operation of a system. Typical
management processes include "Corporate Governance" and "Strategic Management".
2. Operational processes, processes that constitute the core business and create the primary
value stream. Typical operational processes are Purchasing, Manufacturing, Marketing, and Sales.
3. Supporting processes, which support the core processes. Examples include Accounting,
 Recruitment, and Technical support.
38. How do you identify risks in any business process?
We have to examine all the sources of risks from the perspective of stakeholders by brainstorming,
flowcharting, system analysis, design, review and proper judgment.

39. How do you manage risk for a project?

Risk management involves
1. Identification of risk in a selected domain of interest
2. Planning the remainder of the process.
3. Mapping out the following:
o the social scope of risk management
o the identity and objectives of stakeholders
o the basis upon which risks will be evaluated, constraints.
4. Defining a framework for the activity and an agenda for identification.
5. Developing an analysis of risks involved in the process.
6. Mitigation of risks using available technological, human and organizational resources.

40. What is user interfacing, its uses and your experiences?

User interfacing is the method by which the users interact with the system by giving a certain input and the
system giving the right output. There are 2 types of user interfaces:
· Graphical user interfaces (GUI) accept input via devices such as computer keyboard
and mouse and provide articulated graphical output on the computer monitor. There are at least two different
principles widely used in GUI design: Object-oriented user interfaces (OOUIs) and application oriented
interface.
· Web-based user interfaces or web user interfaces (WUI) accept input and provide
output by generating web pages which are transmitted via the Internet and viewed by the user using a web
browser program. Newer implementations utilize Java, AJAX, Adobe Flex, Microsoft .NET, or similar
technologies to provide real-time control in a separate program, eliminating the need to refresh a traditional
HTML based web browser. Administrative web interfaces for web-servers, servers and networked computers
are often called Control panels.

41. How do you categorize requirements?

Functional
Non-Functional

42. How do you analyze the requirements?

As far as my previous experience with understanding requirements, performing analysis and getting myself
prepared for JAD session, I would refer to existing documentation for the application, if I am working on
enhancement of the application. Or refer to project documentation available and any related documents specific to
requirement, if I am working on replacing the application, I would work on existing application to understand the
current functionality or meet with users or experienced personnel in the team to understand the how the task is
done manually today, if there is no system in place today.

43. How would you use Requirements Modeling and when?

Requirements models are used when gathering requirements, and during systems analysis. Whether you
consider eliciting requirements to be a separate activity, or a part of systems analysis, the importance of correct
requirements must be a high priority for you. Building accurate models means that you can guarantee the
correctness of your requirements.

44. What are the roles of an SA, DBA and PM?

 45. What is your role after implementation?
I have taken responsibility to create the implementation plan, roll back plan during the implementation phase and
helped the team to coordinate deployment activities.
After the implementation, I was working closely with business users on post implementation issues, if any (explain
any issues business have found and you followed up with dev team to resolve and quick re-deployment). Also,
created the training documents Quick Start Guide and User Guides for the team and conducted training session to
the users on the application.

46. Explain BRD and FDD?

BRD: A business requirement document is one which is developed at the planning phase of a project by the BA
from the input that he gets from the Business case document. It is a detailed document about the different high
level and low level requirements that the customer wants to be incorporated in his product.
FDD: A Functional Design Specification (FDS) is a document used by companies in a pre-development phase
to translate all notes, concepts, and scope into a complete requirements document. The document can include
anything from flowcharts, screenshots, and wire frames. At a minimum, an FDS will contain an organized list of
requirements that can be used for development, testing, and client sign-off.

47. Have you used customized version of Rational Unified Process?

48. How is RUP used to analyze a process?

49. Let us say you have created a class diagram for a given subject area. How do you make sure that you have
captured all the methods/properties for a class and that you have captured all the classes?
I did not create a class diagram from scratch. I was part of design meeting, where I have captured the details
and created a class diagram. Once I have the diagram drafted, I have conducted review meeting with Solution
Architect and Lead Developer responsible for that module and finalized the diagram.

50. What is a traceability matrix and how do you use it when using the Unified process?
A traceability matrix is a document, usually in the form of a table, that correlates any two baselined documents
that require a many to many relationship to determine the completeness of the relationship. It is often used with
high-level requirements (sometimes known as marketing requirements) and detailed requirements of the
software product to the matching parts of high-level design, detailed design, test plan, and test cases.

51. What is the difference between Agile and Unified Process methodology?

52. What is your approach to resolving conflict during JAD sessions?

53. Let us say you in a JAD session and someone is constantly trying to divert the topic from what is on
agenda for you to some peripheral item. How do you bring the session back on track?
If the topic or concerns are related to another requirement, I would inform the team that I will note this item as a
Parking Lot item and we will talk about it in much detail while having the session about the other requirement.

If the issue or concern is about current requirement, I would inform that we will take this as an action item and talk
about it at the end of the session if time permits or I will follow up with the person who has a concern later on and
notify the team about the decision, if anything is impacted in terms of requirements.
E.g. QA person in the meeting is trying to understand the requirement and over all process, then you can say we
will talk about it after the meeting.

54. How would you handle a scenario when requirements change midway in the project?
I used to follow the Change Management Process

55. What is your approach to solving problems?

56. What types of questions do you ask when gathering data for requirements?
There are mainly 2 types of questions that you ask:
Open ended which allow the interviewee to answer as they please for eg what are the most frequent problems
that you experience with your computer output? And secondly closed questions in which the response is limited
to a finite number of choices.

57. What is your experience in project management?

58. Do you have any experience working with Enterprise configuration projects?
59. Who do you think are the main stakeholders for the project?
§ Shareholders
§ Employees
§ Customers
§ Suppliers
§ Creditors
§ Society
§ The government
§ Competitor
60. Describe the most challenging problem you have ever solved. What was your approach in doing so?
61. Describe a situation when you used some innovative technique for communicating ideas across? This was
probably the best question and it really got me thinking.

62. Do you have any experience with Business Process Reengineering? Explain.
It is an approach aiming at improvements by means of elevating efficiency and effectiveness of the business
process that exist within and across organizations. The key to BPR is for organizations to look at their business
processes from a "clean slate" perspective and determine how they can best construct these processes to
improve how they conduct business.

63. What approaches do you need when 2 companies merge?

64. How did you assign task and/or hold testers accountable for their work?
65. What type of push back have your received from the business users in relation to QA?
66. What have you done to decompose functional requirements to bring to the testing teams? (This should be
answered in a way to explain the process that was involved also).
67. For what reasons does a BA correspond with a Vendor? How can he deal with a vendor effectively?
68. What are the reporting tools used by BA? How do you decide that which reports you have to extract or on
what basis you extract the report? What are the fields or the data when you extract in a report?
The two main reporting tools used by BA’s are SQL Query or Statement which is used by developers or
program managers and OLAP (Online Analytical Processing).
ETL and Hyperian

69. What are different defect tracking tools that you have used?
Quality center 9.0 (advanced version of test director), test director, rational clear quest, bugzilla

70. How do you handle infrastructure requirements?

71. You are working on a project where you have some requirements regarding creating some service
accounts on production server and create a network folder. Who do you contact in the list of people and how do
you organize and capture requirements?
72. I see that you worked on agile methodology. Can you explain the activities that you performed during each
development sprint and couple of best things you noticed in agile methodology?
73. What are the steps you take to get familiarize with the organization processes, system to work on when you
join the team?
74. If you are introduced to a new domain, how do you become familiar with it and start working on it?
75. How do you follow up with development team regarding severity 1 issues and get hot fix for QA to continue
QA process?
 76. How do you handle the situation of the team missing the timelines and where you see an issue delivering
the project within the proposed timeline?
During UAT users have identified some missing requirements and wanted to implement them before the
implementation because they are critical to their needs, how do you handle the changes? Or
How do you handle functional changes during the design or later stages of the project?
Or
Do you know about impact analysis?
Or
Did you perform impact analysis? Can you explain your thoughts on it?

77. What is a shrink wrap contract?

Shrink wrap contracts are license agreements or other terms and conditions of a (putatively) contractual
nature which can only be read and accepted by the consumer after opening the product. The term describes the
shrinkwrap plastic wrapping used to coat software boxes, though these contracts are not limited to the software
industry. Web-wrap, click-wrap and browse-wrap are related terms which refer to license agreements in
software which is downloaded or used over the internet.

78. What is cowboy coding?

Cowboy coding is the absence of a defined method: team members do whatever they feel is right.

79. What are the various steps in a JAD Session?

○ Identify project objectives and limitations

○ Identify critical success factors
○ Define project deliverables
○ Define the schedule of workshop activities
○ Select the participants
○ Prepare the workshop material
○ Organize workshop activities and exercises
○ Prepare, inform, educate the workshop participants
○ Coordinate workshop logistics

84. What is the difference between structural diagrams and behavioral diagrams?
Structure diagrams emphasize what things must be in the system being modeled and Behavior diagrams
emphasize what must happen in the system being modeled.
80. What are package diagrams?
Packages are UML constructs that enable you to organize model elements into groups, making your UML
diagrams simpler and easier to understand. Packages are depicted as file folders and can be used on any of
the UML diagrams, although they are most common on use-case diagrams and class diagrams because these
models have a tendency to grow.
81. What is the difference between component and deployment diagrams?
A component diagram in the Unified Modeling Language, depicts how components are wired together to form
larger components and or software systems. A deployment diagram in the Unified Modeling Language serves
to model the physical deployment of artifacts on deployment targets.

Manager Questions (QA Lead, PM, Lead BA)

1. Was there any situation where you disagreed with your manager thoughts? If yes, how do you propose new
solution or your ideas?

2. If there any issues between teams how do you improve your team communication and resolve team issues?

Additional Questions:
1. Define the following:

Business Case Document: The business case should, at a minimum, describe a proposal’s purpose, identify
expected benefits, and explain how the proposed system supports one of the organization’s business
strategies. The business case should also identify alternative solutions and detail as many informational,
functional, and network requirements as possible.
Organizational Chart: An organizational chart is a diagram that shows the structure of an organization and the
relationships and relative ranks of its parts and positions/jobs. An organizational chart of a company usually
shows the managers and sub-workers who make up an organization. It also shows the relationships between
the organization's staff members which can be one of the following:
· Line - direct relationship between superior and subordinate.
· Lateral - relationship between different departments on the same hierarchical
level.
· Staff - relationship between a managerial assistant and other areas. The assistant
will be able to offer advice to a line manager. However, they have no authority over the line manager actions.
· Functional - relationships between specialist positions and other areas. The
specialist will normally have authority to insist that a line manager implements any of their instructions.
In many large companies the organization chart can be large and incredibly complicated and is therefore
sometimes dissected into smaller charts for each individual department within the organization.
There are three different types of organization charts:
· Hierarchical
· Matrix
· Flat
Project Charter: It is a statement of the scope, objectives and participants in a project. It provides a
preliminary delineation of roles and responsibilities, outlines the project objectives, identifies the main
stakeholders, and defines the authority of the project manager. It serves as a reference of authority for the
future of the project. The purpose of the project charter is to document:
· Reasons for undertaking the project
· Objectives and constraints of the project
· Directions concerning the solution
· Identities of the main stakeholders
The three main uses of the project charter:
· To authorize the project - using a comparable format, projects can be ranked and
authorized by Return on Investment.
· Serves as the primary sales document for the project - ranking stakeholders have
a 1-2 page summary to distribute, present, and keep handy for fending off other project or operations runs at
project resources.
· As a focus point throughout the project - for example: project as people walk in to
team meetings and use in change control meetings to ensure tight scope management.

Test Strategy: A test strategy is an outline that describes the testing portion of the software development
cycle. It is created to inform project managers, testers, and developers about some key issues of the testing
process. This includes the testing objective, methods of testing new functions, total time and resources required
for the project, and the testing environment.
In the test strategy is described how the product risks of the stakeholders are mitigated in the test levels, which
test types are performed in the test levels, and which entry and exit criteria apply.
The test strategy is created based on development design documents. The system design document is the
main one used and occasionally, the conceptual design document can be referred to. The design documents
describe the functionalities of the software to be enabled in the upcoming release. For every set of development
design, a corresponding test strategy should be created to test the new feature sets.

JAD Sessions: Joint Application Development (JAD) is a process used in the Systems Development Life
Cycle (SDLC) to collect business requirements while developing new information systems for a company. The
JAD process also includes approaches for enhancing user participation, expediting development, and improving
the quality of specifications.

Test Plan: A test plan documents the strategy that will be used to verify and ensure that a product or system
meets its design specifications and other requirements. A test plan is usually prepared by or with significant
input from Test Engineers.

Requirements Traceability Matrix: A traceability matrix is a document, usually in the form of a table, that
correlates any two baselined documents that require a many to many relationship to determine the
completeness of the relationship. It is often used with high-level requirements (sometimes known as marketing
requirements) and detailed requirements of the software product to the matching parts of high-level design,
detailed design, test plan, and test cases.

Functional Design Document: A Functional Design Specification (FDS) is a document used by companies in
a pre-development phase to translate all notes, concepts, and scope into a complete requirements document.
The document can include anything from flowcharts, screenshots, and wire frames. At a minimum, an FDS will
contain an organized list of requirements that can be used for development, testing, and client sign-off.

UAT: User Acceptance testing generally involves running a suite of tests on the completed system. Each
individual test, known as a case, exercises a particular operating condition of the user's environment or feature
of the system, and will result in a pass or fail Boolean outcome. There is generally no degree of success or
failure. The test environment is usually designed to be identical, or as close as possible, to the anticipated
user's environment, including extremes of such. These test cases must each be accompanied by test case input
data or a formal description of the operational activities (or both) to be performed—intended to thoroughly
exercise the specific case—and a formal description of the expected results.