SELF-GUIDED BA PRACTICE Packages available · Access after confirmed paymentSee packages ↗

FREE BUSINESS ANALYST REQUIREMENTS PRACTICE

Business Analyst Requirements Example: Make a Cancellation Rule Testable

A useful requirement connects a business need to behavior someone can check. In this original fictional exercise, Juniper Repair Workshop offers scheduled repair classes. Practise turning an unclear cancellation request into a scoped requirement, a user story and acceptance criteria.

This is self-guided Business Analyst (BA) practice. The scenario contains no customer records, completed user research or claim of professional assessment.

1. Separate a claim from the available evidence

A coordinator says, “People cancel too late, and we cannot fill their places.” Treat that as a stakeholder claim. It does not establish how often cancellations happen or whether a different rule would improve attendance.

The exercise supplies three invented requests below. They demonstrate timing and status cases; they are not a representative sample. All times use UTC. The proposed policy permits cancellation at least 24 elapsed hours before a class starts.

Invented requests for a class starting 15 October at 10:00 UTC
BookingRequest timeCurrent status
J0114 October, 10:00 UTCConfirmed
J0214 October, 10:01 UTCConfirmed
J0314 October, 09:00 UTCAlready canceled

Ask the coordinator who approves the cutoff, whether exceptions are needed and how a released place is offered to someone else. Record unanswered questions instead of presenting the proposed policy as established fact.

2. Define the task and its boundaries

The task is to let a booking owner cancel an eligible confirmed booking. Include the eligibility decision, status change and release of one place. Exclude refunds, rescheduling, waiting-list invitations and exception approval from this requirement. Those may need separate decisions.

Before reading the revision, write your own response to this weak draft: “Customers should be able to cancel early enough.” Which words prevent a tester from knowing the expected result?

In scope

  • The eligibility decision
  • The status change to canceled
  • Release of one place

Out of scope (for now)

  • Refunds
  • Rescheduling
  • Waiting-list invitations
  • Exception approval
The boundary of this one requirement. Anything on the right may need its own decision and owner.

3. Write an explicit first attempt

User story: As a workshop participant, I want to cancel my eligible booking so that I can release a place I will not use.

Requirement R1: When the signed-in booking owner requests cancellation, allow it if the booking is confirmed and the class starts at least 24 elapsed hours after the server receives the request. On success, mark it canceled and release one place.

This is an authored proposal for the exercise. The story explains the purpose; R1 defines the decision. Neither replaces confirmation of the policy with its responsible owner.

Requirement R1

When the signed-in booking owner1 requests cancellation, allow it if the booking is confirmed2 and the class starts at least 24 elapsed hours after the server receives the request.3 On success, mark it canceled and release one place.4

  1. Who. Only the owner, which AC4 tests.
  2. Status. A canceled booking cannot be canceled again, which AC3 explores.
  3. Boundary. “At least” includes exactly 24 hours, measured by server time, which AC1 and AC2 test.
  4. Outcome. Exactly one place is released, never two.
R1, part by part. Each highlighted part is a condition a tester can check on its own.

4. Test the boundary and a negative case

These are proposed acceptance cases, not executed software tests. Trace the concern to R1 and each criterion. AC3 exposes a missing repeated-request rule, so add it explicitly before approving the requirement.

The three invented requests placed either side of the 24-hour cutoffBoundary: Cutoff: 14 Oct, 10:00 UTC. At least 24 hours before: J03: 09:00, already canceled; J01: 10:00, exactly 24 hours. Less than 24 hours before: J02: 10:01, refused.At least 24 hoursbeforeJ0309:00, alreadycanceledJ0110:00, exactly 24hoursLess than 24 hoursbeforeJ0210:01, refusedCutoff: 14 Oct, 10:00 UTC
The cutoff as a line. J01 sits exactly on it, which is why “at least” matters; J03 tests status, not time.
Diagram in words
  • At least 24 hours before: J03 (09:00, already canceled); J01 (10:00, exactly 24 hours)
  • Less than 24 hours before: J02 (10:01, refused)
  • Boundary: Cutoff: 14 Oct, 10:00 UTC

5. Explain what remains unresolved

Clarify how concurrent requests avoid releasing a place twice, how times are displayed locally and what happens if a class is canceled by its organizer. A correct cutoff calculation alone does not settle these questions.

Try changing the policy to “more than 24 hours.” J01 should now be refused. Identify every criterion and message affected before changing the wording.

For a larger document exercise, try the separate studio BRD example and outline and its traceability matrix and UAT companion.

Continue with the worked project guide, SQL counting exercise or free demo. Browse all Business Analyst resources. See packages and prices on the pricing page.

Glossary terms in this guide

Browse the full glossary

CHECK BEFORE CONTINUING

Keep your work safe