The PiggyBank online banking system
The city in which the PiggyBank and CityBank exist use the dollar as currency. The smallest unit of the currency is the single dollar. There are no cents and all transactions resolve evenly.
When customers open a new account with the PiggyBank, they receive an information pack that contains unique name and password information to log in to the PiggyBank Internet banking system. Because the PiggyBank Internet banking system uses a Web interface, customers can connect to it from home, or anywhere else, with an internet browser. With this system, customers can perform banking operations online, such as displaying the balance of an account or transferring money.
The customers can also interact with the PiggyBank tellers to perform common transactions such as cashing checks, performing withdrawals, and transferring money. Note that the PiggyBank does not issue checks. In the PiggyBank branches, the tellers use various Java-enabled terminals, such as Windows, Linux, and Java™ computers. To cash checks, tellers use a fat-client application with a graphical user interface. Before this application transfers the money to the given PiggyBank account, it connects to a Web service that CityBank provides. The CityBank Web service verifies the check validity and approves the withdrawal.
The PiggyBank has requested a complete online banking system to enable customers to bank over the Internet and to automate existing teller operations. The system must be robust enough to meet the demands of the PiggyBank customers, and scalable enough to grow as the number of PiggyBank customers increases. Customers must be able to access the online banking system by using any secure browser. The system must be platform-independent, because the PiggyBank branch uses many different types of computer.
The proposed solution uses IBM® Rational® modeling products to build a complete model of the system. The architecture of the system is designed around three model types: a use-case model, an analysis model, and a design model. The use-case model captures the requirements of the online banking system and defines how the users of the application, such as customers and tellers, interact with the system. The requirements model is realized to create an analysis model that describes how the new system addresses the needs of PiggyBank. The design model addresses the design of the final implementation by providing the blueprints for the final application. Finally, the application is implemented by transforming UML models to code and by implementing the source code of the application.