1. The Project
Manager at Janes Technologies has created the use case diagram for the
InfoSuper bank ATM system. Now, the InfoSuper bank wants Janes Technologies to
develop a prototype with few basic functions of the proposed software system
before proceeding with the final software development. The functions that the
InfoSuper bank wants in the ATM prototype are:
Allow customers to withdraw cash from the current and savings accounts.
Allow customers to change their PIN.
Allow customers to obtain a transaction summary. Moreover, the ATM machine validates the ATM card and PIN of the bank customers before allowing them to use other features. The Project Manager, Jennifer, adopts an iterative approach for the development of the software system. She decides to deliver the prototype after the second iteration of the software development life cycle. In the first iteration, Jennifer plans to implement the required functions only for the savings accounts. In the second iteration, she plans to implement the required functions for the current accounts as well. Help Jennifer to identify the system boundaries and create the use case diagrams for each prototype.
Ans To create the use case diagram of the ATM system, you need to perform the following tasks:
1. Identify the use cases and actors for the first iteration.
2. Identify the use cases and actors for the second iteration.
Identifying the Use Cases and Actors for the First Iteration
To identify the system boundary for the first iteration, you need to identify the use cases and actors. The use cases for the first iteration are:
• Cash Withdrawal (Savings)
• PIN Change (Savings)
• Transaction Summary (Savings)
The actors for the first iteration are:
• Bank Customer
• Centralized Bank System
In the first iteration, the Cash Withdrawal (Savings). Change PIN (Savings), and Transaction Summary (Savings) use cases can be performed only when the customer is validated by the centralized bank system. Therefore, the Validation use case should be included in the Cash Withdrawal (Savings), Change PIN (Savings), and Transaction Summary (Savings) use cases.
Identifying the Use Cases and Actors for the Second Iteration
In the first iteration, the use case diagram for the savings account is created. Now. in the second iteration, the use cases need to implement the current account function. The basic functions of the corresponding use cases in both the iterations are the same. Therefore, the functions of the use cases of the first iteration can be extended to obtain the use cases of the second iteration.
The following figure depicts the use case diagram that represents how the functions of the use cases of the first iteration can be extended to obtain the use cases of the second iteration.
Allow customers to withdraw cash from the current and savings accounts.
Allow customers to change their PIN.
Allow customers to obtain a transaction summary. Moreover, the ATM machine validates the ATM card and PIN of the bank customers before allowing them to use other features. The Project Manager, Jennifer, adopts an iterative approach for the development of the software system. She decides to deliver the prototype after the second iteration of the software development life cycle. In the first iteration, Jennifer plans to implement the required functions only for the savings accounts. In the second iteration, she plans to implement the required functions for the current accounts as well. Help Jennifer to identify the system boundaries and create the use case diagrams for each prototype.
Ans To create the use case diagram of the ATM system, you need to perform the following tasks:
1. Identify the use cases and actors for the first iteration.
2. Identify the use cases and actors for the second iteration.
Identifying the Use Cases and Actors for the First Iteration
To identify the system boundary for the first iteration, you need to identify the use cases and actors. The use cases for the first iteration are:
• Cash Withdrawal (Savings)
• PIN Change (Savings)
• Transaction Summary (Savings)
The actors for the first iteration are:
• Bank Customer
• Centralized Bank System
In the first iteration, the Cash Withdrawal (Savings). Change PIN (Savings), and Transaction Summary (Savings) use cases can be performed only when the customer is validated by the centralized bank system. Therefore, the Validation use case should be included in the Cash Withdrawal (Savings), Change PIN (Savings), and Transaction Summary (Savings) use cases.
Identifying the Use Cases and Actors for the Second Iteration
In the first iteration, the use case diagram for the savings account is created. Now. in the second iteration, the use cases need to implement the current account function. The basic functions of the corresponding use cases in both the iterations are the same. Therefore, the functions of the use cases of the first iteration can be extended to obtain the use cases of the second iteration.
The following figure depicts the use case diagram that represents how the functions of the use cases of the first iteration can be extended to obtain the use cases of the second iteration.
No comments:
Post a Comment