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

Business analysis glossary

Precondition and Postcondition

What it is

A precondition is something that must be true before a use case or test can start, such as the user being logged in. A postcondition is what must be true after it ends, such as an order being saved with status Paid. Together they define the boundaries of a use case or test case.

Why it matters

Clear preconditions stop teams from building or testing a scenario in an impossible starting state. Postconditions make the result checkable and show what other processes can rely on afterwards. Both are especially useful for testers, who turn them into setup steps and expected results.

Example

For the use case Approve Invoice at Teakwood Finance, the preconditions are: the approver is logged in and the invoice has a matching purchase order and goods receipt. The postconditions are: the invoice status is Approved, the approval is recorded in the audit trail and the invoice appears in the next payment run.

CHECK BEFORE CONTINUING

Keep your work safe