Chapter 1: Business Analysis 101 Flashcards

1
Q

Area or boundaries being analyzed

A

Domain

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Set of changes to a current State. A solution enables a domain to: meet a business need, solve a business problem, take advantage of an opportunity

A

Solution

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

The function of this role is to solve problems and work as a liaison among all technical and non-technical stakeholders.

A

Business Analyst

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

artifacts, practices or information from any participating entity that is used to perform or manage the project

A

OPA-Organizational Process Assets

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Higher-level statements of the goals, objectives or needs of a domain/enterprise.

A

Business Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Business Requirements are developed in this knowledge area that consists of defining business needs, assess capability gaps, determine solution approach, define solution scope, define business case

A

Enterprise Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Statements of the needs of a particular stakeholder or class/group of stakeholders

A

Stakeholder Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Solution characteristics to satisfy business and stakeholder requirements

A

Solution Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Behavior and information managed by the solution

A

Functional Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Conditions that do not involve behavior or functionality describing environmental conditions or qualities

A

Non-Functional Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Knowledge are that stakeholder and solution requirements are developed in that consists of prioritize requirements, organize requirements, specify and model requirements, define assumptions and constraints, verify requirements and validate requirements

A

Requirements Analysis

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Capabilities of the solution to transition from the current to future state and are not needed after transition is completed. Differentiated from other requirements because they are always temporary.

A

Transition Requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Knowledge area that transition requirements are developed in.

A

Solutions Assessment and Validation

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Responsible and accountable for the execution of BA activities (BSA, SA, Process Analyst, Consultant and Product Owner)

A

Business Analyst

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Makes use of products or services produced (segmented by market, geography and industry, among others)

A

Customer

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Individual with in-depth knowledge of a topic relevant to the business need or solution scope (broken out by organizational unit and job role)

A

Domain SME

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Directly interacts with the solution (broken out by organizational unit and job role)

A

