The actor-task level is the lowest and most detailed level of the business process hierarchy. Its purpose is to show the sequence of actions and decisions taken by specific actors to complete a process. It effectively illustrates the work conducted within each individual task (often referred to as the procedure or work instruction). This level details how the work is performed.

Option A describes the Event-Response level (mid-level).

Option C is only part of the description—the actor is crucial, but the level shows the tasks they perform.

Option D describes the trigger for the Event-Response level.

(Reference: BCS Modelling Business Processes / BCS Business Analysis Practice – Business Process Hierarchy)

===========

Personas are fictional but evidence-based representations of typical users or customer groups. They help business analysts and design teams understand user goals, behaviours, needs, frustrations, and motivations. Personas are often developed from user research and can be based on generic user roles, then enriched with characteristics that make them realistic and useful for analysis. They are not equivalent to a RACI chart because RACI defines responsibility, accountability, consultation, and information responsibilities for tasks. A single real user may also perform multiple roles, so option B is too restrictive. Personas are useful in user-centred design and requirements analysis, but they are not mandatory for decision analysis. Therefore, the true statement is that personas are taken from generic user roles.

A use case diagram is a visual representation of how users (or systems) interact with a system to achieve specific goals. Actors represent the entities (e.g., users or external systems) that expect to receive services from the system.

Key Elements of a Use Case Diagram:

Actors: Represent individuals or systems that interact with the system to achieve a goal.

System Boundaries: Define the scope of the system being modeled.

Users: While " users " may seem similar to actors, the term " actors " is the correct technical term in use case diagrams.

Entities: Entities typically refer to data objects or components, not those receiving services.

Evaluation of Each Option:

A. Actors: Actors are the correct element used to indicate those who expect to receive a service from the system. Conclusion: This is correct .

B. System boundaries: System boundaries define the scope of the system but do not represent those receiving services. Conclusion: This is not correct .

C. Users: While users may interact with the system, the correct term in use case diagrams is " actors. " Conclusion: This is not correct .

D. Entities: Entities represent data objects or components, not those receiving services. Conclusion: This is not correct .

To determine which measures are appropriate Key Performance Indicators (KPIs) for the Critical Success Factor (CSF) " provide excellent customer service, " we must first understand the relationship between CSFs and KPIs:

Critical Success Factors (CSFs): These are the essential areas or activities that an organization must excel at to achieve its goals. In this case, " provide excellent customer service " is a CSF.

Key Performance Indicators (KPIs): These are measurable metrics used to evaluate progress toward achieving a CSF. KPIs should directly align with the CSF and provide actionable insights.

Now, let’s evaluate each option to determine whether it is an appropriate KPI for the CSF " provide excellent customer service " :

A. The number of customers who make use of their in-room mini bar

This measure tracks customer behavior related to a specific hotel amenity (the mini bar). While it may indicate customer satisfaction with the room ' s offerings, it does not directly measure the quality of customer service.

Conclusion: This is not an appropriate KPI for the CSF " provide excellent customer service. "

B. The percentage of customers who use the leisure facilities

This measure tracks how many customers utilize the hotel ' s leisure facilities (e.g., gym, pool, spa). While it may reflect customer engagement with the hotel ' s amenities, it does not directly assess the quality of customer service.

Conclusion: This is not an appropriate KPI for the CSF " provide excellent customer service. "

C. The number of customers who complain

Customer complaints are a direct indicator of dissatisfaction and can highlight areas where customer service needs improvement. A high number of complaints suggests poor customer service, while a low number indicates better service quality.

This measure is closely aligned with the CSF " provide excellent customer service " because it provides actionable feedback on service performance.

Conclusion: This is an appropriate KPI for the CSF.

D. The percentage of customers who join the hotel loyalty scheme

Customers are more likely to join a loyalty scheme if they have had a positive experience with the hotel, including excellent customer service. This measure reflects customer satisfaction and loyalty, which are outcomes of good service.

Conclusion: This is an appropriate KPI for the CSF.

E. The percentage of customers who return

Repeat customers are a strong indicator of customer satisfaction and loyalty, which are directly influenced by the quality of customer service. If customers return to the hotel, it suggests they were satisfied with their previous experience, including the service they received.

Conclusion: This is an appropriate KPI for the CSF.

The hierarchy of requirements organizes requirements into levels (e.g., business needs, stakeholder requirements, solution requirements) to ensure alignment and traceability. Let’s evaluate each statement to determine which is false .

Key Characteristics of the Requirements Hierarchy:

Linking Requirements: The hierarchy ensures that detailed requirements are connected to higher-level business needs and objectives.

Order of Development: The hierarchy does not dictate the sequence in which requirements should be developed; it focuses on relationships and dependencies.

Driven by Strategy: Requirements are derived from the organization ' s values, strategy, and objectives.

Traceability: The hierarchy links different types of requirements to ensure consistency and alignment.

Evaluation of Each Statement:

A. The requirements hierarchy enables detailed requirements to be linked to the business need: This is true; the hierarchy ensures traceability between high-level and detailed requirements. Conclusion: This is true .

