Branch Bank Operation Project Report - DOC

Report as inappropriate Your report has been received

Description

Branch Bank Operation Project Report document sample

Shared by: zoi85216

Tags

interest rate, credit card, bad credit, how to, payday loans, payday loan, credit score, mortgage loan, Home Loans, Mortgage Rates

Stats

views:: 426
posted:: 1/7/2011
language:: English
pages:: 85

Public Domain

Document Sample

PROJECT REPORT
ON
“WEB- BASED REVENUE ACCOUNTING SYSTEM
FOR PAY AND ACCOUNT OFFICE”

Project Undertaken at Central Excise Department

National Informatics Centre - HQ, NEW DELHI- 110001

Submitted To

Jorhat Engineering College, Jorhat
Dibrugarh University, Assam
For the Partial Fulfillment of the Degree
Master of Computer Application

UNDER THE GUIDENCE OF

Mr. Chander Prakash
Technical Director
FFRIG division
National Informatics Centre
New Delhi-110003

SUBMITTED BY

Borsha Bordoloi
MCA Sixth Semester
Roll No. – 203/05
National Informatics Center

GOVERNMENT OF INDIA

MINISTRY OF COMMUNICATIONS & INFORMATION TECHNOLOGY

DEPARTMENT OF INFORMATION TECHNOLOGY
National Informatics Centre HQ

This is to certify that Miss Borsha Bordoloi. ID.N0-10034, a student of MCA from
Jorhat Engineering College has done her full-semester project training at Fiscal and
Financial Resources Informatics Group (FFRIG), National Informatics Centre HQ, New
Delhi, from July 2007 to November 2007.

The project work entitled Web-Based “Revenue Account System” for the office of
Principle Chief Controller of Accounts; CBEC embodies the original work done by her
during her above full semester project training period.

Project Guide/ HOD Head, Training Division

Project Report Revenue Accounting System
National Informatics Center

Jorhat Engineering College
Department of Master of Computer Application
Jorhat-7, Assam

This is to certify that Miss Borsha Bordoloi, a student of 6th
semester, Master of Computer Application, Jorhat Engineering
College, Jorhat has carried out the project “Revenue Accounting
System “ for the office of Principle Chief Controller of Accounts; CBEC

This project work has been prepared as a partial fulfillment of the
requirement for the degree of Master of Computer Application to be
awarded by Dibrugarh University. This work has not been presented
earlier for any other academic activity.

I wish her all success in life.

Signature of Examiners: Signature of the
H.O.D

1. (Siddhartha
Baruah)
Head of the Department
Department of MCA
Jorhat Engineering College,
Jorhat-785007

Project Report Revenue Accounting System
National Informatics Center

DECLARATION

I do, hereby declare that the dissertation entitled “Revenue
Accounting System” for the office of Principle Chief Controller of Accounts,
CBEC is an authentic work developed by me at “National Informatics Centre
HQ, New Delhi” under the guidance of Mr. Chander Prakash (Technical
Director, NIC HQ) and submitted as partial fulfillment of the requirement for
the award of degree of MCA.

I also declare that, any or all contents incorporated in this dissertation
have not been submitted in any form for the award of any degree or diploma
of any other institution or university.

Borsha Bordoloi
Master of computer Application
Roll No -203/05

Project Report Revenue Accounting System
National Informatics Center

Dept. of MCA
Jorhat Engineering College
Abstract

Project Title: Revenue Accounting System

The Project entitled web based “Revenue Accounting System (REVACT)” is basically a software
package for the Revenue Accounting of Central Excise and Service Tax at Pay and Accounts Office of
each Commissionerate. All Assessees pay excise duty/service tax in a nominated public sector bank
through a challan called TR-6 challan in four copies. The bank retains two copies including the
original copy and the other two copies are given back to the Asseesees. The bank sends the original
copy of challans along with its scroll to the Pay and Accounts office (PAO) of Customs and Central
Excise Commissionerates on a daily basis. At the same time the bank also transfers the duty to the
head of account of Government of India. To process all these challans and to ensure proper revenue
receipt accounting, the RevAct package has been developed and implemented at all commissionerates
in India .RevAct does the exact validation between challans and scroll for ensuring the receipt of
revenue. It has improved the Accounting System of the Department. Compilation of monthly
accounting and submission of revenue collection figures to CBEC is done through this package.

Keywords: Assessee, CBEC, Focal point bank, Branch Bank, Commissionerate, Challan, PAO

NIC Division: FFRIG (Central Excise division)
Name of Student Trainee with Id: Borsha Bordoloi. ID-10034

Project Report Revenue Accounting System
National Informatics Center

TABLE OF CONTENT
1. About NIC
2. About the project
2.1 Project title
2.2 Problem Defination
2.3 Existing System
2.4 Proposed System
2.5 Project Description
2.5.1 Introduction
2.5.2 Objective
2.5.3 Methodology/Scope
2.5.4 Features
3. Technology Used
4. Project plan and risk analysis
4.1 Project planning
4.2 Project scope
4.3 Feasibility study
4.3.1 Economic Feasibility
4.3.2 Technical Feasibility
4.3.3 Behavioral Feasibility
4.4 Resources
4.5 Project schedule
4.6 Risk analysis
5. System requirements
5.1 Software requirements

Project Report Revenue Accounting System
National Informatics Center

5.2 Hardware requirements
6. System Design
6.1 Introduction
6.2 Design Consideration
6.3 Assumptions
6.4 General Constraints
6.5 Development method
6.6 Architecture
6.7 Coding
6.9 Detailed System Design
6.9.1 Data Flow diagram
7. Testing
7.1 Introduction
7.2 Testing objective
7.3 Test plan
7.4 Text case design
7.5 Testing requirements and acceptance criteria
8. Maintenance
8.1 Cost Estimation
9. Data Directory
9.1 E-R Diagram
10. Screen Shots
11. Conclusion
12. Bibliography

Project Report Revenue Accounting System
National Informatics Center

ACKNOWLEDGEMENT

I sincerely take this opportunity to express my thanks and deep gratitude to all those who
extended their wholehearted cooperation, opinion and gracious hospitality to me in completing this
project successfully.
I would like to acknowledge my gratitude towards Mr. Siddhartha Baruah (H.O.D. MCA
Dept.) my internal guide at Jorhat Engineering College, Jorhat under Dibrugarh University, Dibrugarh,
Assam, for his understanding, provision of sound counsel and valuable guidance.
In all my humbleness, I express my gratitude to Mr.O.P.Sachdeva, Senior Technical
Director, NIC HQ for his guidance, support and useful suggestions; He gave me the opportunity to
carry out this project work and helped me with their suggestions, ideas and advice at every phase of
this project work. Their guidance has always been a source of inspiration.
I also express my thanks to Mr.Chander Prakash, Technical Director, NIC who rendered
me his invaluable help, suggestions and encouragements with patience and constant guidance.
I also want to thank my project team members for all their support and cooperation.
I owe my in-depth gratitude to the staff of Central Excise Department, NIC, for providing me
their full support and cooperation during my work.
Finally, I wish to thanks to my parents and friends without whom I would not have been able to
make out this place.

New Delhi Borsha Bordoloi

Project Report Revenue Accounting System
National Informatics Center

PREFACE

Web based REVACT (Revenue Accounting System) is a software package for the Revenue
Accounting of Central Excise and Service Tax at Pay and Accounts Office of central excise and
service tax Commissionerate.

It has been developed under Windows Environment using JSP. This package is to be used at Pay
and Accounts Office (PAO) of each Commissionerate. Though the package is self-contained, it is felt
that this manual will help the user in getting acquainted with the software.

It takes care of revenue accounting of more than one Commissionerate. The development work
has been carried out at NIC Head Quarters with the active cooperation of officials from the 'Office of
the Principal Chief Controller of Accounts‟, Central Board of Excise and Customs, New Delhi.

Project Report Revenue Accounting System
National Informatics Center

ABOUT
NATIONAL INFORMATICS CENTRE

Project Report Revenue Accounting System
National Informatics Center

1. ABOUT NIC

INTRODUCTION

National Informatics Center (NIC) is a premier Information Technology organization in India
committed to providing state-of-the-art solutions for the IT needs of the Government of India at all
levels.
NIC carries the distinction of being the largest IT Organization in the country and has set up a
satellite based nationwide computer communication network called NICNET having over 1400 nodes
connecting the National Capital, the State Capitals and the District Headquarters to one another. NIC
has a nationwide presence with its offices spread all across the country, from Leh to Andaman &
Nicobar Islands.
NIC computer cells are located in almost all the Ministries Bhawans of the Central Government and
Apex Offices including the Prime Minister‟s Office, the Rashtrapati Bhawan and the Parliament
House. Apart from this, NIC has various Resource Divisions at the Headquarters, which specialize into
different areas of IT and facilitate the Application Divisions as well as other NIC Centers in providing
state of-the-art services to the Government. At the State level, NIC State Centers provide informatics
support to their respective State Government and at the district level laid.

About National Informatics Centre (NIC)

