| <?xml version="1.0" encoding="UTF-8"?> |
| <org.eclipse.epf.uma:GuidanceDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-qq-9Brh5oa6H3lsdp-m8mQ" name=",_JLOiIMNvEdu2IdAIaWZyAw" guid="-qq-9Brh5oa6H3lsdp-m8mQ" changeDate="2009-08-05T09:49:49.000-0700" version="7.2.0"> |
| <mainDescription><h3>
 |
| 1 Brief Description
 |
| </h3>
 |
| <p>
 |
| This use case describes how the Bank Customer uses the ATM to withdraw money to his/her bank account.
 |
| </p>
 |
| <h3>
 |
| 2 Actors
 |
| </h3>
 |
| <h4>
 |
| 2.1 Bank Customer
 |
| </h4>
 |
| <h4>
 |
| 2.2 Bank
 |
| </h4>
 |
| <h3>
 |
| 3 Preconditions
 |
| </h3>
 |
| <p>
 |
| There is an active network connection to the Bank.<br />
 |
| <br />
 |
| The ATM has cash available.
 |
| </p>
 |
| <h3>
 |
| 4 Basic Flow of Events
 |
| </h3>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| 1. The use case begins when Bank Customer inserts their Bank Card.
 |
| </p>
 |
| <p>
 |
| 2. Use Case: Validate User is performed.
 |
| </p>
 |
| <p>
 |
| 3. The ATM displays the different alternatives that are available on this unit. [See Supporting Requirement SR-xxx
 |
| for list of alternatives]. In this case the Bank Customer always selects "Withdraw Cash".
 |
| </p>
 |
| <p>
 |
| 4. The ATM prompts for an account. See Supporting Requirement SR-yyy for account types that shall be supported.
 |
| </p>
 |
| <p>
 |
| 5. The Bank Customer selects an account.
 |
| </p>
 |
| <p>
 |
| 6. The ATM prompts for an amount.
 |
| </p>
 |
| <p>
 |
| 7. The Bank Customer enters an amount.
 |
| </p>
 |
| <p>
 |
| 8. Card ID, PIN, amount and account is sent to Bank as a transaction. The Bank Consortium replies with a go/no go
 |
| reply telling if the transaction is ok.
 |
| </p>
 |
| <p>
 |
| 9. Then money is dispensed.
 |
| </p>
 |
| <p>
 |
| 10. The Bank Card is returned.
 |
| </p>
 |
| <p>
 |
| 11. The receipt is printed.
 |
| </p>
 |
| <p>
 |
| 12. The use case ends successfully.
 |
| </p>
 |
| </blockquote>
 |
| <h3>
 |
| 5 Alternative Flows
 |
| </h3>
 |
| <h4>
 |
| 5.1 Invalid User
 |
| </h4>
 |
| <p>
 |
| If in step 2 of the basic flow Bank Customer the use case: Validate User does not complete this successfully, then
 |
| </p>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| 1. The use case ends with a failure condition.
 |
| </p>
 |
| </blockquote>
 |
| <h4>
 |
| 5.2 Wrong account
 |
| </h4>
 |
| <p>
 |
| If in step 8 of the basic flow the account selected by the Bank Customer is not associated with this bank card, then
 |
| </p>
 |
| <p>
 |
| 1. The ATM shall display the message "Invalid Account – please try again".
 |
| </p>
 |
| <p>
 |
| 2. The use case resumes at step 4.
 |
| </p>
 |
| <h4>
 |
| 5.3 Wrong amount
 |
| </h4>
 |
| <p>
 |
| If in step 7 in the basic flow, the Bank Customer enters an amount that can't be 'created' with the kind of in the ATM
 |
| (See Special Requirement WC-1 for valid amounts), then
 |
| </p>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| 1. The ATM shall display a the message indicating that the amount must be a multiple of the bills on hand, and ask
 |
| the Bank Customer to reenter the amount.
 |
| </p>
 |
| <p>
 |
| 2. The use case resumes at step 7.
 |
| </p>
 |
| </blockquote>
 |
| <h4>
 |
| 5.4 Amount Exceeds Withdrawal Limit
 |
| </h4>
 |
| <p>
 |
| If in step 7 in the basic flow, the Bank Customer enters an amount that exceeds the withdrawal limit (See Special
 |
| Requirement WC-2 for maximum amount), then
 |
| </p>
 |
| <p>
 |
