Acceptance criteria should define how the system behaves for a given user story or requirement. They must be precise, testable, and directly traceable to the requirement being verified.

REQ 3-12 describes access control for three user types. Option B is a concrete, scenario-based acceptance criterion that tests the enforcement of access rights — making it an ideal match.

Other options:

A is irrelevant — database technology (MongoDB) is an implementation detail, not a functional criterion.

C is too vague — stating that security tests must be performed doesn’t specify expected behavior or outcome.

D is plausible, but option B more directly demonstrates how an actual system behavior validates the requirement.

Answer: B. Since I am logged in as a department manager, when I try to access the file of an employee who is not in my department then a message telling me that I do not have access rights is displayed

Usability testing aims to evaluate the ease of use, efficiency, and satisfaction with which users can achieve tasks. When checking the ergonomics (e.g., layout, visual clarity, interaction comfort), checklist-based evaluations are particularly useful.

Option A is correct because a checklist of ergonomic/usability heuristics (e.g., Nielsen’s heuristics, ISO 9241 standards) allows evaluators to systematically assess whether the interface meets established usability criteria.

Other options:

B (Biometrics-based evaluation) tracks physiological responses (e.g., stress or eye movement), which are useful but indirect and less targeted to ergonomic checks.

C (Walkthroughs) help assess usability by observing task flows, but they are less focused on layout and ergonomic design.

D (Log file analysis) captures behavior but not directly ergonomic issues like spacing, font size, or element alignment.

Answer: A. Checklist-based evaluation

Comprehensive Detailed Explanation (Approx. 200–220 words):

This question focuses on the coverage criterion “execute all possible process tasks” from the BPMN model of a $100 withdrawal.

Let’s analyze the process:

The process starts when the user selects “Withdraw $100.”

A decision gateway checks if the balance is ? $100.

If NO: the card is removed and withdrawal is rejected.

If YES: the user is prompted to select whether they want a receipt.

Depending on the user’s choice:

If YES: the receipt is printed ? then $100 is withdrawn ? card is removed.

If NO: $100 is withdrawn ? card is removed (no receipt printed).

To meet the criterion “execute all possible process tasks,” we must cover:

Rejected withdrawal path (balance < 100)

Withdrawal without receipt

Withdrawal with receipt

Receipt printing

Card removal in both success and failure

Test case coverage:

Test 1 (balance = $100, receipt = YES): covers successful withdrawal + receipt printed.

Test 3 (balance = $85): covers withdrawal rejected + card removed.

Together, these two tests execute all possible process tasks:

Withdraw with receipt

Reject due to insufficient balance

Receipt printed

Withdraw funds

Remove card

Other test combinations are redundant or do not add new path coverage.