National Informatics Centre (NIC) of the Department of Information Technology is providing
network backbone and e-Governance support to Central Government, State Governments, UT
Administrations, Districts and other Government bodies. It offers a wide range of ICT services
including Nationwide Communication Network for decentralized planning, improvement in
Government services and wider transparency of national and local Governments. NIC assists in
implementing Information Technology Projects, in close collaboration with Central and State
Governments, in the areas of (a) Centrally sponsored schemes and Central sector schemes, (b) State
sector and State sponsored projects, and (c) District Administration sponsored projects. NIC endeavors
to ensure that the latest technology in all areas of IT is available to its users.
NIC Headquarters is based in New Delhi. At NIC Headquarters, a large number of Application
Divisions exist which provide total Informatics Support to the Ministries and Departments of the
Central Government. NIC computer cells are located in almost all the Ministry Bhawans of the Central

Project Report Revenue Accounting System
National Informatics Center

Government and Apex Offices including the Prime Minister‟s Office, the Rashtrapati Bhawan and the
Parliament House. Apart from this, NIC has various Resource Divisions at the Headquarters which
specialize into different areas of IT and facilitate the Application Divisions as well as other NIC
Centers in providing state-of-the-art services to the Govt.
At the State level, NICs State/UTs Units provide informatics support to their respective State
Government and at the District level lie the NIC District Informatics Offices.
NIC has conceptualized, developed and implemented a very large number of projects for various
Central and State Government Ministries, Departments and Organizations. Many of these projects are
continuing projects being carried out by various divisions of NIC at New Delhi Headquarters and
State/District centers throughout the country. Some of the most important note worthy projects, which
offer a glimpse of the multifaceted, diverse activities of NIC, touching upon all spheres of e-
governance and thereby influencing the lives of millions of citizens of India is given below:

 Agricultural Marketing Information Network (AGMARKNET)
 Central Passport System
 Community Information Centers (CICs)
 Computerized Rural Information Systems Project (CRISP)
 Court Information System (COURTIS)
 Department of Agriculture Network (DACNET)
 Examination Results Portal
 India Image
 Land Records Information System (LRIS)
 National Hazardous Waste Information System (NHWIS)
 Public Grievance Redress and Monitoring System (PGRAMS)
 Spatial Data Infrastructure (SDI)
 Training
 Video Conferencing
 Web Site of NIC http://indiaimage.nic.in

Project Report Revenue Accounting System
National Informatics Center

ABOUT THE PROJECT

Project Report Revenue Accounting System
National Informatics Center

2. INTRODUCTION

2.1 PROJECT TITLE

The project is title as “WEB- BASED REVACT” (Revenue Accounting System for Pay and
Accounts Officers of Central Excise Commissionerate)

2.2 PROBLEM DEFINITION

Existing REVACT package developed in VB – MS Access environment installed at each PAO which
is working in offline mode. Whenever changes takes place in the software, each time PAO are
required to download and installed the modified software/ Patch. In addition to that recently office of
Principle Chief Controller of Accounts has installed multi-protocol level switching based on Virtual
Private Network. So, there was a need to develop a suitable revenue accounting package using Web-
based technology.

2.3 LIMITATION OF EXISTING SYSTEM

The existing system is offline, manual and time consuming and requires greater coordination among
the various people involved in the work. As it is known land record information are quit vast,
complicated and valuable; any error in the information can lead to disputer and problems for the
government and people (who owns the lands). So proper authentication of all the data is must and also
the modification of data should be restricted to only a few selected officials, and it should be secure
enough so that no unauthorized user can make any changes and also it is important to ensure that some
official making some changes to record information cannot deny it. The current manual system is not
being able to meet these requirements. In the existing system age- old method of taking specimen
signature of the official and putting a stamp on the document is maintained, which can be faked easily
and also after a document is given that document can also be modified by current technologies easily.
Also there is no method to keep proof of who did modification to the data; an official whom did some
modification to the existing data can easily deny it.It was developed using visual basic.

Project Report Revenue Accounting System
National Informatics Center

2.4 PROPOSED SYSTEM
The existing REVACT package is an offline package and each PAO sends data pertaining to their
jurisdiction manually.
The proposed system is based on client-server architecture.Challan data of all PAO will store in
the central server. Thus the all India challan and scroll data is available for other modules like
centralized delay monitoring module (CDMM).
In the proposed we will integrate security features in the already existed “REVACT” application.
This System will allow only the authorized person knowing its “Pass phrase” can login .It is a web
based system which is developed using jsp. e-REVACT is a much improved package over the existing
one and generates qualitatively better reports in areas of delayed remittances, Bank Reconciliation for
Refunds & Drawbacks transactions, Budget Head wise reports, Revenue Reconciliation facility etc.
Separate option for entering the data relating to Customs Duty has also been developed so that this
package is capable of accounting in all the revenue receipt heads of CBEC i.e. Customs Duty, Central
Excise Duty, Service Tax, Foreign Travel Tax etc.

2.5 PROJECT DESCRIPTION

E-REVACT

INTRODUCTION:

E-REVACT (Revenue Accounting System) is a software package for the Revenue Accounting of
Central Excise, Customs, Service Tax and Foreign Travel Tax etc. at Pay and Accounts Office of each
Commissionerate. It has been developed under Windows Environment using jsp. This package is to
be used at Pay and Accounts Office (PAO) of each Commissionerate. Though the package is self-
contained, it is felt that this manual will help the user in getting acquainted with the software. It takes
care of revenue accounting of more than one Commissionerate. The development work has been
carried out at NIC Head Quarters with the active cooperation of officials from the 'Office of the
Principal Chief Controller of Accounts‟, Central Board of Excise and Customs, New Delhi.

Project Report Revenue Accounting System
National Informatics Center

METHODOLOGY / SCOPE:

Windows Xp has been chosen as the server platform. IT uses a visual-based client application
which provides interface for application acceptance and upload data to the server at State Head
Quarters. The Application Processing Centers are in charge of updating the status of application
through a web-based interface.
The Central Board of Excise & Customs (CBEC), under the Department Of Revenue administers
indirect taxes through the Central Excise Commissionerate & Customs Commissionerates. The CBEC
also controls the Narcotics wing comprising of the Narcotics Commissioner and the two Govt. Opium
and Alkaloid Factories under the Chief Controller of Govt. Opium and Alkaloid Factories.
The Commissionerates are entrusted with the task of collection of revenue by way of duties,
cesses and other charges such as fines, penalties, sales proceeds of narcotic products etc. as well as
payment of refunds, rebates and drawbacks on export of goods etc. They are also responsible for the
collection of service tax.
The Central Excise Commissionerates mainly deal with the recovery of central excise duties
and cess from the manufacturers of various types of goods (known as assesses). They are also
responsible for the collection of customs duties at minor ports in their jurisdiction.
Central Excise Duty
Central Excise duties form the single largest source of revenue for the Govt. of India. Every
Manufacturer of excisable goods is required to pay Central Excise duty on the product that he
manufactures.
Service Tax
It is an indirect tax imposed on service provider for the services rendered to the customer. Initially,
service tax was only imposed on
(I) Service rendered by the telegraph authorities to the subscribers in relation to telephone
connections.
(II) Service provided by the insurer to the policy holder in relation to General insurance business and
Services provided by stock broker.
Over the years, following other services have also come under tax net such as.
 Goods transport operators
 Customs House Agents

Project Report Revenue Accounting System
National Informatics Center

 Consultant Engineers
 Air travel agents
 Clearing and forwarding agents etc
Central Excise Officers, all over the country are authorised to conduct surveys to bring the prospective
service tax assesses under the tax net.
At present Challan forms in distinguishing colours are used for each Major Head of Accounts.
The Service Tax deposited in Public Sector Banks is also done by filling TR-6 Challan forms.
(Yellow Colour) to collect tax under Major Head of Account “0044”. All Agencies/Departments who
are authorised to collect the Service Tax have to use Yellow Coloured TR-6 challans for depositing the
Service Tax in the Bank.
Receipts of Customs, Central Excise duties and Service Tax
Receipts of Customs, Central Excise duties and Service Tax under the major head of account
“0037-Custom duties", "0038-Union Excise duties” and “0044-Service Tax” respectively are collected
as follows:
By cash payment to the departmental officer against issue of receipt.
ii) By adjustment through the Personal Ledger Account maintained by the Chief Accounts Officer
of the Commissionerate concerned wherein the amounts are credited by the assesses periodically
through the prescribed Challan.
iii) By cash/cheque/draft along with prescribed Challan.
Role of Public Sector Banks in Revenue Collection
With effect from 1.4.1986 (under one bank - one Commissionerate scheme) payments of dues
and charges under the Major Heads relating to Central Excise, Customs, Gold Control and other allied
heads, except those on account of customs duties and other charges pertaining to the Commissionerate
of Customs at the Major Ports, are to be made. Only in the branches of the public sector bank selected
for the Commissionerate, by means of cash/cheque or draft along with a Challan form TR-6.
Receiving Branch of Bank
The receiving branch forwards the Scrolls and Challans to its focal point branch at the
headquarters of the Commissionerate at the beginning of the next working day through courier
system/registered post.

Project Report Revenue Accounting System
National Informatics Center

