Free CBAF-001 Practice Test

The Business Activity Model (BAM) is constructed to represent the activities necessary to achieve a system's purpose, as defined in a root definition. The logical starting point is to identify the 'Doing' activities. These are the primary, operational activities that directly transform inputs into outputs and fulfill the core purpose of the business system. Once these fundamental value-creating activities are established, the other categories of activities—which plan for, provide resources for (enable), and measure the performance of the 'Doing' activities—can be logically derived. This ensures the model is built around the central function of the system.

A. Enabling: Enabling activities provide the resources (e.g., staff, technology) required by other activities. They cannot be identified until the core 'Doing' activities they must support are known.
B. Planning: Planning activities set the direction, scope, and targets for the 'Doing' activities. The 'Doing' activities must be defined first before they can be planned.
D. Monitoring: Monitoring activities assess the performance of the 'Doing' activities against the plan. Therefore, both the 'Doing' and 'Planning' activities must be identified before monitoring can be defined. ---

1. Checkland

P. (1999). Systems Thinking

Systems Practice: Includes a 30-Year Retrospective. John Wiley & Sons. In Chapter 6

the construction of a conceptual model (or BAM) is described as flowing directly from the root definition's main verb

which corresponds to the primary 'Doing' activities. The other activities are logically dependent on these.

2. Wilson

B. (2001). Soft Systems Methodology: Conceptual Model Building and Its Contribution. John Wiley & Sons. Section 4.3

"Model Building

" explains that the primary-task activities (the 'Doing' activities) are derived directly from the transformation process (the 'T') in the CATWOE analysis and root definition. The regulatory (planning

monitoring

control) and enabling activities are then built around this core set.

3. The Open University. (2006). T3061 Managing complexity: a systems approach - Block 2

Section 5.3 Building the conceptual model. Milton Keynes: The Open University. This courseware explicitly states that the modeling process begins by listing the minimum necessary activities implied by the verb in the root definition. These verbs represent the core 'Doing' activities of the system.

The Internal Rate of Return (IRR) is a fundamental metric in financial analysis and capital budgeting. By definition, the IRR is the specific discount rate at which the Net Present Value (NPV) of a series of cash flows (both inflows and outflows) equals zero. When a business case states that the IRR has been calculated, it means this break-even discount rate has been identified. Therefore, the statement that the Net Present Value is zero is inherently true at the point of the IRR. This rate is then compared to a company's required rate of return or cost of capital to decide whether to accept or reject the project.

A. The Net Present Value is not known. Incorrect. The NPV is explicitly known to be zero at the IRR, as this is the core definition of the IRR calculation.
B. The DCF Rate is not known. Incorrect. The IRR is the specific Discounted Cash Flow (DCF) rate that makes the project's NPV equal to zero.
D. The DCF Rate is Zero. Incorrect. The IRR is the calculated DCF rate, which is a percentage representing the project's return; it is rarely, if ever, zero.

1. Brealey

R. A.

Myers

S. C.

& Allen

F. (2020). Principles of Corporate Finance (13th ed.). McGraw-Hill Education. In Chapter 5

Section 5-2

"The Internal Rate of Return Rule

" the text states

"The internal rate of return (IRR) is defined as the rate of discount that makes NPV = 0."

2. Massachusetts Institute of Technology. (2009). 15.401 Finance Theory I

Fall 2008. MIT OpenCourseWare. In "Lecture 3: The NPV Rule and its Competitors

" the lecture notes define IRR as "the discount rate that sets NPV to zero."

3. Berk

J.

& DeMarzo

P. (2017). Corporate Finance (4th ed.). Pearson. In Chapter 7

Section 7.3

"The Internal Rate of Return Rule

" the IRR is defined as "the interest rate that sets the net present value of the cash flows equal to zero."

A rich picture is a central technique within Soft Systems Methodology (SSM) used to explore and understand a complex or "messy" business problem. It is intentionally unstructured and free-form, resembling a cartoon or mind map. Its purpose is to capture not just processes and structures, but also the crucial human elements of a situation, such as relationships, conflicts, culture, concerns, and different viewpoints. This holistic, pictorial representation helps analysts and stakeholders gain a shared understanding of the problem context without being constrained by formal modeling notations, which might prematurely structure or oversimplify the situation.

A. An organization chart is a formal, hierarchical diagram showing reporting structures, which is far more structured than a rich picture.
B. A swim-lane diagram is a type of flowchart used for structured process modeling, mapping activities to specific roles or departments.
D. A UML class diagram is a highly formal, standardized notation from the Unified Modeling Language used in software engineering to model system structure.

1. Checkland, P., & Poulter, J. (2006). Learning for Action: A Short Definitive Account of Soft Systems Methodology and its use for Practitioners, Teachers and Students. Wiley. In Chapter 2, "The Basics of the Methodology," a rich picture is described as a way of "representing the situation... that is entirely pictorial and informal" to capture the complexities of a human situation.

