In ATDD (Acceptance Test-Driven Development), business process modeling (e.g., using BPMN) is a powerful way to visualize workflows and system behavior from the user ' s perspective. Testers can use these models to derive acceptance test cases by covering different business paths, including normal flows, alternate flows, and exception conditions.

Option A is correct because it reflects this practical usage: testers analyze the business process model and create test cases to ensure coverage of the different paths the system might take. This aligns acceptance testing directly with business logic and enhances traceability.

Other options:

B is partially valid but less direct; business analysts help define rules, but test case creation is a tester ' s role.

C reverses the correct flow; BPMN models are often created first and used to define or validate acceptance criteria, not the other way around.

D is incorrect — requirements/user stories are usually defined through stakeholder collaboration, not auto-generated from BPMN diagrams.

Answer: A. Testers use business process models to write test cases that cover the different paths.

In cross-functional, globally distributed teams, establishing collaboration, communication, and trust is key. A workshop (even virtual) is a proven method for initiating alignment, especially when a new team member joins, and project coordination is weak.

Option A promotes transparency and collective understanding, crucial for building team cohesion.

Option B is too passive and one-directional. Long emails rarely solve coordination problems in Agile or collaborative contexts.

Option C is about tool setup, not team integration or communication — tools are supportive but not substitutes for human connection.

Option D is not efficient; traveling to meet each team member is impractical and doesn’t guarantee a shared team vision.

✔ Answer: A. You organize a workshop with all team members to establish common understanding and to lay the foundation for fruitful trusting collaboration.

In BPMN models, additional annotations such as links to requirements, test data, or risks improve the value of the diagram for downstream stakeholders like testers. When BPMN tasks or flows are linked to known risks, testers can prioritize regression test cases accordingly — a key principle in risk-based testing.

Option D is correct because linking risks to business processes gives testers meaningful input for deciding which parts of the system require deeper or repeated testing.

Other options:

A: Priority links are useful, but less impactful than risk-based test selection.

B: Links to test equipment are not commonly embedded in process diagrams and are more relevant to hardware or system integration testing.

C: Linking to requirements helps traceability, but execution readiness is more closely tied to test cases and data than to BPMN.

Answer: D. Link to risks provide input to testers for selecting regression tests

The medical scanner must be able to examine at least 50 patients per day. This requirement directly impacts hospital operations and service efficiency. If the scanner fails to meet performance requirements, such as processing speed or availability, it will affect the hospital’s ability to deliver services to patients — impacting schedules, patient flow, and ultimately the business goals of the hospital.

Option C is correct because it reflects the consequences of performance shortfalls from a business outcome perspective: failure to meet this requirement may result in financial loss, compliance issues, or customer dissatisfaction.

Other options:

A (User perspective) is involved, but the impact here is primarily operational/business.

B (Functional perspective) refers to whether the scanner has the correct features, not performance.

D (Technical perspective) is also relevant, but the business impact (e.g., service delivery) takes precedence in this case.

Answer: C. Business perspective