Smart Banking CMS
Smart Banking CMS
Indosoft Technology
Address: 01st Floor, S. M. Tower, Above Jijamata
bank, Beside Dominos , Near Karvenagar Bus Stop,
Karve Nagar, Pune, Maharashtra 411052.
INDEX
INTRODUCTION
1. 1.1 Company Profile
1.2 Introduction
1.3 Existing System and Need for System
1.4 Limitations of existing system
7 Conclusion
8 Bibliography
9 ANNEXURES:
ANNEXURE 1 : USER INTERFACE SCREENS
ANNEXURE 2 : OUTPUT REPORTS WITH DATA ( if
any )
ANNEXURE 3 : SAMPLE PROGRAM CODE / Project
Demo( which will prove sufficient development is done by
the student )
1. INTRODUCTION
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
1. This interface integrates all existing banks and provides business solutions for
both retailers and corporate.
2. This system acts as a standard interface between the clients and the banks
3. Users who have accounts in various banks can login here and can make any
kind of transactions.
4. In the backend, system will take care of the entire obligation required in order
to carry on transaction smoothly.
This system provides the following facilities that other systems not
provide these facilities and hence this system is needed for following
facilities:
1. The Multi Banking System Interface is targeted to the future banking solution for
the users who is having multiple bank accounts in multiple banks.
2. This interface integrates all existing banks and provides business solutions for
both retail and corporate.
3. 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.
4. In the backend, system will take care of the entire obligation required in order to
carry on transaction smoothly.
2. PROPOSED 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 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.
Problem Statements
Problem No 1:
Problem No 2:
Problem No 3:
Problem No 4:
The impact of which Admin can‟t access data from different places
is when they want to access and it has a time
period limit.
Problem No 5:
Problem No 6:
Problem No 7:
For User
Website
Management
Reports Yes Yes Yes Yes
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.
2.4 A s su mp t io n s & D ep en de nc ie s
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.
2.5 Objectives
transfer money from his account to other accounts of same bank or other banks.
Transaction Reports: By using this functionality user can get all his transaction reports
like accepted transactions, rejected transactions and pending transactions.
4. Reports Module: In this module administrator will get different types of reports
regarding customers like Number of customers of this portal and no. of banks
registered in this portal. This module is controlled by administrator only.
1) Security:
2.12 Scope/Implementation
To provide flexibility to the users, the interfaces have been developed that are
accessible through a browser. The GUI‟S at the top level have been categorized as
After careful analysis the system has been identified to have the following modules:
1. Admin Module
2. Customer Module
3. Bank Admin Module
4. Reports Module
1. Admin Module:
The admin module will be used by the administrator of this portal, admin can accept or
reject the requests from the bankers, and also admin can accept or reject the requests from the
users. The requests are in the form of bank registration, customer registration. This module is
having following functionalities.
Pending Bankers Requests: By using this functionality Administrator can give access
permeations to all bankers who are registered in this portal.
Pending User Requests: By using this functionality Administrator can give access
permeations to all users who are registered in this portal.
2. Customer Module:
This module describes all about customers, by using this module any customer can do
some operations like create a new account, view the account information, Transfer amount
from one account to other account and customer can also see the Transaction Reports. This
module consists following functionalities.
Create New Account: By using this functionality user can create a new account in any
bank by selecting bank name option.
View Account Information: By using this functionality user view all his account
details, this can be viewed by users who are having account in any bank.
Transfer Amount: By using this functionality user can transfer money from his
account to other accounts of same bank or other banks.
Transaction Reports: By using this functionality user can get all his transaction
reports like accepted transactions, rejected transactions and pending transactions.
This module deals with all transactions of bank management. By using this module
bank staff can view all details of customers, they can go for any transactions of their
customers and also they can give access permeations to all customers of that bank. This
module consists following functionalities.
List of Customers: By using this functionality Bank admin can get their entire
customers list and their details.
List of Accounts: By using this functionality Bank admin can get their entire customers
list based on selected account type like saving account, current account etc.
Transfer Pending: By using this functionality Bank admin can maintain money
transfer details of customers.
Transfer Declines: By using this functionality Bank admin can maintain money
transfer rejected customer details.
New Accounts Pending: By using this functionality Bank admin can maintain entire
user details who are requesting for new account in that bank.
4. Reports Module:
In this module administrator will get different types of reports regarding customers
like Number of customers of this portal and no. of banks registered in this portal. This
module is controlled by administrator only.
To study any system the analyst needs to do collect facts and all relevant
information. the facts when expressed in quantitative form are termed as data. The
success of any project is depended upon the accuracy of available data. These specific
methods for finding information of the system are termed as fact finding techniques.
Interview, Questionnaire, Record View and Observations are the different fact finding
techniques used by the analyst. The analyst may use more than one technique for
investigation.
Record View:
The information related to the system is published in the sources like news
papers, magazines, journals, documents etc. This record review helps the analyst to
get valuable information about the system and the organization.
During the development of this system we goes through lots of documents and
record views and their formats. During the designs of the quotes, invoices and sales
orders we see the different type of quotes, invoices and sales orders. Whereas during
the report generation of all the quotes and invoices and sales orders we see the record
details of various organizations quotes and invoices entries. During the design and
working with contact management, lead management, opportunity management and
organizations management we goes through the lots of records of different
organizations and how they currently uses forms and what are the fields that are very
important during the design and working on campaigns , leads, organizations and
opportunities.
Observation:
Unlike the other fact finding techniques, in this method the analyst himself
visits the organization and observes and understand the flow of documents, working
of the existing system, the users of the system etc.
During the development of this system we observe the work flow of different
organizations and how their daily tasks are done. It is observed that how the
campaigns, leads and opportunities are related to each other.
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.
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.
Class Diagram:
Object Diagram
Sequence Diagram :
Activity Diagram
SATE DIAGRAMS:
Context Level
Admin:
Customer:
Bank Admin:
Money Transfer:
Context Diagram:
ERD- Diagram
Component Diagram
Deployment Diagram
Module Hierarchy
Menu Tree:-
Table Design
1. Admin
UserName VARCHAR(20) No - PK
Passsword VARCHAR(20) No - -
2. Customer
Null
Column Name Data Type Default Constraints
able
Number(10) No - -
Customer_Id
Cust_email VARCHAR(20) No - PK
Password VARCHAR(20) No - -
Name VARCHAR(20) No - -
Address VARCHAR(100) 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
Date No - FK
Transaction _Date
Trasaction_Amount VARCHAR(20) No -
T_Bank Number (10) No -
T_Reason Number (10) No - FK
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 - -
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 -
Quantity Number (10) No -
Date Date No -
Status VARCHAR(10) No -
7. Contact us
Id Number (20) No - PK
Name VARCHAR(20) No -
Email id VARCHAR(20) No - -
Subject VARCHAR(20) No -
Message VARCHAR(200) No -
Data Dictionary
DATA DICTIONARY
1 UserName VARCHAR(20) No - PK
2 Passsword VARCHAR(20) No - -
3 Id Number(10) No - -
4 Cust_email VARCHAR(20) No - PK
5 Password VARCHAR(20) No - -
6 Name VARCHAR(20) No - -
7 Address VARCHAR(100) No - -
12 BankAdmin_email VARCHAR(20) No - PK
13 Password VARCHAR(20) No - -
14 Name VARCHAR(20) No - -
23 Date Date No - -
24 Package VARCHAR(20) No - -
25 OPT Number (10) -
26 Id Number (10) No - PK
27 BankAdmin_email VARCHAR(20) No - FK
33 BankAdmin_email VARCHAR(20) No - FK
39 BankAdmin_email VARCHAR(20) No - FK
40 Password VARCHAR(20) No - -
42 Package VARCHAR(20) No - FK
43 Name VARCHAR(20) No -
44 Home VARCHAR(500) No - -
45 About VARCHAR(500) No -
46 Services VARCHAR(500) No -
47 Contact VARCHAR(500) No -
48 Sidebar VARCHAR(500) No -
49 Slider VARCHAR(10) No -
50 date Date No -
51 Id Number (20) No - PK
52 area VARCHAR(20) No - -
53 Id Number (20) No - PK
54 Main_cat VARCHAR(20) No -
55 Category VARCHAR(20) No - -
56 Id Number (20) No - PK
57 Pk_name VARCHAR(20) No - -
61 Name VARCHAR(20) No -
62 Email id VARCHAR(20) No -
63 Package VARCHAR(20) No - FK
64 Mobile no VARCHAR(13) No -
65 Path VARCHAR(20) No -
66 Date Date No -
67 Id Number (20) No - PK
68 Name VARCHAR(20) No -
69 Email id VARCHAR(20) No -
70 Package VARCHAR(20) No - FK
71 Mobile no VARCHAR(13) No -
72 Path VARCHAR(20) No -
73 Date Date No -
74 Id Number (20) No - PK
75 Name VARCHAR(20) No -
76 Email id VARCHAR(20) No -
77 Title VARCHAR(20) No -
78 Mobile no VARCHAR(13) No -
79 Package VARCHAR(20) No - FK
80 Category VARCHAR(200) No -
81 Info VARCHAR(500) No -
82 Date Date No -
83 Image VARCHAR(20) No -
84 Id Number (20) No - PK
85 Cust_email VARCHAR(20) No - FK
86 BankAdmin_email VARCHAR(20) No - FK
87 Quotation_file VARCHAR(20) No -
88 Date Date No -
89 Status VARCHAR(10) No -
90 Id Number (20) No - PK
91 Cust_email VARCHAR(20) No - FK
92 Name VARCHAR(20) No -
93 Area VARCHAR(20) No -
94 Category Date No -
95 Address VARCHAR(100) No -
96 Requirement VARCHAR(200) No -
97 Quantity Number (10) No -
98 Date Date No -
99 Status VARCHAR(10) No -
100 Id Number (20) No - PK
4.3 Testing
1. Unit Testing
Unit testing concentrates verification on the smallest element of the program – the
module. Using the detailed design description important control paths are tested to
establish errors within the bounds of the module.
In this system each sub module is tested individually as per the unit testing such as
campaign, lead, contact etc are tested individually. Their input field validations are tested.
2. Integration testing
Once all the individual units have been tested there is a need to test how they were put
together to ensure no data is lost across interface, one module does not have an adverse
impact on another and a function is not performed correctly.
After unit testing each and every sub module is tested with integrating each other.
In this level of testing we are testing the system as a whole after integrating all the
main modules of the project. We are testing whether system is giving correct output or not.
All the modules were integrated and the flow of information among different modules was
checked. It was also checked that whether the flow of data is as per the requirements or not.
It was also checked that whether any particular module is non-functioning or not i.e. once
the integration is over each and every module is functioning in its entirety or not.
Test Cases
Test cases are built around specifications and requirements, i.e., what the application is
supposed to do. Test cases are generally derived from external descriptions of the software,
including specifications, requirements and design parameters. Although the tests used are
primarily functional in nature, non-functional tests may also be used. The test designer selects
both valid and invalid inputs and determines the correct output without any knowledge of the
test object's internal structure.
Equivalence partitioning
Boundary value analysis
Cause–effect graph
Error guessing
Advantages
Disadvantages
Test cases are challenging to design without having clear functional specifications.
It is difficult to identify tricky inputs if the test cases are not developed based on
specifications.
It is difficult to identify all possible inputs in limited testing time. As a result, writing
test cases may be slow and difficult.
There are chances of having unidentified paths during the testing process.
There is a high probability of repeating tests already performed by the programmer.
Modules to be tested:-Registration
Module-ID:-2
1. Enter the correct username and wrong password click on Submit button.
2. Enter the wrong username and correct password and click on Submit button.
3. Enter the correct username and password and click on Login button.
5. After login with valid credentials copy the URL and paste in another browser.