Focal Point Branch of Bank
The focal point branch, in addition to acting as a receiving branch, is responsible for prompt
and accurate accounting of the collections reported to it daily by all the receiving branches under the
jurisdiction of the Commissionerate (including its own receipts). The receipts of the entire
Commissionerate will be accounted for through the single focal point branch. The focal point branch
includes the scrolls received from the receiving branches and its own transactions related to the
Commissionerate in its daily main scrolls. These are to be prepared in triplicate and send the original
and duplicate copies of the main scrolls to the PAO of the Commissionerate daily. The original scrolls
and challans received from all the receiving branches are also to be sent on daily basis.
The PAO checks the copies of main scrolls and the supporting documents and certifies and
returns the duplicate copies of the main scrolls to the focal point branch. The PAO books the receipt
figures in his account with reference to the original Challans received with the main scroll and debits
"PSB Suspense".
Delay in Remittances
The RBI allows 5 or 9 days (including holidays) for local branches and other outstation
branches respectively from the date of receipt of the dues/duties etc. at the collecting branches within
which the collection should be passed on to the RBI, Central Accounts Section, Nagpur. The
remittance of collection beyond the said period is treated as delayed remittance.
Revenue Collection Procedure
The Assessee deposits excise duties along with the challan in specified format at the receiving
Branch Bank in his Range/Division. The Branch Bank prepares a scroll of deposits on a particular date
and sends it along with Challans to the Focal Point Bank assigned to it. The Focal Point Bank prepares
a scroll of its own on the basis of scrolls received from receiving Branch Banks and sends it along with
a copy of Challans and Branch Bank scrolls to the PAO of Central Excise Commissionerate. From this
information, statements of Total Revenue Collection and Minor head-wise Revenue Collection are
prepared.
Each division prepares the list of payment cheque issued to Assessee for Refunds/Drawbacks
and renders the same list to the Pay and Accounts Office (PAO) on a daily basis. These cheques are
drawn on the selected branch of the Nominated Bank selected for purpose of Refunds/Drawbacks in
the divisions of the Commissionerate.

Project Report Revenue Accounting System
National Informatics Center

Focal Point Bank receives the payment of the Refund Scroll from paying branches and
prepares its own Payment Scroll and sends it to the PAO of the Commissionerate.
A list of outstanding cheque, encased cheques are maintained in a separate file to keep track of
accounts as all the cheques issued by the Division in a particular month may not be enchased by the
Assessee within the same month.

MAIN FEATURES:

The advantages and benfits of the REVACT Software are:
 All the modules have been incorporated as a single integrated module which will avoid
memory problem.
 More user level security to the application and database.
 Master details relationship enforced in database reflected in the forms also.
 Online help is available.
 Security at application level.
 Same application can work in internet, intranet and stand- alone mode.
 Database independent.
 Software supports both old and new Assessee codes (i.e. 10 digits and 15 digits).
 Report procedure has been standardized to generate reports for any given accounting month.
 The application can work as a stand alone as well as Client/Server architecture mode in LAN
environment in the PAO.
 The raw data (for a considerable period of time) is available on the server and the reports for
any period can be generated at any given time.
 The package generates the following reports:
 Commissionerate wise monthly and progressive reports.
 Focal Point Bank wise monthly and progressive reports.
 Collecting Branch Bank wise monthly and progressive reports.
 Assessee wise monthly and progressive reports.
 Range wise monthly and progressive reports.
 Division wise monthly and progressive reports.
 Detailed Head wise monthly and progressive reports.
 Refunds and Drawbacks monthly and progressive reports.

Project Report Revenue Accounting System
National Informatics Center

 Bank reconciliation for the cheques issued for Refunds and Drawbacks by the Departmental
officers.
 Net Detailed Head wise revenue collection report.
 Missing Focal Point/Collecting Branch bank scrolls and missing list of payment not sent by the
Divisions.
 Consolidated Detailed Head wise reports

Project Report Revenue Accounting System
National Informatics Center

TECHNICAL BASICS

Project Report Revenue Accounting System
National Informatics Center

3. TECHNICAL BASICS
TECHNOLOGIES USED

Here, the basic question is, “Is it possible to build this application?” first we must investigate the
technologies to be used on the project. The problem with technology is that everything works perfectly
on marketing slides, but when you get the technology in house, it is often a very different story. As a
result, alternatives for each technology, if any should be identified, note that, to do a reasonable
assessment, we may need to do a mini-project and build a proof of concept prototype that verifies the
technologies do work together. This is a fundamental task of the elaboration phase and may take
several weeks or months, but will pay for itself when it verifies how your technology choices work
will.
The software and hardware requirements for the development of this project are not many and are
already available in-house at NIC or are available as free open source.
 Java Server Pages.
 Oracle
 JDBC
 Apache Tomcat

3.1 JAVA SERVER PAGES

Java Server Pages technology allows web developers and designers to rapidly develop and
maintain, information dynamic web pages that leverage existing business systems.
Java Server pages technology separates the user interface from the content generation enabling
designers to change the overall page layout without altering the underlying dynamic content .JSP
enjoys cross platform, cross-Web -server support and effectively melds the power of server-side java
technology .
JSP pages typically comprise of:
-Static HTML components.
-Special JSP tags.
Optionally, snippets of code written in the java programming language called “scriptlets”
Servlets and java server pages to create maintainable and reusable wave application. We must combine
JSP s and Servlets.

Project Report Revenue Accounting System
National Informatics Center

3.2 ORACLE

An Oracle database is a collection of data treated as a unit. The purpose of a database is to store
and retrieve related information. A database server is the key to solving the problems of information
management. In general, a server reliably manages a large amount of data in a multiuser
environment so that many users can concurrently access the same data. All this is accomplished while
delivering high performance. A database server also prevents unauthorized access and provides
efficient solutions for failure recovery.
Oracle Database is the first database designed for enterprise grid computing, the most flexible and cost
effective way to manage information and applications. Enterprise grid computing creates large pools
of industry-standard, modular storage and servers. With this architecture, each new system can be
rapidly provisioned from the pool of mponents. There is no need for peak workloads, because capacity
can be easily added or reallocated from the resource pools as needed.
The database has logical structures and physical structures. Because the physical and logical
structures are separate, the physical storage of data can be managed without affecting the access to
logical storage structures.

3.3 INTRODUCTION TO JDBC

JDBC is a Java API (Application Programming Interface) that documents a standard framework for
dealing with tabular and, generally, relational data. While JDBC 2.0 begins a move to make SQL
semi-transparent to the programmer, SQL is still the lingua franca of the standard database engines
and represents a major industry victory in the effort to separate data from code. Before getting into the
course proper, it's worth taking a few moments to provide some background on the movement from
straight-ahead SQL to JDBC.
SQL
SQL is a standardized language used to create, manipulate, examine, and manage relational databases.
This course will not extensively explain SQL, although a very basic SQL Primer and SQL Resources
are provided.
However, you should understand the following:
A database is essentially a smart container for tables.
A table is a container comprised of rows.

Project Report Revenue Accounting System
National Informatics Center

A row is (conceptually) a container comprised of columns.
A column is a single data item having a name, type, and value.

3.4 ODBC

ODBC (Open Database Connectivity), a C-based interface to SQL-based database engines, provides a
consistent interface for communicating with a database and for accessing database metadata
(information about the database system vendor, how the data is stored, and so on). Individual vendors
provide specific drivers or "bridges" to their particular database management system. Consequently,
thanks to ODBC and SQL, you can connect to a database and manipulate it in a standard way. It is no
surprise that, although ODBC began as a PC standard, it has become nearly an industry standard.
JDBC 1.0
The JDBC 1.0 API provided the basic framework for data access, consisting primarily of the following
interfaces and classes:
Driver
DriverManager
Connection
Statement
PreparedStatement
CallableStatement
ResultSet
DatabaseMetaData
ResultSetMetaData
Types
As you will see in this course, you pass a Driver to the DriverManager and then obtain a Connection.
A Statement, PreparedStatement, or CallableStatement is then created and used to update the database
or execute a query. A query returns a ResultSet containing the requested data, which is retrieved by
Type. DatabaseMetaData and ResultSetMetaData classes are available to provide information about a
database or a ResultSet.

Project Report Revenue Accounting System
National Informatics Center

Connecting to the database
This is the first job of the JDBC driver, and specific information must be passed to it. The basic
information requirements are a Database URL (Universal Resource Locator), a User ID, and a
Password. Depending on the driver, there may be many other arguments, attributes, or properties
available.
There are always two steps to making a database connection using the DriverManager:
Load the JDBC driver.
You must load a driver that enables the JDBC classes to communicate with a data source. In the initial
examples, the driver class used with Cloudscape, RmiJdbcDriver is hard-coded. Here's the standard
method for dynamically loading a driver:
Class.forName (DriverClassName);
A standard JDBC Compliant driver should also create a new instance of the driver class with this code.
Unfortunately, in practice this does not work for all cases. For that reason, the exercises use the
following code:
Class.forName (DriverClassName).newInstance ();
While this code will create an additional object in many cases, the code required to determine whether
an instance was created, and to create a new instance if not, generally outweighs that extra cost.
Fortunately, the garbage collector eventually cleans up the unreferenced object and the DriverManager
does not register the driver twice.
Drivers can also be specified from the command line via the jdbc.drivers system property, but this
method requires the driver(s) to be in the classpath at compile time:
The driver supplies methods to make a Connection, but requires a specific type of URL, which uses
the jdbc protocol. One obvious point that is often taken for granted: the use of URLs means that JDBC
applications are more or less automatically network and internet enabled.
Using the DriverManager class, you request a Connection using the passed URL and the
DriverManager selects the appropriate driver; here, only the Cloudscape driver is loaded. Here's the
standard form of the Connection request:
Connection con = DriverManager.getConnection (URL, Username, Password);
This form is best for portability even in cases where Username and Password are empty strings ( "" )
due to a database default or, say, text files acting as ODBC data sources, which cannot make use of
such attributes.

