Multibanking System. About Project
Multibanking System. About Project
About project:-
Multi Banking System
The Multi Banking System Interface is targeted to the future banking solution for the users
who is having multiple bank accounts in multiple banks. This interface integrates all
existing banks and provides business solutions for both retail and corporate.
This system acts as a standard interface between the clients and all the banks, By using
this portal any client who maintain accounts in various banks can directly log on to Multi
Banking System Interface and make any kind of transactions. In the backend, system will
take care of the entire obligation required in order to carry on transaction smoothly.
The ‘Multi Banking System’ Interface is targeted to the future banking solution for the users
who have multiple bank accounts in different banks. This interface integrates all existing
banks and provides business solutions for both retail and corporate. System Involves
• This interface integrates all existing banks and provides business solutions for both
retailers and corporate.
• This system acts as a standard interface between the clients and the banks
• Users who have accounts in various banks can login here and can make any kind of
transactions.
• In the backend, system will take care of the entire obligation required in order to carry on
transaction smoothly.
Feasibility Study: -
While developing any computerized system it is necessary to examine whether the
developed computerized system is feasible in the point of view operational, technical and
financial.
Requirement analysis take place can be combined into a feasibility analysis and a
business proposal is put forth. With a very general plan for the project and some cost
estimates. For feasibility analysis, some understanding of the major requirements of the
system is essential.
The cases are categorized as follows:
1. Operational Feasibility
2. Technical Feasibility
3. Economic Feasibility
Operational Feasibility
Training program will be required to the user. A group of user will be trained during
the training period. It focuses on the willingness and the ability of the user. PES website
does not require special efforts to educate the staff on new way on conducting ways. The
system incorporates user friendly interface, default processing and required validations.
These all are done keeping in view the individual with minimum computer knowledge.
This system is operationally feasible because the user interface provided is very user
friendly and normal user can easily understand it and can perform all the operations easily.
Technical Feasibility
Technical feasibility is the study of cost benefit analysis of the system and study of
the hardware and software requirements i.e. technical requirements of the system in order
to inform management and user for particular system designing this much technical sources
are required, in order to know user and management view, regarding the technical resources.
By studying the technical study the actual cost of the system designing is known.
Organization can provide the minimum required as specified in operational environment.
This system is technically feasible because the java, struts 2.0 is used in the system
and hence it is a very secure system. The required operational environment is very cheap
and it is open source. The development tools and libraries are available for free so it is
technically more feasible.
Economical feasibility
Economical feasibility study is the actual cost and benefit of the system. Actual cost
of the system is calculated in the economic study so as to inform the user and management
that this much cost will be required to develop the system. Because system cost is the first
cost before starting system designing.
The organization is ready to invest on hardware and software required by the
proposed system. So system is economically feasible.
This system is also economically feasible because all the development resources are
open source and are available for free. So it requires the less amount for development and
implementation.
Use Case Diagrams
1) Admin
Table Design
1. Admin
UserName VARCHAR(20) No - PK
Passsword VARCHAR(20) No - -
2. Customer
Null
Column Name Data Type Default Constraints
able
Customer_Id Number(10) No - -
Cust_email VARCHAR(20) No - PK
Password VARCHAR(20) No - -
Name VARCHAR(20) No - -
Address VARCHAR(100) No - -
Status VARCHAR(10) No - -
1. Customer Bank
Null
Column Name Data Type Default Constraints
able
CustomerBank_Id Number(10) No - -
BankName VARCHAR(20) No - PK
IFSC-Code VARCHAR(20) No - -
BankAddress VARCHAR(20) No - -
BankEmail VARCHAR(100) No - -
BankContactNumber VARCHAR(13) No - -
2. Transaction
Id Number (10) No - PK
Transaction Date No - FK
_Date
Trasaction_Amount VARCHAR(20) No -
Date Date No -
3. Bank Admin
Null
Column Name Data Type Default Constraints
able
Id Number (10) No - PK
BA_Name VARCHAR(20) No - FK
Password VARCHAR(20) No - -
Bank_Address VARCHAR(20) No - -
ContactNumber VARCHAR(20) No -
Date Date No -
1. Website
Null
Column Name Data Type Default Constraints
able
Id Number (10) No - PK
Customer_email VARCHAR(20) No - FK
Password VARCHAR(20) No - -
Package VARCHAR(20) No - FK
Name VARCHAR(20) No -
Home VARCHAR(500) No - -
About VARCHAR(500) No -
Services VARCHAR(500) No -
Contact VARCHAR(500) No -
Sidebar VARCHAR(500) No -
Slider VARCHAR(10) No -
Date Date No -
2. Add Category
Id Number (20) No - PK
Main_cat VARCHAR(20) No -
Category VARCHAR(20) No - -
3. Package
Id Number (20) No - PK
Pk_name VARCHAR(20) No - -
Duration VARCHAR(20) No -
4. Add slider
Id Number (20) No - PK
Name VARCHAR(20) No -
Email id VARCHAR(20) No -
Package VARCHAR(20) No - FK
Mobile no VARCHAR(13) No -
Path VARCHAR(20) No -
Date Date No -
5. Product Advertisement
Id Number (20) No - PK
Name VARCHAR(20) No -
Email id VARCHAR(20) No -
Title VARCHAR(20) No -
Mobile no VARCHAR(13) No -
Package VARCHAR(20) No - FK
Category VARCHAR(200) No -
Info VARCHAR(500) No -
Date Date No -
Image VARCHAR(20) No -
6.Send requirement
Id Number (20) No - PK
Cust_email VARCHAR(20) No - FK
Name VARCHAR(20) No -
Area VARCHAR(20) No -
Category Date No -
Address VARCHAR(100) No -
Requirement VARCHAR(200) No -
Date Date No -
Status VARCHAR(10) No -
7.Contact us
Column Name Data Type Null able Default Constraints
Id Number (20) No - PK
Name VARCHAR(20) No -
Email id VARCHAR(20) No - -
Subject VARCHAR(20) No -
Message VARCHAR(200) No -
Module Design:-
Login.
Add / Manage Beneficiaries.
Transfer Type.
Search IFSC.
Added Transfer Type Detail.