ATM REPORTING SYSTEM
ABSTRACT
The
project entitled "ATM Reporting System" has been developed using ASP.NET
and C#.Net as front end and SQL Server as back end.
The main objective of this
project is reporting application based on an existing client/database
application. The existing application
gathers all the transaction data from different ATM machine'’. The goal of the application is to allow
manager to view general reporting information through a web browser and not
require the installation of the client or exhaustive training.
The scope of this
application is 4 graphical reports, a security module. Which are ATM availability,
Transaction types and volume, on-us and not on-us transactions, Average withdrawal
amounts etc., the reports will primarily be accessing data in the transaction
log which contains most of the prevalent information for managers.
Project Description
The project is a web based reporting application. The existing
Application gathers all the transaction data from different ATM Machines. The
goal of the application is to allow managers to view General reporting information
of all ATMs through a web browser and not require the installation of a client
or exhaustive training. The web reporting application is being built in java. The
Backend database is oracle. The web application server is Apache Tomcat.
The scope of the application is four graphical reports, a
security
Module. The reports will primarily be accessing data in the
transaction
Log (which contains most of the prevalent information for
managers).
This
project has four modules
1.
ATM Availability
2.
Transaction type and volume
3.
On-us versus not on-us transactions
4.
Average withdrawal Amounts
1. ATM Availability
This report reflects ATM
uptime and reasons for any down
Time. Single ATM by region code.
Details:
This
report starts with standard selection criteria, as results, the
Report shows the user details.
Report Drilldown:
Step
1: choose area (system)
Step
2: choose date (year, month, week, day)
2. Transaction type and volume
Number and
percentages of different types of transaction performed at the ATM
details.
This report starts with standard
selection criteria, as results, the
Report shows details.
There are several transaction types
that need to be grouped
Together
3. On-us versus not on-us
transactions
Percentage of on-us versus off-us transaction
activity Number and percentage of on-us and foreign transactions
4. Average withdrawal Amounts
Lowest, highest and average amount of
withdrawal transactions
Details:
This
report starts with standard selection criteria. As a result the report
Outputs the average withdrawal amount
lowest withdrawal and highest
Withdrawal
SYSTEM ANALYSIS
2.1 Requirement analysis
The requirements
gathering process is intensified and focused specifically on software. To
understand the nature of the program to be built, the software engineer must
understand the information domain for the software, as well as required
function, behavior, performance, and interface. Requirements for both the
system and software are documented reviewed with the customer.
2.2 Manual System
The existing system has many drawbacks like maintaining records for all
Clients, online transactions are not possible, and manpower is required. It is more difficult by verifying all the
information and making reports for each and every transactions ,up and down
time details and the final reports which are going to be stored to their
transaction have to be kept secure and also generation of every report is very
difficult. The present system is a
manual work and is should require so much of manpower and it is very time consuming
process.
Time
Delay
Information
related to all transactions is stored in different tables. Since all the values are stored in different
tables, it takes a lot of time to prepare different reports and know the
information about that particular transaction.
Redundancy
As
the data passes through different tables it involves a lot of
Complication and duplication in manual
work, thus it causes redundancy.
Accuracy
Since data is compiled at different types
of transactions. If the data is more validation becomes difficult. This may result in loss of accuracy.
Reports
Various reports are tabulated manually.
They are not much attractive and require more time. Online enquiry of data is
not possible.
2.3 Proposed New system
Proposed system is entirely computer
based one. In this all data is entered
into computer and stored it allows to store large amount of data. Since the system is developed to provide
visual environment, it is very easy for the evaluator to get understand and
work on it. In this evaluator need not
bother about the common data entry mistakes as well as the common data fields
validated against pre-specified rules and regulations.
We can get any information about the
process at online Because of software capabilities reports can be generated
speedily and in attractive and desired manner.
The data security checks are made to prevent unauthorized access by
other users. The system is users friendly
by providing tree view controls, customized text boxes, combo boxes and other
options. Since database is fully
normalized, memory usage is very less compared to existing manual system.
Goals of New System
- To
reduce paper work.
- To save
time by getting faster results.
- The
reports needed by the officials for analysis and decision making
- Will be
readily available.
- To
avoid errors inherent in manual paper work.
- To
improve management of permanent and
updated information i.e.,
- Databases
by providing facilities to edit this information, manipulate it
- And
finally retrieve this information as efficiently as possible.
- To
provide tangible as well as intangible cost saving.
- Data updating
for time-by-time information is nicely retrievable.
No comments:
Post a Comment