Is Expected Outcome interchangeable with Postcondition depending on your use case structure?
Should Expected Outcome and Postcondition be explicitly differentiated from each other?
Say I have a snippet of the use case of withdrawing money from an ATM (agrees to issue receipt):
Description: This use case describes how a Bank Customer uses an ATM to withdraw money from their bank account
Customer inserts their bank card into the card reader of the ATM
System ejects the Customer's bank card; the Customer takes the bank card from the machine
Should the Expected Outcome be:
Expected Outcome: The ATM dispenses the requested amount of the Customer
Expected Outcome: The Customer obtains cash from the machine
with the Postcondition having
Postcondition: The Customer obtains the receipt from the machine; the system records a transaction log entry for the withdrawal
I was thinking that the Expected Outcome should be the latter since it agrees with the Description while the Postcondition enumerates the activities/conditions that the system will perform upon successful execution of the use case. Am I in the right logic here?