https://github.com/hassan-ghm/bank-app

Desktop application (Lanterna library) for Client, Account, and Agency Management
https://github.com/hassan-ghm/bank-app

desktop-app desktop-application java lanterna

Last synced: about 1 month ago
JSON representation

Desktop application (Lanterna library) for Client, Account, and Agency Management

• Host: GitHub
• URL: https://github.com/hassan-ghm/bank-app
• Owner: hassan-ghm
• Created: 2024-02-23T11:01:24.000Z (over 1 year ago)
• Default Branch: main
• Last Pushed: 2024-11-23T15:44:27.000Z (6 months ago)
• Last Synced: 2025-04-29T22:58:24.671Z (about 1 month ago)
• Topics: desktop-app, desktop-application, java, lanterna
• Language: Java
• Homepage:
• Size: 3.38 MB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# Banking Application

Desktop application for Client, Account, and Agency Management

## Technologies

  * Lanterna library (JAVA)

## Architecture

  * MVC	

## User list

* test-case:{

  * email:[email protected]

  * password:bob

  * role:client

  

  * username:[email protected]

  * password:ben

  * role:manager

 }

## Divers

  

  * DB:{

  	* db.user=root

	* db.password= root or empty

  }

## App

### Database class diagram

![database](assets/database.png)

### Login and BackToTheFuture

![login](assets/login.png)

The purpose behind this is to allow users, upon logging into the application, to freely define the current date and time within the app. This custom date and time are independent of the computer's system clock, enabling users to set it to any point in the past or future. The goal of this feature is to simplify testing by allowing users to effectively "travel through time" 😉.

When launching the application, on the login screen, the user can choose one of two options:

Use the system date and time (from the computer's clock).

Manually set a fixed date and time.

In the first option, the application operates in "real-time." This means actions like recording the creation date of transfers will use the computer's current date and time, which updates continuously.

In the second option, time is frozen at the user-defined date and time, remaining fixed.

A logical side effect of this second option is that, since the present time is defined by the user, any transfers in the database with a creation date/time later than this defined present must be removed. Otherwise, they would belong to the "future," and our application isn’t designed to handle future data!

### Client

#### AccountList

![accountList](assets/account-list.png)

#### AccountDetails

![accountDetails](assets/account-details.png)

#### CreateTransfer

![createTransfer](assets/create-transfer.png)

### Admin

#### AgencyDetails

![agencyDetails](assets/agency-details.png)

#### CreateClient

![createClient](assets/create-client.png)