Project Report Revenue Accounting System
National Informatics Center

Statements, ResultSet, and Interacting with a Database
A Statement object is a container or transport mechanism to send/execute (normally) SQL statements
and retrieve any results via its associated Connection. As mentioned in Areas Controlled by the
Connection Interface, there are three types of Statements, including Prepared Statements and Callable
Statements, both of which are sub interfaces of Statement. As noted earlier, you do not create a new
instance of Statement, but instead, request the associated Connection to create one:
Statement stmt = con.createStatement ();
The execute series are the most often used of Statement's methods:
ExecuteQuery () is used to execute SQL statements that return a single ResultSet.
execute Update() is used to execute SQL statements that modify a table or values of columns in a table
and return the number of rows affected (which is zero in the case of DDL statements).
Execute () can be used to execute any type of SQL statement, but is intended for those that can return
multiple results or values. Execute () is not discussed further in the course.
To allow the most flexibility to work with various databases and data sources, JDBC places no
restriction on the kinds of SQL statements that a Statement can send. In fact, if the data source can
understand it (and this is a programmer responsibility), the statements don't even have to be SQL,
which raises some interesting possibilities. However, a driver that claims to be JDBC Compliant must
support at least ANSI SQL-92 Entry Level capabilities.
A Statement should automatically be closed when the Connection is garbage collected, but you should
close it yourself as soon as it is no longer needed. The JDBC recommendation is to always close the
Statement explicitly.
Modifying Data
Update has a specific meaning to programmers and, indeed, to SQL, so execute Update() is probably
an unfortunate name for a method that is used to execute DML ( INSERT, UPDATE, and DELETE)
statements as well as DDL statements such as CREATE TABLE, DROP TABLE, and ALTER
TABLE. Regardless, it is used for all of these; in fact, as a rule of thumb, use it for anything that does
not return a ResultSet.
JDBC defines types to match SQL data types. These must be appropriate to the data to avoid technical
problems, unanticipated results, and to promote job retention. See Java-SQL Type Equivalence for
further information on the available and appropriate types.

Project Report Revenue Accounting System
National Informatics Center

execute Update() returns an int containing the affected row count for INSERT, UPDATE, or DELETE
statements, or zero for SQL statements that do not return anything, like DDL statements.
The JDBC provide support for two tier and three tier database access models. We will examine use the
two tier database access model. Your java application talks directly to the database. This is
accomplished through the use of JDBC driver, which send commands directly to the database. The
results of these commands are then sending back from the database. The results of these commands are
then sending back from the database directly to the application.
4.6 APACHE TOMCAT
Apache Tomcat is the servlet container that is used in the official Reference Implementation for
the Java Servlets and java server pages technologies. The Java Servlets and Java Server Pages
specifications are developed by Sun under the java community process.
Apache Tomcat is developed in an open and participatory environment and released under the
Apache tomcat license. Apache Tomcat is intended to be a collaboration of the best-of-breed
developers from around the world. We invite you to participate in this open development project
Apache Tomcat powers numerous large-scale, mission-critical web applications across a diverse
range of industries and organizations.

Project Report Revenue Accounting System
National Informatics Center

PROJECT PLAN AND RISK ANALYSIS

Project Report Revenue Accounting System
National Informatics Center

4. PROJECT PLAN AND RISK ANALYSIS

4.1 PROJECT PLANNING

Software project planning involves estimation of Money, Effort, Resources and Time it will take to
build a specific software base system.
It provides a framework that enables the manager to make seasonable estimate of resources, cost and
schedule. The estimates are made within a limited time frame at the beginning of the software project
and should be updated regularly as project progresses.

4.3 FEASIBILITY STUDY

4.3.1 Economic Feasibility
The financial and economic question raised during preliminary investigations are for the purpose of
estimating-
 The cost to conduct full system investigation.
 The cost of hardware and software for class of application.
 The benefits in term of reduced cost and fewer costly errors.
 The cost if nothing changes, i.e., if the proposed system is not developed
Our Proposed system is economically feasible because-
 The System works efficiently
 The system will provide a fast and efficient automated environment instead of slow and taxing
manual system, thus reducing both time and manpower spent in running the existing system.
 The system will be a user friendly one with an easy GUI
 The system will provide more efficient and unbreakable security than the already existed
manual system.
 The cost of the system is nothing in comparison to the amount of money it will save because of
the higher security it provides.
4.3.2 Technical Feasibility
Technical feasibility centers the existing computer system (H/W and S/W)
Whether it can support the addition of proposed system, if not, to what extent it can support and the
organization‟s capacity to acquire additional components.
Our proposed system is technically feasible because-

Project Report Revenue Accounting System
National Informatics Center

The H/W and S/W required are easy to install and handle.
The necessary H/W configuration and software platform is already there and only two additional
hardware (smart card reader and barcode reader) will be needed which NIC can purchase easily.
The system supports interactivity with the user through GUI
4.3.3 Behavioral Feasibility
Behavioral feasibility determines how much effort will go into selling the proposed system, in
educating and training the user staff on the new system. Behavioral study strives on ensuring that the
equilibrium of the organization is not disturbed. The changes should be readily accepted by the staff
and sanctioned by authority to achieve organizational objective.
Our proposed system is behaviorally feasible because-
The state authority accepts it since it provides greater security, which is a must requirement.
The Staff, which uses the application, accepts it, as it is not hard to use.
The land owner accepts it as it provide greater value to the document he posses.
4.4 RESOURCES
Resources are required to accomplish the software development effort. The three major categories of
software engineering resources are- people, reusable software components, and the development
environment (hardware and software tools).
Human Resources:
In this project, there is only person assigned to do coding all the phases of software development. For
support internal guides are included.
Reusable Software Resources:
We have used a barcode generator executable jar file, to make application to generate barcode.

4.5 PROJECT SCHEDULE

Project scheduling is the process of creating a network of the software engineering tasks that will
enables the job done on time. After creating network have to assign responsibility. Project scheduling
needs to follow the following steps:
 Determine the estimated effort and duration for the project.
 Use an incremental process model and develop a software engineering strategy that will deliver
critical functionality by the imposed deadline.

Project Report Revenue Accounting System
National Informatics Center

 Meet the user and explain why the imposed deadline is unrealistic.
 Offer the incremental development strategy as an alternative.
To complete the project on time following principals are need to be followed:
 Compartmentalization: The project must be divided into a number of manageable activities,
actions, and tasks.
 Interdependency: The interdependency of each compartmentalized activity, action, or task
must be determined.
 Time allocation: Each task to be scheduled must be allocated some number of work units.
 Effort validation: Project should have defined number of people having defined task.
 Defined responsibilities: Each member of the project team should have a definite task.
 Defined outcome: Every task should have a defined outcome.
 Defined milestones: Every task should be associated with a project milestone.

4.6 RISK ANALYSIS

Risk analysis and management are a series of steps that help a software team to understand and
manage uncertainty. Many problems can plague a software project. A risk to a potential problem – it
might happen, it might not. But , regardless of the outcomes, its really good idea to identify it, assess
its probability of occurrence, estimate its impact, and establish a contingency plan should the problem
occur.
Software is difficult undertaking. Lots of things can go wrong, many often do. Its for this reason that
being prepared – understanding the risks and talking proactive measures to avoid or manage them – is
a key element of good software project management. Different steps in risk analysis and management
are risk identification, risk analysis and risk planning and management.
Risk Identification
Risk identification is the first stage of the risk management. It is concern with discovering possible
risks to the project. In principal, these should not be assessed or prioritized at this stage, although I
practice risks with very minor consequences or very low probability risks are not usually considered.
Risk Analysis
During the risk analysis process, each identified risk is considered in turn and a judgment made about
the probability and seriousness of the risk. Once the risks have been analyzed and ranked, a judgment
must then made about which are the most important risks which must be considered during the project.

Project Report Revenue Accounting System
National Informatics Center

Risk Planning and management
Risk planning process considers each of the key risks. Which have been identified and identified
strategies to manage the risk. Again there is no simple process which can be followed to establish risk
management plans. It relies on the judgment and experience of the project manager.
For the above risk we have following strategies:
Schedule failure:
We have divided wok in no of days so very less chances of failure of schedule.
Project as per requirement:
We have met each and every person related to our system for getting the right requirement so in short
we achieve almost all the requirement.
Quality of product:
As we have gathered all requirements, we can produce the system with a clear idea. There is no doubt
regarding the requirements and the processes so quality of product is a low risk factor.

