BA Knowledge (Chapter 10: Techniques) Flashcards

Chapter 10: Techniques

1
Q

Bring stakeholders together in order to collaborate on achieving a predefined goal.

A

Workshops

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

represents a small, concise statement of functionality or quality needed to deliver value to a specific stakeholder.

A

User Stories

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

_______ and _______ describe how a person or system interacts with the solution being modelled to achieve a goal.

A

Use Cases and Scenarios

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

used to elicit business analysis information—including information about customers, products, work practices, and attitudes—from a group of people in a structured way and in a relatively short period of time.

A

Survey or Questionnaire

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

used to describe and analyze the different possible states of an entity within a system, how that entity changes from one state to another, and what can happen to the entity when it is in each state.

A

State Modelling

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

involves identifying the stakeholders that may be affected by a proposed initiative or that share a common business need.

A

Stakeholder List, Map, or Personas

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

shows how processes or objects interact during a scenario. The classes required to execute the scenario and the messages they pass to one another

A

Sequence Diagrams

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

define the nature of one or more limits or boundaries and place elements inside or outside those boundaries.

A

Scope Modelling

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

used to identify and evaluate the underlying causes of a problem, a systematic examination of a problem or situation that focuses on the problem’s origin as the proper point of correction rather than dealing only with its effects.

A

Root Cause Analysis

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

used to ensure coverage of activities by denoting responsibility, to identify roles, to discover missing roles, and to communicate results of a planned change

A

Roles and Permissions Matrix

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

used to evaluate the content of a work product.

A

Reviews

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

used to elicit and validate stakeholder needs through an iterative process that creates a model or design of requirements, can be non-working models, working representations, or digital depictions of a solution or a proposed product

A

Prototyping

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

describes the sequential flow of work across defined tasks and activities through an enterprise or part of an enterprise

A

Process Modelling

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

assesses a process for its efficiency and effectiveness, as well as its ability to identify opportunities for change.

A

Process Analysis

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

defines how an organization or organizational unit is structured.

A

Organization Modelling

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

is used to elicit information by viewing and understanding activities and their context.

A

Observation

17
Q

examines the requirements for a solution that define how well the functional requirements must perform. It specifies criteria that can be used to judge the operation of a system rather than specific behaviours.

A

Non-Functional Requirements Analysis

18
Q

_________ and __________ measure the performance of solutions, solution components, and other matters of interest to stakeholders.

A

Metrics and Key Performance Indicators (KPIs)

19
Q

also known as a retrospective helps identify either changes to business analysis processes and deliverables or successes that can be incorporated into future work.

A

Lessons Learned

20
Q

used to capture and assign responsibility for issues and stakeholder concerns that pose an impact to the solution

A

Item Tracking

21
Q

s a systematic approach designed to elicit business analysis information from a person or group of people by asking relevant questions, and documenting the responses.

A

Interviews

22
Q

is used to identify where, what, why, when, how, and for whom information is exchanged between solution components or across solution boundaries.

A

Interface Analysis

23
Q

defines key terms relevant to a business domain.

24
Q

helps manage complexity and reduce uncertainty by breaking down processes, systems, functional areas, or deliverables into their simpler constituent parts and allowing each part to be analyzed independently.

A

Functional Decomposition

25
is a means to elicit ideas and opinions about a specific product, service, or opportunity in an interactive group environment.
Focus Groups
26
used to support decision making by predicting attributes such as: * cost and effort to pursue a course of action, * expected solution benefits, * project cost, * business performance
Estimation
27
used to elicit business analysis information, including contextual understanding and requirements, by examining available materials that describe either the business environment or existing organizational assets.
Document Analysis
28
usually takes the form of a diagram that is supported by textual descriptions, frequently used in elicitation and requirements analysis and design, as well as to support implementation and continuous improvement.
Data Modelling
29
an analytic process that examines large amounts of data from different perspectives and summarizes the data in such a way that useful patterns and relationships are discovered.
Data Mining
30
portray the transformation of data. They are useful for depicting a transaction-based system and illustrating the boundaries of a physical, logical, or manual system.
Data Flow Diagrams
31
used to standardize a definition of a data element and enable a common interpretation of data elements.
Data Dictionary
32
starts with a glossary, which typically focuses on the core noun concepts of a domain
Concept Modelling
33
refer to several structured techniques inspired by game play and are designed to facilitate collaboration.
Collaborative Games
34
used to identify, express, validate, refine, and organize the rules that shape day-to-day business behaviour and guide operational business decision making.
Business Rules Analysis
35
a technique intended to produce a broad or diverse set of options.
Brainstorming
36
used to record, track, and prioritize remaining work items.
Backlog Management
37
used to define the requirements, outcomes, or conditions that must be met in order for a solution to be considered acceptable to key stakeholders.
Acceptance and Evaluation Criteria