Account management (java/eclipse)

Project: account management Background informations The CBS (Credit Bank of Switzerland) commissioned your project group to implement the new account management. An account of this bank has the attributes (each is obligatory) • Account number (all number between 1000000 and 9999999), identifying • Account owner • Opening date (new creation date) • Change date • Status: active (default), blocked or deleted Specifically, there are the terms "savings account" (attributes interest rate and period of notice in days) and "current account" (attributes dispositions and disposition rate). Requirements The program is intended to support the administration (re-creation, editing) of accounts via a GUI interface. By double-clicking on a tab entry, the corresponding account is displayed in the upper part of the table and can be edited there. The following rules apply: The account number and the opening date are automatically assigned when you create a new one, change date when you create or change the new data; These attributes can not be entered or changed by the user. Physical deletion of accounts is not possible, but they are transferred to the "deleted" status. Such accounts can not be modified, but display is possible. The account number of «deleted» accounts can not be used for other accounts. A button (or menu) "New" can be used to create new accounts. For the assignment of a customer to the account, a selection list exists which contains the names of all customers. It is possible to print out a selected account as well as to display a list of all accounts (sorted by customer number, account number) with complete information. Simulate printing by consoles. Implementation Provide an abstract class account with matching Comparator, methods toString (), equals (), and hashCode (), as well as specific classes, checking account and saving account. Use the DAO programming model for the database accesses of these entities, which do not really need to be persisted. It is sufficient to manage these in a dynamic list (see next paragraph). An appropriate class and a rudimentary DAO implementation are provided for the entity customer. Customers should not be managed (newly created, changed, etc.) but should only be displayed for the selection of an account owner. For this, there are the classes [login to view URL] and [login to view URL] (an interface is not used). Deadline, Payment and other We need the code until Sunday (18 July, 12PM [Central European Time]). We offer you 60 US Dollars; You will be paid through PayPal. There is an existing code which you may use (German). We expect a functioning account management which satisfies all conditions above. Thank you in advance for your help!