End User

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Responsible for designing and implementing solution (project librarian, change manager, config manager, solution architect, dev, DBA, trainer

A

Implementation SME

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Supports operation of project activities (help desk, network tech, release mgr)

A

Operational Support

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Ensures project’s objectives are met while balancing project assumptions and constraints related to the scope, budget, schedule, resources, quality and risk, among others (scrum master, team leader)

A

Project Manger

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Provides products or services (providers, consultants)

A

Supplier

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Responsible for determining how to verify that the solution meets the requirements defined by the BA within the verify requirements task (QA analyst)

A

Tester

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Responsible for the definition and enforcement of standards ( govt, regulatory bodies and auditors)

A

Regulator

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Responsible for initiating the effort to define a business need and develop a solution (mgrs, execs, pm, process owners)

A

Sponsor

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Q

Identifying business problems and assessing proposed solutions so that a full understanding of all needs can be provided to stakeholders

A

analytical thinking and problem solving

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
26
Q

developing working relationships with stakeholders, incorporating qualities such as trust and ethical behavior

A

behavioral characteristics

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
27
Q

understanding general business principles, and how analysis and available solutions will interact within the business environment

A

business knowledge

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
28
Q

enhancing the communication methods and practices between analysts and stakeholders so that there is a clear understanding of ht needs and objectives between parties

A

communication skills

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
29
Q

facilitating interaction between stakeholders and divisions, and fostering management involvement so that all goals and objectives are met for current and future projects

A

interaction skills

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
30
Q

the tools used during the development and distribution of requirements to stakeholders

A

software applications

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
31
Q

minimal requirements met for a solution to be considered implementable

A

acceptance criteria

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
32
Q

requirements used to evaluate multiple solutions

A

evaluation criteria

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
33
Q

requirements that must be met for a solution to be considered acceptable by key stakeholders

A

acceptance and evaluation criteria definition

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
34
Q

the recording of a current state so that a comparison against future states is possible

A

baselining

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
35
Q

a comparison of an organization’s practices against its own or a competitor’s superior performance in areas of strategy, ops and processes, and how much strengths can best be utilized to improve future enterprise ops.

A

benchmarking

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
36
Q

producing numerous and diverse options and/or solutions to a particular issue by a group

A

brainstorming

37
Q

rules that govern decisions which constrain or enable ops within an organization such as SOX, ITIL, CMMI

A

Business Rules analysis

38
Q

a document ensuring important items are included int eh final deliverables, such as test cases and test scripts

A

checklist

39
Q

a table or spreadsheet used to manage tracing, such as requirements traceability matrix

A

coverage matrix

40
Q

key terms used by an org as well as the definition of data elements, their meanings and values

A

data dictionary/ glossary

41
Q

graphical representation of how information is processed by a system

A

data flow diagrams

42
Q

description of any relevant concepts and their relationships to one another

A

data modeling

43
Q

examination of consequences/outcomes of different proposed solutions so that an optimal decisions can still be ascertained during times of difficulty or uncertainty.

A

decision analysis

44
Q

identification of requirements by studying pertinent documentation on existing and proposed solutions

A

document analysis

45
Q

approximating the cost and effort required to implement a solution

A

estimation

46
Q

a preliminary analysis of solution alternatives to gauge whether they can meet the business need

A

feasibility analysis

47
Q

utilization of a moderator in an interactive environment to elicit ideas about products and services from pre qualified members.

A

focus groups

48
Q

assess potential problems identified during the readiness assessment, and determine which problems are the most important to deal with so that a mitigation strategy can be developed

A

force field analysis

49
Q

the separation of issues into smaller components and subcomponents so that work can be assigned to different entities.

A

functional decomposition

50
Q

identification of interfaces between solutions and/or solution components and how they will interact

A

interface analysis

51
Q

eliciting and documenting information from an individual or group in a formal or informal setting

A

interviews

52
Q

compiling and documenting successes, difficulties or areas for improvement, along with resultant recommendations for future projects or project phases

A

lessons learned process

53
Q

measuring the performance of solutions and their components, and other pertinent areas of interest to stakeholders

A

metrics and key performance indicators

54
Q

analysis of requirements that fit into the following: must, should, could, won’t

A

MoSCoW Analysis

55
Q

process of describing the required qualities of a system, such as compatibility, security and performance

A

non-functional requirements analysis

56
Q

process of structuring the whys, whats and hows of project requirements into a hierarchy of objects containing encapsulated data and procedures.

A

object-oriented design (OO)

57
Q

assessment of a process or environment performed via a passible/invisible approach or an active/visible approach

A

observation

58
Q

aligning an organization’s existing roles, responsibilities and reporting structures with the organization’s goals.

A

organization modeling

59
Q

document identifying the business need and key stakeholders, and entails the positive impact that achieving the objectives will have on stakeholders

A

problem/vision statement

60
Q

detailing the approach to tracking, managing and resolving defects, issues and risks so that they can be resolved in a timely fashion

A

problem tracking

61
Q

understanding the work and interaction between groups or processes within an organization which is performed (can be displayed via graphic representation)

A

process modeling

62
Q

process of identifying, describing and validating the user interface requirements and their integration with other requirements, such as data and business rules

A

prototyping

63
Q

formal requirements document, product roadmap, system requirements specs

A

requirements documentation

64
Q

use of a RFI, RFQ or RFP if an outside vendor is to provide a solution

A

requirements for vendor selection

65
Q

identifying the scope and definition, priority and criteria of requirements by utilizing a facilitator, group and scribe

A

requirements workshops

66
Q

isolation and management areas of risk that can impact a process, proposed solution, an objective or the organization itself, and evaluating responses

A

risk analysis

67
Q

determining of the underlying issues/source of a problem

A

root cause analysis

68
Q

describing of how a person, process or system interacts with a solution to accomplish an objective

A

scenarios and use cases

69
Q

one specific way to accomplish a goal

A

scenario

70
Q

all outcomes of an attempt to accomplish a goal that the solution will support

A

use-cases

71
Q

graphical representation to describe the scope of analysis/solution

A

scope modeling

72
Q

graphical representation to show how info is passed between objects during the execution of a task

A

sequence diagrams

73
Q

formalizing of an agreement by stakeholders that the requirements docs are accurate and complete

A

signoff

74
Q

graphical representation showing the behavior of how a concept transitions in response to a change in conditions

A

state diagrams

75
Q

a review and discussion used to verify and validate requirements

A

structured walkthrough

76
Q

survey to elicit info regarding business aspects, personnel and practices

A

survey/questionnaire

77
Q

identification of strengths, weaknesses, opportunities, and threats of the pertinent processes

A

SWOT analysis

78
Q

priorities requirements by allocation of a fixed resources

A

timeboxing/budgeting

79
Q

description of functionality that user requires from a solution to meet goals

A

user stories

80
Q

analyzing the differences between planned and actual performance, and identify ing any corrective and preventative actions

A

variance analysis

81
Q

evaluation of a vendor’s ability to meet requirements, commitments or objectives in regard to a product or service

A

vendor assessment

82
Q

voting to allocate a fixed amount of resources to be distributed among requirements

A

voting

83
Q

The BA planning and Monitoring Knowledge Area identifies and describes the steps involved in what on the performance of business analysis effort to ensure expected outcomes are produced

A

planning, monitoring and reporting

84
Q

gathering information from stakeholders to determine and understand their needs

A

elicitation

85
Q

defines how requirements are managed and how these requirements are communicated to stakeholders of varying backgrounds and business groups

A

requirements management and communication

86
Q

identifying business need, problem or opportunity, determining the most effective solution and justifying the investment for the new business requirement. Often initiates new projects and continues as changes occur.

A

Enterprise Analysis

87
Q

examining the capability of stated requirements to provide a potential soution to meet stakeholder needs and develop models of the current state of an organization to identify opportunities for improvement

A

requirements analysis

88
Q

activities performed to assess and validate all components of the proposed solution to ensure successful implementation

A

solution assessment and validation