barcodefontsoft.com

Client/Server Software Architecture Case Study in Software Assign barcode 39 in Software Client/Server Software Architecture Case Study

Client/Server Software Architecture Case Study using software toget code39 for asp.net web,windows application Developing with Visual Studio .NET Withdraw Funds include include Query Account ATM Customer Transfer Funds include Validate PIN Add Cash Startup ATM Operator Shutdown Figure 21.1. Banking System use case model However, b bar code 39 for None y comparing the three use cases, it can be seen that the rst part of each use case namely, reading the ATM card and validating the customer s PIN is common to all three use cases. This common part of the three use cases is factored out as an inclusion use case called Validate PIN. The Withdraw Funds, Query Account, and Transfer Funds use cases can then each be rewritten more concisely as concrete use cases that include the Validate PIN inclusion use case.

The relationship between the use cases is shown in Figure 21.1. The concrete Withdraw Funds use case starts by including the description of the Validate PIN inclusion use case and then continues with the Withdraw Funds description.

The concrete Transfer Funds use case also starts with the description of the Validate PIN inclusion use case, but then continues with the Transfer Funds description. The revised concrete Query Account use case is similarly organized. The inclusion use case and concrete use cases are described next.

The main sequence of the Validate PIN use case deals with reading the ATM card, validating the customer s PIN and card. If validation is successful, the system prompts the customer to select a transaction: withdrawal, query, or transfer. The alternative branches deal with all the possible error conditions, such as the customer enters the wrong PIN and must be re-prompted, or an ATM card is not recognized or has been reported stolen, and so on.

Because these can be described quite simply in the alternative sequences, splitting them off into separate extension use cases is not necessary.. Case Studies 21.2.1 Validate PIN Use Case Use case n ame: Validate PIN Summary: System validates customer PIN Actor: ATM Customer Precondition: ATM is idle, displaying a Welcome message. Main sequence: 1. Customer inserts the ATM card into the card reader.

2. If system recognizes the card, it reads the card number. 3.

System prompts customer for PIN. 4. Customer enters PIN.

5. System checks the card s expiration date and whether the card has been reported as lost or stolen. 6.

If card is valid, system then checks whether the user-entered PIN matches the card PIN maintained by the system. 7. If PIN numbers match, system checks what accounts are accessible with the ATM card.

8. System displays customer accounts and prompts customer for transaction type: withdrawal, query, or transfer. Alternative sequences: Step 2: If the system does not recognize the card, the system ejects the card.

Step 5: If the system determines that the card date has expired, the system con scates the card. Step 5: If the system determines that the card has been reported lost or stolen, the system con scates the card. Step 7: If the customer-entered PIN does not match the PIN number for this card, the system re-prompts for the PIN.

Step 7: If the customer enters the incorrect PIN three times, the system con scates the card. Steps 4 8: If the customer enters Cancel, the system cancels the transaction and ejects the card. Postcondition: Customer PIN has been validated.

. 21.2.2 Withdraw Funds Concrete Use Case Use case n ame: Withdraw Funds Summary: Customer withdraws a speci c amount of funds from a valid bank account. Actor: ATM Customer Dependency: Include Validate PIN use case. Precondition: ATM is idle, displaying a Welcome message.

. Client/Server Software Architecture Case Study Main seque nce: 1. Include Validate PIN use case. 2.

Customer selects Withdrawal, enters the amount, and selects the account number. 3. System checks whether customer has enough funds in the account and whether the daily limit will not be exceeded.

4. If all checks are successful, system authorizes dispensing of cash. 5.

System dispenses the cash amount. 6. System prints a receipt showing transaction number, transaction type, amount withdrawn, and account balance.

7. System ejects card. 8.

System displays Welcome message. Alternative sequences: Step 3: If the system determines that the account number is invalid, then it displays an error message and ejects the card. Step 3: If the system determines that there are insuf cient funds in the customer s account, then it displays an apology and ejects the card.

Step 3: If the system determines that the maximum allowable daily withdrawal amount has been exceeded, it displays an apology and ejects the card. Step 5: If the ATM is out of funds, the system displays an apology, ejects the card, and shuts down the ATM. Postcondition: Customer funds have been withdrawn.

.
Copyright © barcodefontsoft.com . All rights reserved.