The First Central Savings Bank has asked you to help them design a Java application as part of a technology initiative. Customers are able to secure loans from this bank for automobiles, education and homes. At this point, the IT management staff has asked you to provide them with UML design diagrams, including a class diagram, a use-case diagram, and a sequence diagram, that will help them understand what your application will do. The IT management staff has already completed a list of requirements for the application. They are listed below. 

The requirements for the application are: 

•The application will act as a support system for the bank.
•The bank lends to borrowers, who have checking and/or savings accounts.
•An employee of the bank interacts with the customers. The employee's work is supported by the system.
•Modifications to information such as name and ownership changes can be made easily by using the application.
•The application is able to run under most operating systems, including UNIX and Windows, and has a modern graphical user interface.
•The application is designed for future growth. 
The actors in the bank will be identified as the employees and the borrowers. The employees are the users of the system and the borrowers are the customers. However, the system should enable the borrower to submit a request directly through the system or through an employee.

First, create a class diagram of the bank application from these requirements. Your classes will correspond to Borrower, Account Details, etc. Each will be a class. You can use any UML tool you have access to or you may use Word to create the diagram - just make sure it is legible. 

Second, identify what the banking system will be used for and who will be using it. These are the use cases and actors, respectively. All use cases must begin with an actor, and some will end with an actor as well. Actors are people or other systems that are outside of the system you are working on. Prepare and submit the use case diagram.

Finally, identify the major actors in the banking system and then create a use case diagram of the banking system. Each of the use cases should be completely documented. At a very minimum, your documentation should include the following: Use case name, description, actors in the use case, and sequence diagrams. Here are a few use cases to get you started: 

•Create an account
•Submit request for a loan
•Pay on an existing loan
•Update or Remove Customer
•Modify customer information
•Close an account 
You should be able to identify additional use cases on your own. Here is an article that provides guidelines for documenting use cases. Documenting the use case.