anumoluvasavi@gmail.

com

9290846883 SYSTEM DESIGN

1. Introduction
System design is a process of dividing the system into sub systems. During the
system design, developers define the goals of project and decompose the system into
smaller subsystems that can be realized by individual teams. Developers also the
selecting strategies for building the system , such as the hardware/soft ware platform on
which the system will run the persistent data management strategy, the global control
flow ,the access control policy and the handling of boundary conditions . The resulted of
system design is a clear description of each of these strategies, a sub system
decomposition, and deployment diagram representing the hardware/ software mapping of
the system.

Purpose:
To main purpose of the system design is to identify the components of the system
and integration among the components. Apart from identifying the components database
design was also most important of the system design phase. In this phase identification of
components and respective modules and integration among the modules was identified.
Both in the low level design and high level design all the diagrams were drafted clearly
so that these documents form the base for the coding phase.

The main purpose of the multi banking system is to provide the single interface to the
user to access all the banks accounts. Main purpose in this phase is to identify the
modules accurately so that the interface is developed properly.

Design goal:
The main goal in system design is to develop the logical and physical design
documents. The design was carried out so accurately that it became a basement for the
coding phase.
2. Current system s/w architecture or survey of current architecture
The architecture used in the current system is the client server architecture as
the communication is among the users and the government personnel. Customers will not
be able to login into the system. Only the employees of the system will be able to login
into the system to update the schemes information. This architecture follows a standalone
application where every employee will have the application and they have to use the
system without any relation with other systems.

3. Proposed S/w architecture

The architecture used in the proposed system is the distributed client server
architecture as the communication is among the server and the multiple clients residing
across the different places. Due the distribution in architecture any client can
communicate with server without any hassles. Also there will not be any delays as it is
implemented in the servlets and jsps. More over security for the project is very high as
the complete information will be placed or deployed in the database.

Overview:
 To propose multiple accesses to the banking services through a single website.
 Provide a flexible interface to the user.
 Provide a dynamic interface and mechanism for the user to work with
the multiple accounts with the multiple banks.
 To reduce time while accessing the accounts.
 To provide high level of security.

Subsystem decomposition:
Modules

1. Scheme Management Module.

2. Panchayat management Module.

3. Administration Module.

4. Reporting

Module Description
Number of Modules

The system after careful analysis has been identified to present itself with the
following modules:

 Scheme Management Module: This module provides user interface to

add, edit, and delete various government schemes. This module takes
care of accepting various applications from users and escalating those
applications to DDO for approval. In scheme management module
available schemes list and eligibility criteria for corresponding schemes
details will be displayed in schemes list.
Eligibility details, how many members are already applied for the schemes
all these details will be displayed. Only the admin user can add the details
of users for the related schemes. He only the user to update or delete the
details of users from schemes list. All the remaining users can view the
details of schemes.

 Panchayat Management Module: This module provides facility to add

or delete or edit various panchayats. Also provides interface to view the
status of applications at panchayat level. Provides an interface to
accept/reject applications at panchayat level it self. In panchayat
management module all the available panchayaties will be displayed in
panchayaties list. Every panchayat has its own ID. This list contains
details of all the panchayaties means panchayat ID, Name, district ID,
name of the GPO, population of the corresponding panchayat, how many
literates and illiterates are living there in that panchayat, how many
families are living with BPL(Below Poverty Line), their occupation all these
details will be included. Only the admin user can add the new
panchayaties. He is only the user to update or delete the panchayaties
from the list. Remaining users can view the details of all the panchayaties.

 Administration module: This module provides administrators to

add/remove users and assign various access rights to them. This module
 contains all the adding and removing functions. This module contains all
the users details, panchayaties details, schemes details, and district
details. The administrator can add / update or remove any of the above
functions. The administration module having authority to add or update
the details of all the above mentioned functions. This module maintains all
the departments. Each and every user should be created by administrator.
He can maintain all the departments. Applications of the eligible users and
available schemes will be added by administrator. All the users details and
every department details will be available only in administration module.

Reporting module: In this module we can see various types of reports

like scheme wise report, panchayat wise report, and user wise report.
Various reports like Approved applications, Pending applications and
Rejected applications at different levels panchayat wise as well as user
wise. Name of the scheme, eligibility for the scheme and maximum
strength of the scheme all these details will be included in scheme wise
report. Name of the panchayat and in which district it will be located all
the details will be added in panchayat wise report. Application ID, name of
the applicant, scheme ID, panchayat ID, status of the application all these
details will be included in user wise applications report. Status of the
application and any remarks information will be displayed in approved
applications report. All the rejected applications report will be placed in
the rejected applications report.

Component Diagram

H/w, S/w mapping

Hardware:

PROCESSOR : PENTIUM IV 2.6 GHz

 RAM : 512 MB DD RAM

MONITOR : 15” COLOR

HARD DISK : 20 GB

FLOPPY DRIVE : 1.44 MB

CDDRIVE : LG 52X

KEYBOARD : STANDARD 102 KEYS

MOUSE : 3 BUTTONS

Software:

FRONT END : Java, Swing

Tools Used : JFrameBuilder

Operating System : Windows-XP

Persistent data management

As it is a web based project data from the users is retrieved and stored in the
database. All the data is maintained and stored in the database for the future retrieval.
Since it is a financial project persistent storage of data is very important.

Access control & security

Proposed system is highly secured and no changes can be made to the database
without proper authentication. As the project cannot be accessed by the normal users
there is very less scope for creeping of errors in the system. More over system is
maintained by the administrator who will provide high security to the system and does
not allow access to the normal users without proper authorization.

4. Subsystem services (Modules)

Performance of the proposed system is judged based on the display of
the information about the user accounts and the functionalities allowed to
work on the system. If the information provided by the account is true then
the performance of the proposed system is high as with that of the existing
system.

SubModules
Sub modules functionality

Module Diagram

Admin

Receives
request
Admin from
Clients.

Customer

Sends the Received by the

Customer Request Admin

Request received by
bank admin
 Process the request and
send to customer

Report Generation

Admin Generate
Reports.

Customer Generate
Reports.

Bank Admin Generate

Reports.