Project Report Revenue Accounting System
National Informatics Center

SYSTEM REQUIREMENT SPECIFICATION

Project Report Revenue Accounting System
National Informatics Center

5. SYSTEM REQUIREMENTS

5.1 Software Requirements
 Windows XP as Client and Windows Server2000 as Server
 Note taker
 Oracle
 JDK 1.6
 Tomcat

5.2 Hardware Requirements

 Intel Pentium 4 processor, 2.40 GHZ
 256 DDR RAM
 80 GB Hard Disk
 17” color monitor
 Inkjet Printer

Project Report Revenue Accounting System
National Informatics Center

SYSTEM DESIGN

Project Report Revenue Accounting System
National Informatics Center

6. SYSTEM DESIGN

6.1 INTRODUCTION

Design is critical component of software development life cycle. It is a meaningful
representation of the system to be built and can be traced to the customer requirements. Absence of
proper design is bound to lead to confusion and errors. A complete design must accommodate all of
the implicit requirements desired by the customer. It must be a readable, understandable guide for
programmers. It should provide a complete picture of the software addressing the data, functional, and
behavioral domains from an implementation perspective.
The following insights and understandings gained during the analysis phase were used as guidelines
for designing the system:
The structured system development methodology should be followed while designing the system i.e.
the system should be designed in such a way that it has the following properties:
 Modularity: The system should have a separate module for each function.
 Logic/Hierarchy: The components/modules of the system should be logically hierarchically
related to each other.
 Cohesiveness: There should be maximum interaction within each component module.
 Low degree of coupling: There should be minimum interaction between components
/modules.
 Visibility: It should be easy to perceive how and why actions occur i.e. the actions being taken
must be traceable.
 Simplicity: There should be no complexity or ambiguity in the system.
 Uniformity: The structure of the components / modules should be uniform.
This design of the software is a multi-step process that focuses on five distinct attributes of a program:
Data Structure, Software Architecture, Interface Representation, System Controlling and Procedural
Detail.
Design process translates requirement of software that is assessed by quality before coding begins.
Requirements of system is documented and become part of software configuration.

6.2 DESIGN CONSIDERATIONS

A variety of design alternatives were considered. A summary of the principal issues follows:

Project Report Revenue Accounting System
National Informatics Center

Overall design
Keeping in mind the software is designed to be modular. It was decided that going for a modular
design would be highly beneficial. This design decision helped immensely in getting a clear view and
thus reducing and simplifying greatly the effort required in generating the code.
Designing of Forms
Deciding on the layout of a form is critical. A faulty design can prove to be a major problem.
Changing form layout at later stages is demanding so it is better to finalize the design before making
the form. For this purpose lengthy discussions were held with the actual users in order to get a better
understanding of their requirements. Suggestions were invited to explore the drawbacks in the existing
forms so that a conscious effort could be made to make the forms user-friendlier.
Finally a layout was finalized to incorporate ease of navigation as required in real time while
simultaneously adhering to the established organizational standards.
Design characteristics and evaluation Criteria
The following goals were kept in mind while designing the new systems:
 To reduce the manual work required.
 To avoid errors inherent in the manual works and hence make the outputs consistent, correct,
authentic and secure.To make the system completely menu-driven and hence user friendly.
This was necessary so that even non-programmers could use the system efficiently and system
could act as catalyst in achieving objectives.
 To make the system completely compatible i.e. it should provide output in a format that is
standardized so that no issue arises of compatibility problem.
 To design the system in such a way that reduced Future maintenance and enhancement times
and efforts. Hence the DLL was coded so that the further enhancements can be done without
giving the core code and also making it simple for any additions.
 To make the system more reliable, understandable and cost effective.
6.3 ASSUMPTIONS
It would be required that the sub-division level Revenue Functionaries must be present at the time
of Initial/ Basic Data entry of the Plots & Owner Holdings, so that the errors can be minimized and
time taken to verify the data would be substantially reduced. If more errors exist in the data then new

Project Report Revenue Accounting System
National Informatics Center

forms may have to be added to resolve data integrity issues, such as forms for deletion, renaming and
so on. The proper working of the system depends upon the following assumption:
All the requirements of the required hardware and software are fulfilled.

6.4 GENERAL CONSTRAINTS
Basic constraint:
The operator of this software should be computer literate.
As the software is not multi lingual therefore operator must know Basic English.
Technical Constraint:
 The PC should be booted in Windows Operating system.
 PC should have Oracle and Jdk1.2 or higher.

6.5 DEVELOPMENT METHOD
In this project we have used waterfall model because of following reason:
 Initial requirements are reasonably well-defined and reasonably stable.
 Works flows through development in a linear fashion.
The waterfall model suggests a systematic sequential approach to software development. The waterfall
model, is sometimes called the classic life cycle, suggests a systematic, sequential approach to the
software development that begins with customer specification of requirements and progress through
planning, modeling, construction, and deployment, culminating in on-going support of the completed
software.
The waterfall model is the oldest paradigm for the software engineering.
The steps that are followed during waterfall model are:
 Communication: Project initiation requirements gathering.
 Planning: Estimating scheduling tracking.
 Modeling: Analysis design.
 Construction: Coding and Testing.
 Deployment: Delivery, support and feedback.

Project Report Revenue Accounting System
National Informatics Center

6.6 ARCHITECTURE

The three-tiered client/server architecture introduces a third layer of processing between the client
and the server as shown in fig below. On PC-based LANs, three-tiered is the more recent architecture
and what goes on in the middle tier is much less strictly defined than what goes on in the client and
server tiers. An important advantage of three-tiered architecture over two-tiered is that it allows the
client and the server to lose weight and become "thin clients" and "thin servers." This means that the
partitioning of functions can be carried further, and greater modularity can be achieved. Advocates of
three-tiered architecture usually agree that transactions should be implemented in the middle layer.
Other processes that could be implemented in that layer include translating data from legacy
applications on mainframes, handling security and authentication, and generating reports.
Three-Tiered Web Database Application
Web database applications combine their two-tiered parent technologies into a new kind of system.
The new system is based on the three-tiered client/server architecture. A Web browser occupies the
client tier, a database server occupies the server tier, and the middle tier holds a Web server and a
server extension program (Figure below). This architecture reduces network traffic, makes
components interchangeable, and increases security. However, this architecture also makes database
transaction processing more difficult because of the stateless nature of the HTTP protocol that is used
to transfer data between the web browser and the database server.
The Web browser sends Web page requests or data requests to the Web server. The Web server
services the page requests and passes the data requests to the server extension program. The server
extension program then accepts the requests that are passed to it, converts them to a form that the
database server. Next, the database server performs a database task, such as a query or an insert, and
returns a result set to the server extension program. Finally, the server extension program converts the
database results to a form that the Web browser will accept (for example, HTML), and passes them to
the Web server, which in turn passes results to the Web browser.

Project Report Revenue Accounting System
National Informatics Center

6.7 CODING

Coding Optimizations
Code optimization depends on the type of application we are writing. In most case we will be
optimizing small, tight sections of code that are executed frequently (such as loops or frequently called
procedures). Code optimization requires a combination of experience, an eye for detail, and a basic
understanding of the architecture of the language and how processors work.
We should never consider our code to have been optimized completely, and never underestimate our
capabilities. Although there are no hard and fast rules for optimizing code, there are some tricks we
can use and some guidelines we could follow.
Maximize Subjective Speed
No amount of optimization is going to do us good unless the users of our application think it is fast.
Speed (also called perceived speed or apparent speed). The most important measure of the speed of an
application is its so-called subjective speed can‟t be measure in time units; actually it is a speed, which
describes how fast the application appears to the user. An application that loads responds and repaints
the screen quickly, may actually be preferred to an application that does its math faster, but takes too
long to load, or one that doesn‟t respond quickly to user action. Subjective speed can be improved in
many ways in this case our goals includes:
Forms are loaded quickly
We have avoided lengthy code segments in a form run event. This is because a form run event takes a
few seconds to execute; the form wouldn‟t be drawn until the run event handler has completed its
execution.
Use of Proper Data Types
The simplest optimization is to use the proper data types for our calculations. In general the short the
data type, the more efficiently it is handled. Actually extra accuracy comes at a price, and when it is
not really called for, it should be avoided.

6.8 IMPLEMENTATION

Implementation is the process of having systems personnel check on output, new equipment into use,
train users, install the new equipment and construct any files of data needed to use it. Depending on
the size of the organization that will be involved in using the application and the risk associated with

Project Report Revenue Accounting System
National Informatics Center

its use, system developers may choose to pilot (test) the operation in only one area of the firm, say in
one department or with only one or two persons.Once installed application are often used for many
years.However, both the organization and users will change, and the environment will be different
over weeks and months. Therefore the application will undoubtedly have to be maintained;
modification and changes will be made to the software, files or producers to meet user requirements.

6.9 DETAILED SYSTEM DESIGN

6.9.1 DATA FLOW DIAGRAMS