2. The Open University. (2019). TU811: Thinking strategically: systems tools for managing change, Block 2, Section 5.2: The rich picture. Milton Keynes: The Open University. This courseware states, "A rich picture is a drawing of a situation that illustrates the main elements and relationships that must be considered... It is an attempt to encapsulate the real situation through a no-holds-barred, cartoon-style representation."

3. Avison, D., & Fitzgerald, G. (2003). Information Systems Development: Methodologies, Techniques and Tools (4th ed.). McGraw-Hill. In Chapter 19, Soft Systems Methodology, rich pictures are defined as a tool to "build up a picture of the problem situation... as rich as possible... showing the elements of structure, process, and the climate of the situation." (p. 425).

A mind map is a visual diagram used to organize information around a central subject. It is an effective tool for documenting the outcomes of a workshop because it can capture and structure ideas, discussion points, decisions, and their relationships in a non-linear, graphical manner. This visual representation helps stakeholders understand the connections between different elements discussed and provides a clear, consolidated summary of the workshop's results, making it an excellent documentation technique for collaborative sessions.

B. Brainwriting: This is a technique for silent and parallel idea generation during a workshop, not a method for documenting the final, consolidated outcomes.
C. Round-robin: This is a facilitation technique used during a workshop to elicit contributions from all participants sequentially, not a tool for documenting the overall results.
D. Stepwise refinement: This is a top-down design strategy used in software engineering to break down a system into detailed components; it is not a workshop documentation method.

1. de Oliveira

O. H. B.

de Oliveira

T. C.

& do Prado Leite

J. C. S. (2009). Using Mind Maps to Elicit and Model Crosscutting Requirements. In Proceedings of the 2009 ACM Symposium on Applied Computing (pp. 599–600). Association for Computing Machinery. This paper explicitly discusses the use of mind maps as a tool to "support the elicitation and modeling of requirements

" demonstrating its role in capturing and structuring information from elicitation activities like workshops. (DOI: https://doi.org/10.1145/1529282.1529411)

2. Pohl

K. (2010). Requirements Engineering: Fundamentals

Principles

and Techniques. Springer Publishing. In Chapter 6

Section 6.3.2 "Creativity Techniques

" mind mapping is described as a technique for structuring thoughts and ideas

which is central to documenting workshop outputs. In contrast

techniques like brainwriting are categorized purely for idea generation.

3. University of Calgary

Schulich School of Engineering. (n.d.). SENG 471: Software Requirements Engineering

Lecture 6 - Elicitation. Courseware. Slide 21

"Brainstorming

" presents mind mapping as a method to organize ideas generated during brainstorming sessions

which are a core component of many workshops. It distinguishes this from idea generation techniques themselves.

Gap analysis is a technique used to compare the current state ("as-is") of a business process or system with the desired future state ("to-be"). This comparison identifies the differences, or "gaps," that need to be addressed. Within the standard Business Analysis Process Model, this activity is central to the 'Analyse needs' stage. It is during this stage that the business analyst moves from understanding the current situation to defining the core business needs that must be fulfilled to achieve the desired future state. The gap itself represents the business need.

A. Define requirements: This stage occurs after a solution option has been chosen; it details the specifics of the solution, whereas gap analysis identifies the problem.
C. Evaluate the options: This stage involves assessing different ways to bridge the gap. Therefore, the gap must have already been identified and analyzed.
D. Investigate situation: This stage focuses on understanding the current "as-is" state, which is only one of the two components required for a gap analysis.

1. Paul, D., & Cadle, J. (2020). Business Analysis (4th ed.). BCS, The Chartered Institute for IT. In Chapter 4, "The Business Analysis Process Model," section 4.4.3, "Analyse needs," it is stated: "The purpose of this stage is to get to the root of the business problem or opportunity and to identify exactly what needs to be addressed... This involves analysing the gap between the current situation and the desired future."

2. The Open University. (n.d.). T215: Communication and information technologies. Courseware Block 3, Section 5.2, "The business analysis process model." The materials describe the 'Analyse needs' stage as the point where the gap between the current and desired situation is analyzed to define the business needs.

3. Turner, P., & Coupé, T. (2011). A Business Analysis Process Model. In Proceedings of the European Conference on Information Management and Evaluation (pp. 440-446). Academic Conferences International Limited. This paper discusses the standard process model, positioning the analysis of needs (including gap analysis) after the initial investigation and before the evaluation of potential solutions.

Protocol analysis is an investigation technique where an analyst observes a user performing a task and asks them to verbalize their thought process. The goal is to understand the user's cognitive process, including their reasoning, decisions, and any difficulties they encounter. By asking questions about how a customer order form is completed while the user is doing it or walking through it, the analyst is directly applying protocol analysis to understand the detailed steps and logic involved in the process.