| 1. the ATM shall display a warning message, and ask the Bank Customer to reenter the amount
 |
| </p>
 |
| <p>
 |
| 2. The use case resumes at step 7
 |
| </p>
 |
| <h4>
 |
| 5.5 Amount Exceeds Daily Withdrawal Limit
 |
| </h4>
 |
| <p>
 |
| If in step 8 in the basic flow, the Bank response indicates the daily withdrawal limit has been exceeded (this is
 |
| determined by the Bank and depends upon the specific account), then
 |
| </p>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| 1. The ATM shall display a warning message, and ask the Bank Customer to reenter the amount.
 |
| </p>
 |
| <p>
 |
| 2. The use case resumes at step 7.
 |
| </p>
 |
| </blockquote>
 |
| <h4>
 |
| 5.6 Insufficient Cash
 |
| </h4>
 |
| <p>
 |
| If in step 7 in the basic flow, the Bank Customer enters an amount that exceeds the amount of cash available in the
 |
| ATM, then
 |
| </p>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| 1. The ATM will display a warning message, and ask the Bank Customer to reenter the amount.
 |
| </p>
 |
| <p>
 |
| 2. The use case resumes at step 7.
 |
| </p>
 |
| </blockquote>
 |
| <h4>
 |
| 5.7 No Response from Bank
 |
| </h4>
 |
| <p>
 |
| If in step 8 of the basic there is no response from the Bank within 3 seconds, then
 |
| </p>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| 1. The ATM will re-try, up to three times.
 |
| </p>
 |
| <p>
 |
| 2. If there is still no response from the Bank, the ATM shall display the message "Network unavailable – try again
 |
| later".
 |
| </p>
 |
| <p>
 |
| 3. The ATM shall return the card.
 |
| </p>
 |
| <p>
 |
| 4. The ATM shall indicate that it is "Closed".
 |
| </p>
 |
| <p>
 |
| 5. The use case ends with a failure condition.
 |
| </p>
 |
| </blockquote>
 |
| <h4>
 |
| 5.8 Money Not Removed
 |
| </h4>
 |
| <p>
 |
| If in step 9 of the basic flow the money is not removed from the machine within 15 seconds, then
 |
| </p>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| 1. the ATM shall issue a warning sound and display the message "Please remove cash".
 |
| </p>
 |
| <p>
 |
| 2. If there is still no response from the Bank Customer within 15 seconds the ATM will re-tract the money and note
 |
| the failure in the log.
 |
| </p>
 |
| <p>
 |
| 3. the use case end with a failure condition.
 |
| </p>
 |
| </blockquote>
 |
| <h4>
 |
| 5.9 Quit
 |
| </h4>
 |
| <p>
 |
| If at point prior to step 8 in the basic flow the Bank Customer selects Quit, then
 |
| </p>
 |
| <blockquote dir="ltr" style="MARGIN-RIGHT: 0px">
 |
| <p>
 |
| 1. The ATM shall print a receipt indicating the transaction was cancelled.
 |
| </p>
 |
| <p>
 |
| 2. The ATM shall return the card.
 |
| </p>
 |
| <p>
 |
| 3. The use case ends.
 |
| </p>
 |
| </blockquote>
 |
| <h3>
 |
| 6 Key Scenarios
 |
| </h3>
 |
| <h4>
 |
| 6.1 No Response from Bank
 |
| </h4>
 |
| <h3>
 |
| 7 Post-conditions
 |
| </h3>
 |
| <h4>
 |
| 7.1 Successful Completion
 |
| </h4>
 |
| <p>
 |
| The user has received their cash and the internal logs have been updated.
 |
| </p>
 |
| <h4>
 |
| 7.2 Failure Condition
 |
| </h4>
 |
| <p>
 |
| The logs have been updated accordingly.
 |
| </p>
 |
| <h3>
 |
| 8 Special Requirements
 |
| </h3>
 |
| <p>
 |
| [SpReq:WC-1] The ATM shall dispense cash in multiples of $20.
 |
| </p>
 |
| <p>
 |
| [SpReq2:WC-2] The maximum individual withdrawal is $500.
 |
| </p>
 |
| <p>
 |
| [SpReq:WC-1] The ATM shall keep a log, including date and time, of all complete and incomplete transactions with the
 |
| Bank.
 |
| </p></mainDescription> |
| </org.eclipse.epf.uma:GuidanceDescription> |