Data flow diagram serves two purposes:
Provide an indication of how data are transformed as they move through the system.
To depict the functions (and sub functions) that transform the data flow.
The DFD provides additional information that is used during the analysis of the information domain
and serves as basis for modeling of function. A description of function in DFD is contained in
Functional specification.
Directory Details
Directory Request
Revenue
Vsat Deta data entry Details
Accounting
USER Data entry Request Easiest Details Data base
System
Easiest Request
(REVACT)
View Reports
Reports

CONTEXT DIAGRAM (0 LEVEL DFD)

Project Report Revenue Accounting System
National Informatics Center

Request
1 Directory Details
Directory
Processing

2
Request
User
Data entry
Processing
Data entry Details

Data_Base

Request 3
Easiest Details
Easiest
Processing

Report
4
Request
View
Reports

Project Report Revenue Accounting System
National Informatics Center

1st Level DFD

Request 1.1

Directory_Up Data Base

Directory

CF
Forward
Comm_Name

Request 1.2
User
Directory List
Response
Directory Data base

2nd level DFD (Directory)

Project Report Revenue Accounting System
National Informatics Center

2.1

Challan
Challan_mast
Data Entry

User

2 nd Level DFD (Data Entry)

3.1
Verification
Of e-Challan NSDL_DATA

Easiest

User

3.2

Scroll
Comm_CodeMass
Easiest
Focal_Point_bank

Acchead_Dir

2 nd Level DFD (Easiest)

Project Report Revenue Accounting System
National Informatics Center

Request
4.1
Response
Directory
Data base
Report

Request 4.2
Response validate report Data base

Report

User Request 4.3
Monthly Data base
Response revenue

Report

4.4
Request Data base
Response Progressive

Report

Request 4.5

Response Refund Data base

Report

Request 4.6
Database
Challna/Scroll

Report 2nd level DFD(Report)

Project Report Revenue Accounting System
National Informatics Center

3rd level DFD (Directory)

1.1.1
Assessee_Dir
Assessee

Diretory_Up
Updation

1.1.2 Comm_CodeMass

Commissioner

Directory_Up

User
1.1.3 Div_Dir

Division

Directory_Up

Range_Dir
1.1. 4

Range

Diretory_Up

1.1. 5
Branchbank_Dir
Branch Bank

Diretory_Up

Focalpoint_Dir
1.1. 6

Focal Bank
Project Report Revenue Accounting System
Diretory_Up
National Informatics Center

3rd level DFD(Report) Comm_CodeMass

Request
4.1.1
Assessee_Dir
Response
Assessee
Range_Dir
Directory

1.1.1 Division_dir

Request 4.1.2
Assessee
Response Commission
Diretory_Up Comm_CodeMass
Updation
Directory

Request
USER Response 4.1.3
Div_Dir
Division

Directory

Request
4.1.4
Response Range_Dir
Range

Directory

4.1.5
Request
Branch Bank Branchbank_Dir
Response
Directory

Request 4.1.6
FocalPoint_Dir
Focal bank

Project Report Directory Revenue Accounting System
National Informatics Center

1.1.1.1
Assessee_entry Data Base

Assessee_Up

User

1.1.1.2

Upload File Data Base
Text File
Assessee_Up

4th level DFD (Directory)

Project Report Revenue Accounting System
National Informatics Center

Request
1.1.1.1.1
Response
Query Assessee_Dir

Assessee_Up

Comm_CodeMass
Request 1.1.1.1.2
Response
Execute
Assessee_Dir
Assessee_Up

1.1.1.1.3 Comm_CodeMass
Request
User
Next
Response
Assessee_Up
Updation

1.1.1.1.4
Request
Response Prev
Assessee_Dir
Assessee_Up

1.1.1.1.5
Assessee_Dir
Save

Assessee_Up
5th Level DFD (Directory)

Project Report Revenue Accounting System
National Informatics Center

E-R DIAGRAM ass_Address Range_Code
ass_type

ass_Name

ass_Code
necc_code
Assessee_Dir

bb_code

1
Range_Name
m

CA
Range_Code
Batch_No Tax
Date_deposit
bb_scr_no
1 n
acc_Month

Bill_ship_no
ChallMast

Range_Dir
Serial_No
n
Div_Code
Frward

Country_code.
necc_Code 1
challan_no
. Division_Dir
ass_type
Comm_Code

A Div_name
A
Project Report Revenue Accounting System
National Informatics Center

A A

Frwrd
Frwrd
bb_status

1
Fpb_code
1

Branch_Bank_ n
Dir
Sen
1 Comm_CodeM
d_ch ass

Comm_Code bb_code Comm_Code
bb_name

4.1.1

Assessee

Diretory

Fpb_address 1.1.1
Fpb_code
Assessee
Fpb_name
Diretory_Up
Updation
Comm_Code

FPB_Dir

Project Report Revenue Accounting System
National Informatics Center

TESTING

7. TESTING

7.1 INTRODUCTION

Software testing is a critical element of software quality assurance and represents the ultimate review
of specification, design and coding. The purpose of product testing is to verify and validate the various
work viz. units integrated units, and final product to ensure that they meet their respective
requirements.
This has two parts:
Planning: This involves writing and reviewing unit, integration, functional, validation and acceptance
test plans.

Project Report Revenue Accounting System
National Informatics Center

Execution: This involves executing these tests plans, measuring, collecting data and verifying if it
meets the quality criteria set in the quality plan. Data collected is used to make appropriate changes in
the plan related to development and testing.

7.2 TESTING OBJECTIVE
 Testing is a process of executing a program with the intent of finding an error.
 A good test case is one that has a high probability of finding an as-yet undiscovered error.
 A successful test is one that uncovers an as –yet undiscovered error.

7.3 TEST PLAN
The quality of a product or item can be achieved by ensuring that the product meets the requirements
by planning and conducting the following tests at various stages
Unit Tests at unit level, conducted by development team, to verify individual standalone units.
Integration Tests after two or more product units are integrated conducted by development team to
test the interface between the integrated units.
Functional Test prior to the release to validation manager, designed and conducted by the team
independent of designers and coders, to ensure the functionality provided against the customer
requirement specifications.
Acceptance Tests prior to the release to validation manger, conducted by the development team, if
any supplied by the customer.
Validation Tests prior to customer, conducted by the validation team to validate the product against
the customer requirement specifications and the user documentation.

7.4 TEST CASE DESIGN
Test case design focuses on a set technique for the cases that meet overall testing objectives. In test
case design phase, the engineer creates a series of test cases that are, intended to “demolish” the
software that has been built.
Any software product can be tested in one of two ways:

Project Report Revenue Accounting System
National Informatics Center

Knowing the specific function that a product has been designed to perform, test can be conducted that
demonstrate each function is fully operational, at the same time searching for errors in each function.
This approach is known as black box testing.
Knowing the internal working of a product, test can be conducted to ensure that internal operation
performs according to specification and all internal components have been adequately exercised. This
approach is known as white-box testing.
Black box testing is designed to uncover errors. They are used to demonstrate that software function
are operations; that input is properly accepted and output is correctly produced ; and that integrity of
external information is maintained (e.g. data files .). A black box examines some fundamental aspects
of a system with little regard for the internal logical structure of the software.
White box testing of software is predicated on close examination of procedural details. Providing test
cases that exercise specific set of conditions and loops test logical paths through the software. The
“state of the program” may be examined at various points to determine if the expected or asserted
status corresponds to the actual status.
Unit Testing
This focus on verification effort on smallest unit of software designed the software component or
module. In this we can take User Authentication module is considered to be as unit testing part. Using
component level design, description as a guide important control path is tested to uncover errors. The
module interface is tested to ensure that information properly flows into and out of the program unit
under test. Data structure is locally examined to ensure that data stored temporarily maintains its
integrity during all the steps in execution of algorithm. Boundary conditions are tested to ensure that
module is operating properly at boundaries which are established to limit or restrict processing. All
independent paths through control structure are exercised to ensure that all statements in module is
executed at least once. Finally all error-handling paths are tested.
Test cases uncover errors like:
 Comparison of different data type.
 Incorrect logical operators or precedence.
 Expectation of equality when precision errors make equality unlikely.
 Incorrect comparisons of variables.
 Improper or non-existent loop termination.
 Failure to exit when divergent iteration is encountered.

Project Report Revenue Accounting System
National Informatics Center

 Improperly modified loop variables.
The potential errors should be tested when error handling is evaluated. Boundary testing is last task of
unit test. Errors often occur when nth element of n-dimensional array is processed when ith repetition
of loop with I passes is invoked when maximum or minimum allowed value is encountered. After
source level code is been developed reviewed and verified for correspondence. A component is not a
stand-alone program.
Integration Testing
It is a systematic technique for constructing program structure while at same time conducting tests to
uncover errors associated with interfacing. There is tendency to attempt non-incremental integration;
to construct program using “big bang” approach. Entire program is tested as a whole. Program
constructed and tested in small increments where errors are easier to isolate and correct. Interfaces are
tested completely and a systematic way is applied.
In this process of testing it is incremented approach to construction of program structure. Modules are
integrated moving downward beginning with main control module. Modules subordinate structure to
main control module is incorporated into structure. This form of testing is performed of software in
five steps: -
 Main control module is used as test driver and stubs (modules) are substituted for all