A. Activity sampling. This technique measures how users divide their time among different activities through random observations, not the detailed cognitive process of a single task.
C. Document analysis. This involves the review of existing documents (like the form itself) to understand its structure and content, not the dynamic process of how a user completes it.
D. Structured observation. This technique involves observing a user against a pre-defined checklist of actions or criteria. It focuses on what is done, rather than the user's thought process or reasoning, which is elicited by asking questions.

1. Paul

D.

Yeates

D.

& Cadle

J. (2014). Business Analysis (3rd ed.). BCS

The Chartered Institute for IT. In Chapter 5

Section 5.5.3

"Observation

" protocol analysis is described as a type of observation where "the person being observed is asked to talk through what they are doing and why they are doing it... This helps the business analyst to understand the business rules and procedures." This directly matches the scenario.

2. Preece

J.

Rogers

Y.

& Sharp

H. (2015). Interaction Design: Beyond Human-Computer Interaction (4th ed.). Wiley. Chapter 13

"Introducing Evaluation

" details the "Think-Aloud" technique (a synonym for protocol analysis) as a primary method for understanding a user's thoughts and motivations while they interact with a system or document.

3. Nielsen

J. (1994). Usability Engineering. Morgan Kaufmann. Chapter 6

"Usability Testing

" pp. 195-198

establishes the "thinking aloud" protocol as a fundamental method for gaining qualitative insights into how users actually work through a task

which is precisely what the analyst in the scenario aims to achieve.

Shadowing is a direct observation technique used in business analysis and requirements elicitation. It involves an analyst closely following and observing a user in their natural work environment for a significant period, such as one or two days. The goal is to gain a deep, contextual understanding of the user's tasks, workflows, interactions, and the informal processes or challenges they encounter. This immersive method is particularly valuable for understanding complex roles and tacit knowledge that users might not articulate in interviews or workshops.

A. Scenario analysis. This technique involves creating narrative descriptions of possible user interactions with a system to explore requirements, not observing a user's current job.
B. Protocol analysis. This is a "think-aloud" method where a user verbalizes their thought process while performing a task, focusing on cognitive aspects, not a long-form observation.
D. Activity sampling. This is a statistical technique using random, intermittent observations to determine how time is distributed across various tasks, not a continuous, in-depth study.

1. Preece

J.

Rogers

Y.

& Sharp

H. (2015). Interaction Design: Beyond Human-Computer Interaction (4th ed.). Wiley. In Chapter 7

"Data Gathering

" the authors describe direct observation in the field

stating

"Observation can be direct or indirect... Direct observation involves spending time with individuals and observing their activity as it happens... shadowing a user is a form of direct observation" (p. 235).

2. Kuniavsky

M. (2003). Observing the User Experience: A Practitioner's Guide to User Research. Morgan Kaufmann. This text

often used in university HCI and design courses

details shadowing as a key observational method. Chapter 11

"Observations

" explains that shadowing involves "following a subject through their day" to understand the context of their actions (p. 251).

3. Lazar

J.

Feng

J. H.

& Hochheiser

H. (2017). Research Methods in Human-Computer Interaction (2nd ed.). Morgan Kaufmann. In Chapter 5

"Observation

" the authors differentiate various observational techniques. They describe shadowing as a form of ethnographic observation where the researcher follows a participant to understand their activities in context

contrasting it with techniques like activity sampling

which is quantitative and intermittent (pp. 120-122).

The typical sequence of reactions to organizational change follows a predictable pattern often illustrated by the "Change Curve" model, which is adapted from the Kübler-Ross grief model. The process begins with an initial negative reaction, such as fear or shock (b). As individuals grapple with the change, a period of disruption, resistance, and uncertainty often leads to a temporary decline in morale and job performance (c). Following this low point, individuals begin to explore and test the new methods, leading to a gradual, often reluctant, acceptance (d). Finally, as the benefits of the change become clear and new skills are mastered, individuals integrate the change into their work, leading to commitment and enthusiasm (a).

A. b, d, c and a: This is incorrect because the dip in performance (c) typically precedes acceptance (d). Acceptance marks the beginning of the recovery from the performance low.
B. a, b, c and d: This is incorrect as enthusiasm (a) is characteristic of the final stage of successful change adoption, not the initial reaction.
D. a, b, d and c: This is incorrect for starting with enthusiasm (a) and for placing acceptance (d) before the performance dip (c), which misrepresents the typical emotional and productivity cycle.

1. Elrod, P. D., & Tippett, D. D. (2002). The ‘death valley’ of change. Journal of Organizational Change Management, 15(3), 273-291. In Section "The Change Process Model" (pp. 275-278), the authors describe the initial shock and fear, followed by a dip in performance (the "death valley"), which must be traversed before acceptance and institutionalization of the change can occur. This supports the sequence of fear -> reduced performance -> acceptance. DOI: https://doi.org/10.1108/09534810210429277

