Bank Of Zuvie     Online Banking Prototypes 
                                        
                         9.A Explanation of the technologies  
                                        
                                            Online Banking Prototypes 
                          
                          
                                                                                     MVC architecture  

                    
                    
                                                 Model:   
The Model is the part of the application that handles the data and business rules.
It stores the data and updates the controller or view whenever that data change.

LoginBean
JavaBeans have been used to retrieve and manage the Available Balance and Total Balance of the account.
Validation       
The Servlet checks the customer’s bank details in the database to verify and process the requested transaction.
 i.e   Customer  credentials.
getLastLogon()  
In order to display the most recent current account transactions, the system compares the last log-on date
with the current log-on date to identify any new transactions since the user’s previous session.

                                                    View:  
It represents the presentation layer of the application.
 It is responsible for displaying the data provided by the model to the user in a suitable format.
 
Home.jsp
it displays the current account balance.
balance.jsp
It displays the updated current account balance to the user.

                                             Controller:   
It works with both the model and the view. It is being used to manage the flow of the application .
controlling how data moves within the model objects and ensuring the view is updated whenever the data changes.

Login.java
This class verifies the customer’s login credentials against the database.
If the username and password match the stored records, the customer
is authenticated and granted access to their online banking account.
Otherwise, an error message is displayed and access is denied.

TransactionProcess.java
This servlet handles all customer transaction requests. 
It processes payment operations to designated payees and updates the customer’s account
details in the database accordingly. After each successful transaction, it creates a new transaction record 
for the customer’s account statement to maintain an accurate and up-to-date balance history.

        
Diagram: Fund Flow Between Accounts

  

Functional Description (System Requirements)  


1. Current Account A (main account) – this is the primary account where funds are held.
2. Current Account B (secondary account) – receives transfers from Current Account A.
3. Credit Card Account – receives payments from Current Account A as well.

The setup works like this:

Funds Flow 

  Current Account A → Current Account B (regular transfers, maybe standing orders or automatic sweeps).
  Current Account A → Credit Card Account (to pay down balances, e.g., minimum payment or full amount).

    Purpose

  Current Account A acts as the “source.”
  Current Account B could be for savings, household expenses, or business use.
  The Credit Card Account is for managing debt and ensuring timely repayments.

  Possible Features to Develop  

  1. Scheduled Transfers – automatic rules to move money from Account A to B on certain dates.
  2. Credit Card Payments – direct debit setup from Account A to the card.
  3. Balance Rules – e.g., always leave a minimum balance in Account A before transferring.
  4. Notifications – alerts when transfers or payments happen

Credit Card Payment Testing

The shopping cart module was implemented to test and validate the 
credit card payment process within the online store.
When users added products to the shopping cart and proceeded to checkout,
the system simulated a credit card transaction to verify payment processing logic.

The testing ensured:

Successful validation of card details.
Accurate deduction of the transaction amount.
Proper update of customer account balance.
Confirmation message generation after payment completion.
This module played a key role in confirming the integration
between the shopping cart, payment gateway, and database.


 Technologies Used  

The online banking web application is being  developed using several key technologies that work together 
to provide a secure, responsive, and efficient system for users to manage their accounts and perform transactions.

 HTML5   is being  used to design and structure the web pages. It defines the layout and content of the user
 interface, such as the login screen, account overview, and transaction forms.

 CSS3    is being  applied to style the web pages and enhance the visual appearance of the system.
 CSS3 animations, including the use of the `@keyframes` rule, are being implemented to provide 
smooth transitions and interactive effects, improving the overall user experience.

 Java   (Servlets and JSP) form the core of the backend logic. Servlets handle requests from users,
 process banking transactions such as payments and fund transfers, and communicate with the database
 to update account details. JSP (JavaServer Pages) is being used to dynamically generate 
the web pages displayed to users.

 JDBC  (Java Database Connectivity) is being  used to enable communication between the Java Servlets and 
the database. It allows the application to execute SQL queries to retrieve, insert, and update data securely.

 Database   (MySQL or Oracle) serves as the central storage for customer details, account balances,
 and transaction records. The database ensures that all financial data remains consistent and 
persistent after every transaction.

 Apache Tomcat Server   is being  used as the web container to deploy and run the Java-based application.
 It processes client requests, manages Servlets and JSPs, and serves dynamic content to users via a web browser.

Finally,  JavaScript    is being  used on the client side to provide form validation and
 interactive elements, ensuring that user inputs are verified before submission and enhancing usability.