Project Title: Online Banking System Design and Architecture

Project Overview:

The aim of the project is to determine the design and architecture of the Online Banking System project as an application for the Software Design and Architecture course. This project aims to provide students with practical experience in designing a complex software system with a focus on scalability, maintainability and security. Students will collaborate in teams to design the architecture of the online banking system, considering various architectural patterns, design principles, and best practices.

Project scope:

The project will include the design of an online banking system that includes the following components and features:

User authentication and authorization

Account management $($e$.$g$.$ opening$/$closing account, updating account information$)$

Inter$-$account fund transfer

Bill payment functionality

Transaction history and statement creation

Security measures $($e$.$g$.$ encryption, secure authentication$)$

Scalability to manage concurrent users and transactions

Purposes:

Gain practical experience in applying software design principles and architectural patterns to real$-$world scenarios.

Understanding the trade capacity involved in architectural decision$-$making, e$.$g$.$

performance etc. scalability or security etc. such as availability. Develop a comprehensive software architecture by collaborating effectively in a team environment

create document.

Make design decisions effectively through architecture diagrams and documentation

Learning to convey.

Gain insight into industry best practices in designing scalable, maintainable and secure software systems.Architecture:

High Level Architecture:

The online banking system will follow a layered architectural pattern to separate concerns and facilitate maintenance through modularity.

The main layers of the Architecture include:

Presentation Layer: Responsible for web or mobile interfaces for user interaction.

Application Layer: Contains business logic and workflows to process user requests and transactions.

Domain Layer: Represents the main domain entities and business rules of the banking system.

Data Access Layer: Manages data storage and retrieval by interacting with the database.

Integration Layer: Facilitates communication with external systems or services, such as payment gateways or third$-$party APIs.

Security Layer: Implements security measures to protect user data and system resources.

Design Principles:

Online banking system design will comply with the following principles:

$1.$ Modularity: Components will be modularly and loosely designed to facilitate maintenance and facilitate updates.

$2.$ Scalability: Architecture to accommodate increasing user load and transaction volume

It will support horizontal scaling.

$3.$ Maintainability: The code supports future enhancements and bug fixes.

It will be well structured and documented to make it easier.

$4.$ Security: Preventing unauthorized access, data breaches and other security threats

Robust security measures will be implemented. $5.$ Performance: Fast response times and speeds without compromising security or reliability

Improvements will be made for efficient resource use.

Deliveries:

Software Architecture Document: A document detailing the architecture of the online banking system will include architecture diagrams, component descriptions, and design decisions.

Presentation: A presentation slide set that summarizes key aspects of software architecture, including architectural patterns, design principles, and trading capabilities.

Design Products: Diagrams and models that describe the architecture in detail, such as UML diagrams $($e$.$g$.,$ class diagrams, sequence diagrams$),$ entity relationship diagrams $($ERDs$),$ and distribution diagrams.

Documentation: Documents supporting the architectural document will include explanations of key design decisions, justifications for selected architectural patterns, and guidelines for future development and maintenance.

make this project like report use tables to explain the project and use UML diagrams in the report $..$ I will give you images only as examples $..$