2. University of Exeter. (n.d.). The Change Curve. Professional Development Unit. Retrieved from university courseware on change management. The model presented outlines the stages of reaction to change, starting with 'Shock & Denial' (related to fear), moving down to 'Anger' and 'Depression' (where performance drops), then moving up through 'Acceptance' and 'Exploration' (reluctant acceptance), and finally reaching 'Commitment' (enthusiasm). This directly supports the b, c, d, a sequence.

3. Carnall, C. A. (2007). Managing Change in Organizations (5th ed.). Prentice Hall. In Chapter 3, "The Human Side of Change," Carnall details the cycle of change, which includes stages of denial, anger/blame (leading to performance issues), exploration (acceptance), and finally commitment, aligning with the sequence in option C.

Protocol analysis is an investigation technique where an analyst observes a user performing a task and asks them to verbalize their thoughts, actions, and decisions in real-time. This method, often called the "think-aloud protocol," is used to understand the user's cognitive process, problem-solving strategies, and the specific steps they take to complete their work. The analyst's request for the user to "describe each step in a task as they perform it" is the defining characteristic of this technique.

A. Ethnographic study: This is a long-term, immersive observation of users in their natural environment to understand work culture and context, not a single, narrated task performance.
B. Interviewing: This involves a direct question-and-answer session with a user, which is typically conducted before or after a task, not concurrently with its execution.
C. Activity sampling: This is a quantitative technique used to record the frequency and proportion of time spent on different activities at random intervals, not to analyze a single task in detail.

1. Ericsson, K. A., & Simon, H. A. (1993). Protocol analysis: Verbal reports as data. MIT Press. In Chapter 2, the authors detail the methodology, stating that in concurrent verbal reporting, subjects are instructed "to verbalize their thoughts, which are generated anyway in the course of performing the task" (p. xiii, Preface). This directly corresponds to the scenario.

2. Goguen, J. A., & Linde, C. (1993). Techniques for requirements elicitation. In Proceedings of the 1st IEEE International Symposium on Requirements Engineering (pp. 152-164). IEEE. This paper describes protocol analysis as observing "what users do in performing specific tasks" and analyzing the resulting "protocol" of their behavior. It explicitly contrasts this with ethnography, which focuses on the broader social context of work (Section 3.3, p. 156). DOI: https://doi.org/10.1109/ISRE.1993.324824

3. Nielsen, J. (1994). Usability Engineering. Morgan Kaufmann. Chapter 6 discusses the "Thinking Aloud" method, defining it as a process where "you ask test users to use the system while continuously thinking out loud" to understand their thought process (p. 195).

Brainstorming is a fundamental group creativity technique used to generate a large number of ideas for the solution to a problem. The core principle, as described in the question, is to encourage participants to contribute ideas spontaneously without immediate criticism or evaluation. All ideas are captured and listed, with the analysis and evaluation phase deferred until after the idea generation session is complete. This separation of idea generation from evaluation is a key characteristic of brainstorming, designed to foster a more open and creative environment.

A. Round Robin: This is a specific facilitation method to ensure equal participation, where each person contributes in turn. It can be used during brainstorming but is not the name of the overall technique itself.
C. Mind Mapping: This is a diagramming technique used to visually organize information and ideas around a central concept. While it is an excellent tool for capturing and structuring the output of a brainstorming session, it is not the act of generating the ideas.
D. Mess Finding: This is an initial step in some creative problem-solving models, focused on identifying a broad, ill-defined area of challenge (a "mess") before defining a specific problem to be solved. It precedes the idea generation phase.

1. International Institute of Business Analysis (IIBA). (2015). A Guide to the Business Analysis Body of Knowledge (BABOK Guide)

Version 3.0. Section 10.8.1

"Brainstorming: Purpose

" states

"The goal of brainstorming is to produce a broad or diverse set of options... Participants are encouraged to be creative

to build on the ideas of others

and to withhold judgment or criticism of the ideas that are generated."

2. Coulin

C. (2016). A Situational Approach to Requirements Engineering Processes: A Goal-Based Perspective. Springer. In Chapter 3

Section 3.2.2 "Elicitation Techniques

" brainstorming is described as a technique for generating ideas in a group setting where "criticism is ruled out" and "evaluation is postponed." (DOI: https://doi.org/10.1007/978-3-319-23436-9)

3. University of Washington

Department of Human Centered Design & Engineering. (n.d.). Design Methods: Brainstorming. Courseware. The description outlines the process: "Brainstorming is a method for generating a large quantity of ideas in a short amount of time... Defer judgment. Don't criticize any ideas. All ideas are welcome." This aligns with the scenario of listing ideas for later evaluation.