components subordinate to main control.
 Depending on integration selected subordinate stubs are replaced one at a time.
 Tests are conducted as each component is integrated.
 On completing each set of tests another stub is replaced.
 It is also tested to ensure that new errors have not been introduced.
In well-factored program structure decision-making occurs at upper levels in hierarchy and therefore
encountered first. If major control problem do exist, early recognition is essential. This is termed as
top-down integration testing.
Bottom-up integration testing begins construction and testing with atomic modules as the
components are integrated from the bottom-up, processing required for components subordinate to a
given level is always available and the need for stubs is eliminated. In this strategy:-
Low-level components are combined into clusters that perform a specific software function.
A driver (a control program for testing) is written to coordinate test case input and output.
The cluster is tested.

Project Report Revenue Accounting System
National Informatics Center

Drivers are removed and clusters are combined moving upward in the program structure.
Each time a new module is added as part of integration testing, the software changes. New data flow
paths are established, new I/O can occur, and new control logic is invoked. These changes cause
problems with functions that previously worked flawlessly. In context of integration test strategy,
regression testing is the re-execution of some subsets of tests already been conducted to ensure that
changes are not propagated unintended side effects.
Successful tests result in discovery of errors and errors must be corrected. When software is corrected
some aspect of software configuration is changed.
Smoke testing is an integration testing that is commonly used when “shrink wrapped” software
products are being developed. It is designed as pacing mechanism for time critical projects, allowing
us to assess the project on frequent basis. This consists of steps: -
Software components are translated into code is integrated into a “build”. A build includes all data
files, libraries, reusable modules and engineered components.
A series of tests is designed to expose errors that will keep the build from properly performing its
function.
The build is integrated with other builds and the entire product is smoke tested daily.
Validation Testing
Software is completely assembled as package, interfacing errors have been uncovered and correct, and
a final series of software tests is validation testing. Validation is defined in many but simply is that
validation succeeds when software functions in a manner reasonably expected. Software validation is
achieved through series of tests that demonstrate conformity with requirements. A test plan outlines
the classes of tests to be conducted and a test procedure defines specific test cases that will be used to
demonstrate conformity with requirements. Both the plan and procedure are designed to ensure that all
functional requirements are satisfied, all behavioral characteristics are achieved, all performance
requirements are attained, documentation is correct and other requirements are met.
Finally all validations we want to apply on the system during starting stage of development, after
doing validation testing it is noticed that nearly all are working at their respective part in application.
7.5 TESTING REQUIREMENTS AND ACCEPTANCE CRITERIA
The following acceptance criteria were established for the evaluation of the new system

Project Report Revenue Accounting System
National Informatics Center

The system developed should be accurate and hence reliable i.e. the error rate should be minimized
and the outputs should be consistent and correct.
The developed software should provide all the required functions. Further, both the execution time and
the response time should negligibly low. It should also satisfy the criteria specified in functional and
performance requirements.
The system should be efficient i.e. the resource utilization should be optimal.
The system should have scope to foresee modifications and enhancements i.e. it should be able to cope
with business changes.
The system must satisfy the standards of good software:
User Friendliness: The system should meet user needs and should be easy to use.
Modularity: The system should have relative independent and single-function parts that can be put
together to make the complete system.
Maintainability: The system should be such that future maintenance and enhancement times and
efforts are reduced.
Timeliness: The system should operate well under normal, peak and recovery conditions

Project Report Revenue Accounting System
National Informatics Center

MAINTENANCE

8. MAINTENANCE
Standardized software and hardware platforms are used. The REVACT software design too follows
the software development standards.
The code/programs and routines must be well documented and self-explanatory for any programmer to
understand. Variable names must indicate their functionality; logical constructs must be commented
etc.

Project Report Revenue Accounting System
National Informatics Center

Once the Design stage of Software development is over. Detailed documentation should be available
for easy comprehension of the software system. The documents shall be as per IEEE standards with
user requirements well defined.
The software must try to achieve a balance of structured and object oriented approach to maximize
performance. Since the development tool is not fully object oriented, the common and reusable
functionality of the software can be separated and maintained in modules to avoid duplication of code
and functionality as well. For e.g. Login function, functions dealing with codes‟ population with code
category as a parameter, using stored procedures for common tasks, functions used for common
calculations and conversions.
Optimum distribution of client based processing and the server based processing so as to minimize
network traffic, by utilizing database-coding facilities like stored procedures and triggers.

8.1 COST ESTIMATES

It is very difficult to make an exact of estimate cost and effort for any project. Too many variables-
human, technical, environmental, and political - can affect the ultimate cost of software and effort
applied to develop it. This being an in-house project makes it difficult to determine the costs exactly.

Project Report Revenue Accounting System
National Informatics Center

DATA DIRECTORY

THE TABLE USED ARE SHOWN BELOW

Table: Assesseedir

Name Type Size Description
necc_code Varchar2 15 New Assessee Code

Project Report Revenue Accounting System
National Informatics Center

asse_code Varchar2 10 Old Assessee Code
asse_type Varchar2 1 Specify the type of the assessee
asse_name Varchar2 60 Assessee name
asse_addres Varchar2 160 Assessee address
s
Range_cod Varchar2 6 Assessee location
e

Primary key- necc_code

Table: CommissionerateDir

Name Type Size Description
Comm_code Varchar2 2 Commissionerate code.
Comm_name Varchar2 55 Commissionerate.Name

Primary Key- comm_code

Table: Divisiondir

Name Type Siz Description
e
Comm_code Varchar2 2 Commissionerate code.
div_code Varchar2 2 Division code.
div_name Varchar2 30 Division name.

Table: Rangedir

Name Type Size Description
Range_code Varchar2 6 Range code
range_name Varchar2 50 Range name.

Primary Key- Range_code

Table: Branchbankdir

Name Type Size Description
fpb_code Varchar2 7 Focal Point Bank code
bb_code Varchar2 7 Branch bank code

Project Report Revenue Accounting System
National Informatics Center

bb_name Varchar2 35 Branch Bank Name
Comm_Code Varchar2 2
bb_status Varchar2 1 Bank‟s status. („O‟ : „Out-station‟ , „L‟ : „Local‟)

Primary key – bb_code

Table: Focalpbdir

Name Type Size Description
comm_code Varchar2 2 Commissionerate code

fpb_code Varchar2 7 Focal point bank code

fpb_name Varchar2 35 FP Bank name
fpb_address Varchar2 70 FP Bank address

Table: ChalMast