B. The requirements hierarchy shows the order in which requirements should be developed: The hierarchy does not specify the development order; it focuses on relationships and dependencies. Conclusion: This is false .

C. Requirements are driven by the organisation ' s values, strategy and objectives: This is true; requirements must align with organizational goals. Conclusion: This is true .

D. The requirements hierarchy links different requirements to each other: This is true; the hierarchy ensures traceability and alignment across levels. Conclusion: This is true .

Final Recommendation:

The false statement is:

B. The requirements hierarchy shows the order in which requirements should be developed.

The Requirements Engineering Framework provides a structured approach for discovering, analysing, validating, documenting, and managing requirements. Its purpose is not to force requirements around a pre-selected solution, because business analysis should first understand the business need and problem before recommending a solution. It also does not only consider technical requirements; it covers business, stakeholder, functional, non-functional, general, and technical concerns as appropriate. The framework is separate from the business case, although requirements may support business case development. The best explanation is that it facilitates better defined requirements by giving the business analyst a disciplined process for elicitation, analysis, validation, and control. This reduces ambiguity, improves traceability, and helps ensure that the final requirements support business objectives.

Change control is a critical aspect of requirements management in business analysis. It ensures that changes to requirements are systematically evaluated, approved, and implemented without negatively impacting the project.

Key Considerations:

Change Control Definition: Change control is a formal process used to manage modifications to requirements, ensuring that changes are necessary, feasible, and aligned with project goals.

Version Numbering: While version numbering is part of documentation management, it is not the primary purpose of change control.

Preventing Changes: Change control does not prevent changes but ensures they are managed appropriately.

Tracing Requirements: Tracing requirements involves tracking their origin and impact, which is separate from managing changes.

Evaluation of Each Option:

A. A process to control version numbering: Version numbering is a documentation practice, not the purpose of change control. Conclusion: This is not correct .

B. A process to manage changes to requirements: This accurately describes change control as a structured approach to handling modifications to requirements. Conclusion: This is correct .

C. A process to ensure that changes cannot be made: Change control does not block changes but ensures they are managed effectively. Conclusion: This is not correct .

D. A process to trace requirements: Tracing requirements is a related but distinct activity focused on linking requirements to their source and impact. Conclusion: This is not correct .

An organization chart visually represents the structure of an organization, including roles, responsibilities, and reporting relationships. By reviewing the organization chart, Sara can learn specific details about the sponsor of her project.

Key Considerations:

Position in the company hierarchy: The organization chart clearly shows where the sponsor fits within the company’s structure (e.g., senior leadership, middle management). This helps Sara understand their level of authority and influence.

Span of control: The chart also reveals how many teams or individuals report to the sponsor, providing insight into their scope of responsibility and decision-making power.

Culture within their team: While the chart may hint at team structure, it does not provide qualitative information about team culture, which requires direct observation or interviews.

Scope of their responsibilities: The chart outlines reporting lines but does not explicitly detail the specific responsibilities of the sponsor.

Preferred management style: Management style is a behavioral trait that cannot be inferred from an organization chart alone.

Evaluation of Each Option:

A. Their position in the company hierarchy: The organization chart explicitly shows the sponsor ' s position in the hierarchy, helping Sara understand their level of authority. Conclusion: This is relevant .

B. Their span of control: The chart reveals how many people or teams report to the sponsor, indicating their span of control. Conclusion: This is relevant .

C. The culture within their team: Team culture is not represented in an organization chart. It requires additional qualitative data. Conclusion: This is not relevant .

D. The scope of their responsibilities: While the chart provides structural information, it does not specify the exact responsibilities of the sponsor. Conclusion: This is not relevant .

E. Their preferred management style: Management style cannot be determined from an organization chart. Conclusion: This is not relevant .

Critical success factors define the areas where an organisation must perform well to achieve its objectives. They are broad success areas, such as improving customer service, reducing operating costs, increasing market share, or improving product quality. Key performance indicators are measurable values used to monitor whether those success factors are being achieved. Therefore, KPIs track progress against CSFs. CSFs are not sub-targets within KPIs; the relationship works the other way around. KPIs also are not measured by CSFs because CSFs are qualitative success areas, while KPIs are measurable indicators. For example, if a CSF is “provide excellent customer service,” relevant KPIs might include complaint numbers, customer satisfaction scores, repeat customer percentage, or response times. This makes option C the correct relationship.

The investigation technique best suited to achieve these outcomes is the Interview. A one-on-one interview provides a private and focused setting, which is essential for discussing confidential or politically sensitive issues that a stakeholder would not be comfortable raising in a group or on a written questionnaire. The personal interaction during an interview is the most effective way to build rapport with the stakeholder, leading to more open and honest communication. This deeper level of trust and detailed conversation is what allows the analyst to gain a richer appreciation of the political and cultural landscape of the business. Special purpose records, document analysis, and questionnaires are more impersonal and cannot provide the same level of qualitative insight or trust.

(Reference: BCS Foundation Certificate in Business Analysis / BCS Business Analysis Practice – Investigative Techniques, Interviews)