Column Type Size Description
batch_no Varchar2 6 physical identification for file e.g. for challan file
CH0001
acc_month Varchar2 6 Is a 6-digit field, first 4-digit: accounting year Next
2-digits: accounting month for specific challan.
serial_no Number 8 Serial no. of the Challan (Automatically generated
for each challans.
necc_code Varchar2 15 Assessee code
asse_type Varchar2 1 Assessee type “E‟ : „Excise‟, „C‟: „Customs‟, ‟S‟ :
„Sales‟, „T‟ : „Travel‟, „O‟ : „Others‟
Range_code Varchar2 6 Assessee‟s location code
challan_no. Number 5 Challan no.
bb_code Varchar2 7 Branch bank code
bb_scr_no Number 8 B Bank Scroll number of the challan
Country_code Varchar2 3 3-digit field ,specifies country code of the assessee

Bill_ship_no Varchar2 6 Bill of Entry/ Shipping Bill No.

Project Report Revenue Accounting System
National Informatics Center

SCREEN SHOTS

10. SCREEN SHOTS

Revenue Accounting System [REVACT]

Project Report Revenue Accounting System
National Informatics Center

Fig: Home page

Project Report Revenue Accounting System
National Informatics Center

Fig: Login screen

Project Report Revenue Accounting System
National Informatics Center

Fig: 1.1

By clicking the login, the screen shown above in fig 1.1 is displayed with current date and time. The
following main modules are available:

Directory Data-entry Validation House Keeping Reports Exit

By clicking the above mentioned options as and when required the corresponding options become
available to the user. All these options are discussed in detail in further sections.
NOTE: 1. All the directories are to be updated first to carry out all the online validations required at
the time of data entry related with
- Challan
- Scroll

Project Report Revenue Accounting System
National Informatics Center

2. Though Commissionerate directory is not needed, yet it has been created for the sake of
uniformity. Entering respective Commissionerate at the time of report generation will pick up the
corresponding Commissionerate name from the directory.
3. Focal point bank directory is also not needed under „one bank-one Commissionerate„scheme. So at
this stage, the directory will have single record. The directory has been prepared to facilitate any future
changes (i.e. multi bank-one Commissionerate scheme).
2.1 Directory
2.1.1 Directory Update

Fig 2.1.1

Project Report Revenue Accounting System
National Informatics Center

As shown in the fig 2.1.1, to update the specific directory, select Directory option from the main
menu. It has two options
- Directory Update
- Directory Listing
Before Actual Data Entry of Challan/Scroll files the following directories mentioned in the “Directory
Update” are to be updated.
Assessee
Entry Form
To update the directory of Assessee, select Assessee option from the Directory Update. This leads us
to the Assessee Updating screen as shown below:

Fig 2.1.2

Project Report Revenue Accounting System
National Informatics Center

To enter records to the database:
Message is displayed for each entry field, depending upon the cursor position for e.g. when the cursor
is positioned at “Assessee Code” field, the message is displayed as “Enter the Assessee code”, which
facilitate the user to enter the assesses code in the appropriate field. Depending on the cursor location
appropriate message is displayed.
The following buttons are provided to user at all data entry screens to do Data Entry /Retrieval
of records.
Query / Retrieve
For fetching particular record in the above screen, the Assessee code is entered and on clicking
the query button and Retrieve button, the record pertaining to that particular Assessee code is fetched.
If no Assessee code is given after clicking the query button, then all the records are fetched.
Next / Prev
- On clicking the next or Next / Prev button user can scroll through the records of the database.
Delete
- On clicking the Delete button the record on the screen is deleted with delete conformation.
Clear
- On clicking Clear button the information on the screen gets cleared.
Show Keys
- On clicking Show Keys button the following help keys are available to the user for ready reference.
Save
- On clicking Save button the record on the form (screen) gets saved. Even otherwise pressing Enter
key after the last field automatically saves the record.
Exit
- On clicking Exit button user can come out of the form.
(ii). Update from File
Select this option from Assessee of Directory Update option. This option is used whenever Assessee
directory is to be updated from floppy.

Project Report Revenue Accounting System
National Informatics Center

Fig 2.1.3

Project Report Revenue Accounting System
National Informatics Center

Fig 2.2.4

Project Report Revenue Accounting System
National Informatics Center

The remaining directories (II to XI) can be updated easily in the same way..
II Commissionerate
III Division
IV Range/Location
(i). Entry Form

(ii). Update from File
Select this option from Range/Location of Directory Update option. This option is used whenever
Range/Location Directory is to be updated from floppy.
V Branch Bank: The option „update from file‟ is also provided here to update Branch Bank Directory
from floppy.
VI Focal Point Bank
VII Refund Bank
VIII Account Head
IX Cheque Nos.
X Import / Export
XI Country
2.1.7 Directory Listing
To view the records of a specific directory, select Directory option from the main menu and then
Directory listing option. The following list is displayed.

Project Report Revenue Accounting System
National Informatics Center

Assessee

Fig: 2.1.5

Commissionerate
Division
Range / Location
Branch Bank
Focal Point Bank
Refund Bank
Account Head

Project Report Revenue Accounting System
National Informatics Center

Cheque Nos.
Import / Export
Country
The main difference between Directory update and Directory Listing is that in the former the database
records can be viewed one by one where as in the case of latter complete directory can be viewed at
one instance.
2.2 Data Entry
Select Data Entry option from the main menu of RevAct, the follow is displayed:
Challan
Scroll
Refund/ Drawback
(I) On selecting Refund/Drawback, the following is displayed:
Scroll of Payment
List of Payment
2.2.1 Challan
Select this option from the Data Entry menu to enter the Challan records to the database. On selecting
this option theTR6 Challan Data Entry screen as shown below in the fig. 2.2.1. Is displayed. Here the
Batch No. and A/C Month are to be entered by the user only once (per Accounting Month). Later on
they are automatically displayed for all further entry of records. (I.e. the user need not to enter these
fields for each record).
The TR6 Challan Data Entry Screen is same for Excise, Service tax.

Project Report Revenue Accounting System
National Informatics Center

Fig: 2.2.1
2.2.2 Scroll

Select this option from the Data Entry menu to enter the Scroll records to the database and is shown
below in Fig. 2.2.2
Here also data entry screen has been divided into two forms namely Main Form and Sub Form. Here
the Batch No. and A/C Month are to be entered by the user only once (per each Accounting Month of
a financial year). Later on they are automatically displayed for all further entry of records.
After entry of the data in main form is over, cursor will be at Branch Bank Code field of the sub form.
Here Serial No. and Sub Serial No. are already displayed. The Serial No. is same as that in the main
form and Sub Serial No. display the number of records for the specific record of the main form.

Project Report Revenue Accounting System
National Informatics Center

Enter the data in the Branch Bank Code and Amount Fields of the current record of the sub form.
Press Save button on the sub form or press enter key after entry of data in the last field automatically
saves the current record. This will clear the Branch Bank Code and Amount fields of the current
record; replace the current record as previous record in the sub form. Now the Sub Serial No. is
incremented by one, and the cursor is displayed again at Branch Bank Code to enter another sub
record, if any. Total Amount is also shown each time as and when a fresh record is entered in sub
form.
An additional button „Delete All Sub Records‟ has been provided to delete all sub records within range
specified (i.e. from sub serial no. to sub serial no) related to the main serial no.
2.3 Easiest

Select easiest option from the main menu of RevAct, the follow is displayed b, c are displayed:

EASIEST (Electronic Accounting System in Excise and Service Tax) to capture G.A.R.-7/TR6
challan details electronically from banks (Data originating source) to central server (G.A.R.-7/TR6
Challan is a document used by Assessees to pay Central excise duty). EASIEST provides all data
transmission mechanism (upload and download utilities) to all stake holders of the system. Stake
holders of EASIEST are PAO, Commissionerate
It has helped the Central Excise Department to avoid the huge data entry work of challan details
and the data is readily available for the correctness of credit and monthly accounting. Accordingly the
changes were done in REVACT (Revenue Accounting System) and a separate module EASIEST is
available in e-REVACT.
The following directories are downloaded using EASIEST and pass the same to banks. These
directories are used by banks to do validations like assessee code, location code, etc. while entering
challan data. NSDL is primarily responsible to collect challan data electronically and upload the same
to NIC server on daily basis. Each challan record in the file is uniquely identified by CIN (Challan
Identification Number) consists of Challan Number, Date of deposit and Bank Code (BSR Code).

- Commissionerate code
- Division code
- Range / location code
- Assessee master
- Account head code

Project Report Revenue Accounting System
National Informatics Center

b. Verification of e-Challan Data

Click on the above option, the screen „Verification of e-challan data‟ is displayed. Click on “Query &
Execute (F1 & F2)” will display e-challan data records one by one and user can verify e-challan data
with the physical copy of a challan for the correctness of data.
User can Retrieve e-challan data for verification as per his choice by clicking at “QUERY”, enter the
content at the desired field (fields are focal point bank code, receiving bank code, focal point scroll
date, Commissionerate Code etc.) and click on EXECUTE. All e-challan records are displayed one by
one as per the user choice.
All challans manually received from banks (banks not covered under EASIEST), if any, can be entered
using the option „ADD MANUAL DATA”. Both e-challan data and the challans entered manually are
combined together in final database (BACKUPREVACT.MDB), which is used to generate monthly

Project Report Revenue Accounting System
National Informatics Center

reports. However, a separate flag “M” is used in data base to identify manually entered data separately
with e-challan data downloaded from server.

c. Scroll Entry

Click on the above option, the manual scroll received from focal point can be entered branch bank
wise one by one record.
j. Reports

The reports together provide details regarding rectified number of challan, error in Scroll and error in
challan.
2.4 Reports

Select Reports option from the main menu of RevAct, the following is displayed:

Directory

Validation Reports

Monthly Revenue

Progressive Revenue

Refund/Drawback

DTHD (Detail head wise Net Revenue)

Challan and Scroll Details

Before Validation

User is provided with the facility of using some special keys for the frequently generated

reports like match/mismatched reports under validation reports option.

2.4.1 Directory

On selecting Directory option, the complete listing of following directories can be generated:

Project Report Revenue Accounting System
National Informatics Center

 Assessee
 Commissionerate
 Division
 Range / Location
 Focal Point Bank
 Branch Bank
 Refund Bank
 Account Head
 Cheque Nos.
 Import / Export
 Country

(i) On selecting Assessee from Directory, the following reports can be generated.
 All Assessee

Project Report Revenue Accounting System
National Informatics Center

 Commissionerate wise
 Division wise
 Range wise

(ii) On selecting Division from Directory, the following reports can be generated.
 All Divisions
 Commissionerate wise
(iii) On selecting Range / Location from Directory, the following reports can be generated.
 All Ranges / Locations
 Commissionerate wise
 Division wise
(iv) On selecting Branch Bank from Directory, the following reports can be generated.
 All Branch Banks
 Focal Point Bank wise

Project Report Revenue Accounting System
National Informatics Center

CONCLUSION

Project Report Revenue Accounting System
National Informatics Center

12. CONCLUSION
Revenue accounting system is a web enabled system so that authorized user can easily access this
system from any location.
This system provides all the information about Equipments, Manpower, and Coordinators etc. of all
districts of all states.
Various reports for assesses details, commissionerate details etc. are available.
Authorised user can easily access this system even without much knowledge of this.
There is no headache of maintaining files or databases manually as they are done automatically.
No need to store Database at different sites differently.

Project Report Revenue Accounting System
National Informatics Center

13. BIBLIOGRAPHY

In order to develop Revenue Accounting system, the following books and Website are referred.
 Complete Reference JAVA
 Java server pages –Sams tech yourself.
 https://jsp-spec-public.dev.java.net/
 http://www.daniweb.com/forums/thread23246.html
 http://osdir.com/ml/jakarta.myfaces.user/2005-08/msg00056.html

Project Report Revenue Accounting System