A case study on

Computerized Information System for Trade Tax

Department
Of
Computer Science and Engineering

VISHNUSREE INSTITUTE OF TECHNOLOGY

(Affiliated to Jawaharlal Nehru Technological University)
Nalgonda District, A.P. India
Year-2011

1
 A Case Study on
Computerized Information System for Trade Tax
A Dissertation submitted in partial fulfillment for the award of the degree
of

Bachelor in Technology
In

Computer Science and Engineering

A.V.R. Aditya(08UT1A0501)

M.R. Sandeep(08UT1A0549)

S.Naveen Kumar(08UT1A0551)

VISHNUSREE INSTITUTE OF TECHNOLOGY

(Affiliated to Jawaharlal Nehru Technological University)
Nalgonda District, A.P. India
Hyderabad

2
 Certificate
This is to certify that the project report entitled ………… being submitted by Mr./Mrs.
…….. In partial fulfillment for the award of the Degree of Bachelor of Technology in
CSE to the Jawaharlal Nehru Technological University is a record of bonafide work
carried out by him under my guidance and supervision.

The results embodied in this project report have not been submitted to any other
University or Institute for the award of any Degree or Diploma.

(Head of the Department) Guide Name

Designation

3
 ABSTRACT

Computerized Information System for Trade Tax enables a state

commercial taxation department to improve its services using IT. The software covers
various aspects of the working of the department.
The trade / commercial tax department is the organization that collects tax on the sale or
purchase of goods at a certain point of sale as well as purchase of goods throughout the
state. It may be divided into various zones, regions, circles, divisions or sectors to
facilitate better monitoring and control. To enforce the commercial tax laws and to
check tax evasion, there are several road check posts, railway check-posts, mobile
squads and special investigation branches.
The Internet revolution has been changing the fundamentals of our society. It shapes the
way we communicate and the way we do business. It brings us closer and closer to vital
sources of Information. It provides us with means to directly interact with service-
oriented computer systems tailored to our specific needs; therefore, we can serve
ourselves better by making our own decisions. The project deals with the trade tax web
application that uses data base logic to make a record of all the tax payers or the
registered members.

4
 CONTENTS
i. Introduction 6

ii. Software Requirement Specification 8

 Purpose of this Document

 System Analysis
 Software Requirements
 Hardware Requirements

iii. Literature Study 9

iv. Software Design 14

 Unified Modeling Language

 Use Case Diagram
 Class Diagram
 Sequence Diagram
 E-R diagram

v. Coding Templates 21
 Code for Updating Dealer’s Profile
 Data Base Design for Updating Dealers Profile
 Code For Entering Dealer’s Information
 Data Base Design for Entering Dealer’s Profile
 Code for Deleting Users Profile
vi. Testing 29
 Test Approach
 Test Plan
vii. Output Screens 34
viii. Conclusion 39
ix. Bibliography 40

5
1. INTRODUCTION

6
1. INTRODUCTION
1.1 INTRODUCTION TO TAX INFORMATION SYSTEM
1.1.1 DEALER INFORMATION SYSTEM
Handles the registration of dealers under commercial tax and central sales tax:
It registers dealers under commercial tax and central sales tax, effectively checks the
mandatory enclosures, and displays warnings Effectively tracks amendments in the
business details of dealers Issues duplicate registration certificates Monitors
cancellation of dealer registration Efficiently tracks transfer of dealers Keeps track of
unregistered dealers liable to pay tax Effectively maintains records of stocks of forms at
various offices, issues forms to dealers, and monitors forms lost and used. Issues show-
cause notices Generates an application status report for the monitoring of various
applications.

1.1.2 RETURNS PROCESSING SYSTEM

Takes on the task of returns filing and monitoring of defaulters:
Periodicity of returns filing can be fixed / changed at any time with a minimum of effort
Monitors filing of returns under different acts (VAT, SAT, ET, CST) Effectively
generates a defaulter list for monitoring dealers who have not filed returns Displays the
list of defaulters for reminders / advance tax notices Issues revenue recovery certificates
(RRC).

1.1.3 DEALER AUDITING SYSTEM

Controls the assessment of the dealers registered for trade tax and central sales tax:
Automatically generates and displays a list of dealers who are to be assessed Generates
hearing notices for assessment Assesses dealers on the basis of the returns filed
Effectively generates demand notices Monitors demand notices for compliance and
generates RRCs in case of non-compliance Effectively generates refund orders Adjusts
payments against any other demands or payment of refunds after adjustment Reassesses
dealers (on a request by the dealer or the authority).

7
1.1.4 LUXURY TAX SYSTEM
This module controls the registration of hoteliers under luxury tax:
Registers hoteliers under the law and issues registration certificates Generates penalty
notices in case of late registration Amends the registration details of the hotelier.Issues
duplicate certificates when hoteliers lose permanent certificates Transfer of hoteliers
Cancels registration when sought by hoteliers Cancels registration when sought by
various authorities Captures details of unregistered hoteliers Processes returns along
with challans Processes assessments and issues assessment orders and demand notices
Processes refund amounts in case of refunds Provides for appeals / revisions.

1.1.5 PROFESSIONAL TAX SYSTEM

Caters to the registration and monitoring of dealers under the Professional Tax Act:
Registers dealers under the Professional Tax Act (both as employers and persons)
Generates penalty notices in case of late registration or furnishing of false information
Issues amended registration certificates to dealers in cases of amendments Issues
duplicate registration certificates Cancels registration when sought by an employer or
person Efficiently detects unregistered employers or persons Effectively tracks dealers
shifting their place of work Efficiently tracks returns filed by dealers Assesses dealers
and issues demand notices or refund orders Monitors cases under appeal / revision.

1.1.6 INDUSTRIAL EXEMPTION SYSTEM

Deals with the exemptions given to dealers for starting new businesses:
Records and updates application details Identifies dealers eligible for exemptions
Provides an efficient method for verification of capping amounts and exemption period
at the time of filing returns Issues provisional / permanent certificates for exemption
deferment.

8
INTRODUCTION TO MODULES

 Administrator Module

 Dealer Module.

 Supervisor Module
We have front end communicating with back end which has a driver interface
between them and GUI components to interface with the user. For designing here we
use HTML and J2SE as front end and Orcal9i or higher as back end. The system works
by comparing the dates in the database with the current date of the server.

9
2. SYSTEM ANALYSIS

10
2. SYSTEM ANALYSIS
2.1 PROPOSED SYSTEM
Information System for Trade Tax is specially designed for
organization to keep track of employee leave –tracking. This system aims to reduce
the paper-work to track-down employee leave with accuracy and minimal fuss, thus
saving time and money.
Our Trade Tax can retrieve the latest information for employees leave application,
leave cancellation, entitlement updating and leave approval which are automated and
user-friendly with the information displayed for preparing reports, enquiries or
updating relevant details.
By using this system the employee can apply, approve, cancel, postpone and view
leave records at their finger tips at anytime, anywhere.

2.2 EXISTING SYSTEM

In early days we maintain Information of an employee in the form of registers. If we
want to retrieve information regarding their leaves and dates we have to refer to several
sets of registers. It was very time consuming and lengthy process .We needs to perform
manual upgrade whenever new features are added. It may lead to waste of time and
money.

2.3. FEASIBILITY STUDY

Literature Study is a compressed capsule version of scope and objectives is confirmed
and corrected and any constraint imposed on the systems are identified. Heuristics are
searched as analyzed for feasibility. To yield a successful to the organization that can be
obtained through efficient feasibility study. These are a number of feasibility studies to
be conducted by the three equally important tests of feasibility studies are:

 Technical Feasibility

 Operational Feasibility

 Economical Feasibility

11
2.3.1 TECHNICAL FEASIBILITY
Evaluating the technical feasibility is the trickiest part of a feasibility study. This is
because, at this point in time, not too many detailed design of the system, making it
difficult to access issues like performance, costs on (on account of the kind of
technology to be deployed) etc. A number of issues have to be considered while doing a
technical analysis.
1.Understand the different technologies involved in the proposed system before
commencing the project, we have to be very clear about what are the technologies those
are required for the development of new system.
2. Find out whether the organization currently possesses the required technologies is the
required technology available with the organization? If so is the capacity sufficient?
For instance – “Will the current printer be able to handle the new reports and forms
required for the new system?”

2.3.2 OPERATIONAL FEASIBILITY

Proposed projects are beneficial only if they can be turned into information
systems that will meet the organizations operating requirements. Simply stated, this test
of feasibility asks if the system will work when it is developed and installed. Are there
major barriers to Implementation? Here are questions that will help test the operational
feasibility of a project:
 Is there sufficient support for the project from management from users? If the
current system is well liked and used to the extent that persons will not be able
to see reasons for change, there may be resistance.
 Are the current business methods acceptable to the user? If they are not, users
may welcome a change that will bring about a more operational and useful
systems.
 Have the user been involved in the planning and development of the project?
Early involvement reduces the chances of resistance to the system and in
General and increases the likelihood of successful project.

12
Since the proposed system was to help reduce the hardships encountered in the existing
manual system, the new system was considered to be operational feasible.

2.3.3 ECONOMIC FEASIBILITY

Economic feasibility attempts 2 weigh the costs of developing and implementing
a new system, against the benefits that would accrue from having the new system in
place. This feasibility study gives the top management the economic justification for the
new system.
A simple economic analysis which gives the actual comparison of costs and
benefits are much more meaningful in this case. In addition, this proves to be a useful
point of reference to compare actual costs as the project progresses. There could be
various types of intangible benefits on account of automation. These could include
increased customer satisfaction, improvement in product quality better decision making
timeliness of information, expediting activities, improved accuracy of operations, better
documentation and record keeping, faster retrieval of information, better employee
morale.

13
3. SYSTEM REQUIREMENTS

14
3. SYSTEM REQUIREMENTS

3.1 HARDWARE REQUIREMENTS

 HDD : 20GB Min, 40GB Recommended

 RAM : 1GB Min
 Operating System : Windows XP with SP2 or Windows Vista

3.2 SOFTWARE REQUIREMENTS

 Operating System : Windows XP with SP2 or Windows Vista

 Database : MS-SQL server 2005
 Technologies : ASP.NET with C#.NET
 IDE : MS-Visual Studio .Net 2008
 Browser : Mozilla Firefox ,IE 6

3.3 WINDOWS OPERATING SYSTEM

Front-end : JSP, JAVA Script, HTML.
Model Layer : Struts, Servlets
Back-end : My SQL Database
Tools : My Eclipse, Dream weaver

15
4. SOFTWARE DESCRIPTION

16
4. SOFTWARE DESCRIPTION

INTRODUCTION TO JAVA

FEATURES OF JAVA
The inventors of java wanted to design a language which could offer
solution to some of the problems encountered in modern programming. They wanted
the language to be not only reliable, portable and distributed but also simple, compact
and interactive.

Sun Microsystems officially describes Java with the following

ATTRIBUTES:
 Compiled and Interpreted
 Platform _ Independent and Portable
 Object Oriented
 Robust and Secure
 Distributed
 Familiar, Simple and Small
 Multithreaded and Interactive
 High Performance
 Dynamic and Extensible

Although the above appears to be a list of buzzwords, they aptly describe the full
potential of the language. These features have made Java the first application
language of the World Wide Web. Java will also become the premier language for
general purpose stand_ alone applications.

17
Compiled and Interpreted

Usually a computer language is either compiled or interpreted. Java combines both

these approaches thus making Java a two _ stage system. First, Java compiler translates
source code into what is known as byte code instructions. Byte code are not machine
instructions and therefore, in the second stage, Java interpreter generates machine code
that can be directly executed by the machine that is running the Java program. We can
thus say that Java is both compiled and interpreted language.

Platform Independent and Portable

The most significant contribution of Java over other language is its portability. Java
programs can be easily moved from one computer system to another, anywhere and
anytime. Changes and upgrades in operating systems, processors and system resources
will not force any changes in Java programs. This is the reason why Java has become a
popular language for programming on Internet which interconnects different kinds of
systems worldwide.

Object Oriented

Java is a true object _ oriented language. Almost everything in Java is an object. All
program code and data reside within objects and classes. Java comes with an extensive
set of classes, arranged in packages, which we can use in our programs by inheritance.
The object model in Java is simple and easy to extend.

Robust and Secure

Java is a robust language. It provides many safeguards to ensure reliable code. It has
strict compile time and run time checking for data types. It is designed as a garbage
collected language relieving the programmers virtually memory management problems.
Java also incorporates the concept of exception handling which captures series errors
and eliminates any risk of crashing the system.

Distributed

Java is designed as a distributed language for creating applications on networks. It has

the ability to share both data and programs. Java applications can open and access
remote objects on Internet as easily as they can do in a local system. This enables

18
multiple programmers at multiple remote locations to collaborate and work together on
single project.

Simple, Small and Familiar

Java is a small and simple language. Many features of C and C++ that are either
redundant and source of unreliable code are not part of Java. For example, Java does not
use pointers preprocessor header files; go to statement and many others. It also
eliminates operator overloading and multiple inheritance. Familiarity is another striking
feature of Java. To make the language look familiar to the existing programmers, it was
modeled on C and C++ languages.

Multithread and Interactive

Multithreaded means handling multiple tasks simultaneously. Java supports

multithreaded programs. This means that we need not to wait for the application to
finish one task before beginning another. The Java runtime comes with tools that
supports multiprocessor synchronization construct smoothly running interactive
systems.

High Performance

Java performance is impressive for an interpreted language, Mainly due to

the use of intermediate byte code. According to Sun, Java speed is comparable to the
native C/C++. Java architecture is also designed to reduce overheads during runtime.
Further, the incorporation of multithreading enhances the overall execution speed of
Java programs.

Dynamic and Extensible

Java is dynamic language. Java is capable of dynamically linking in new class libraries,
methods, and objects. Java can also determine the type of class through a query,
making it possible to either dynamically link or abort the program, depending on the
response. Java programs support functions written in other language such as C and C++.
These functions are known as native methods. This facility enables the programmers to

19
use the efficient functions available in these languages. Native methods are linked
dynamically at runtime.

4.2. HTML

Hypertext Markup Language (HTML), the languages of the World Wide Web
(WWW), allows users to produces Web pages that include text, graphics and pointer to
other Web pages (Hyperlinks).

HTML is not a programming language but it is an application of ISO Standard

8879, SGML (Standard Generalized Markup Language), but specialized to hypertext
and adapted to the Web. The idea behind Hypertext is that instead of reading text in
rigid linear structure, we can easily jump from one point to another point. We can
navigate through the information based on our interest and preference. A markup
language is simply a series of elements, each delimited with special characters that
define how text or other items enclosed within the elements should be displayed.
Hyperlinks are underlined or emphasized works that load to other documents or some
portions of the same document.

HTML can be used to display any type of document on the host computer, which
can be geographically at a different location. It is a versatile language and can be used
on any platform or desktop.

HTML provides tags (special codes) to make the document look attractive.
HTML tags are not case-sensitive. Using graphics, fonts, different sizes, color, etc., can
enhance the presentation of the document. Anything that is not a tag is part of the
document itself.

4.3. JAVASCRIPT

JavaScript is a script-based programming language that was developed by Netscape

Communication Corporation. JavaScript was originally called Live Script and renamed
as JavaScript to indicate its relationship with Java. JavaScript supports the development
of both client and server components of Web-based applications. On the client side, it
can be used to write programs that are executed by a Web browser within the context of
a Web page. On the server side, it can be used to write Web server programs that can
process information submitted by a Web browser and then updates the browser’s display
20
accordingly

Even though JavaScript supports both client and server Web programming, we prefer
JavaScript at Client side programming since most of the browsers supports it.
JavaScript is almost as easy to learn as HTML, and JavaScript statements can be
included in HTML documents by enclosing the statements between a pair of scripting
tags

<SCRIPTS>... </SCRIPT>.

<SCRIPT LANGUAGE = “JavaScript”>

JavaScript statements

</SCRIPT>

Here are a few things we can do with JavaScript:

Validate the contents of a form and make calculations.

Add scrolling or changing messages to the Browser’s status line.

Animate images or rotate images that change when we move the mouse over them.

Detect the browser in use and display different content for different browsers.

Detect installed plug-ins and notify the user if a plug-in is required.

We can do much more with JavaScript, including creating entire application.

4.4. JDBC
Java Database Connectivity or in short JDBC  is a technology that enables
the java program to manipulate data stored into the database. Here is the complete
tutorial on JDBC technology.

1. What is JDBC?  
JDBC is Java application programming interface that allows the Java programmers to
access database management system from Java code. It was developed by Java Soft, a
subsidiary of Sun Microsystems.

21
JDBC has four Components:

1. The JDBC API.

2. The JDBC Driver Manager.
3. The JDBC Test Suite.
4. The JDBC-ODBC Bridge.

5. The JDBC API.

The JDBC application programming interface provides the facility for accessing the

relational database from the Java programming language. The API technology provides
the industrial standard for independently connecting Java programming language and a
wide range of databases. The user not only execute the SQL statements, retrieve results,
and update the data but can also access it  anywhere within a network because of  it's
"Write Once, Run Anywhere" (WORA) capabilities.

Due to JDBC API technology, user can also access other tabular data sources like
spreadsheets or flat files even in the a heterogeneous environment.  JDBC application
programming interface is a part of the Java platform that has included Java Standard
Edition (Java SE) and the Java Enterprise Edition (Java EE) in itself.

The JDBC API has four main interface:

The latest version of JDBC 4.0 application programming interface is divided into two
packages
i java.sql
ii javax.sql. 

Java SE and Java EE platforms are included in both the packages.

4.5. Java Server Pages (JSP)

Java server Pages is a simple, yet powerful technology for creating and
maintaining dynamic-content web pages. Based on the Java programming language,
Java Server Pages offers proven portability, open standards, and a mature re-usable
component model. The Java Server Pages architecture enables the separation of content
generation from content presentation. This separation not eases maintenance headaches;
it also allows web team members to focus on their areas of expertise. Now, web page
designer can concentrate on layout, and web application designers on programming,

22
with minimal concern about impacting each other’s work.

Features of JSP:
 Portability
 Components
 Processing
 Access Models

Steps in the execution of a JSP Application:

The client sends a request to the web server for a JSP file by giving the name of the JSP
file within the form tag of a HTML page.

This request is transferred to the JavaWebServer. At the server side JavaWebServer

receives the request and if it is a request for a jsp file server gives this request to the JSP
engine.

JSP engine is program which can understand the tags of the jsp and then it converts
those tags into a Servlet program and it is stored at the server side. This Servlet is
loaded in the memory and then it is executed and the result is given back to the
JavaWebServer and then it is transferred back to the result is given back to the
JavaWebServer and then it is transferred back to the client.

23
5. SYSTEM DESIGN

24
5. PROJECT DESCRIPTION

5.1 UNIFIED MODELING LANGUAGE

Unified Modeling Language (UML) is a standardized general-purpose modeling

language in the field of object-oriented software engineering. The standard is managed,
and was created by, the Object Management Group.

UML includes a set of graphic notation techniques to create visual models of object-

oriented software-intensive systems.

5.2 USE CASE DIAGRAM

A use case diagram in the Unified Modeling Language (UML) is a type of behavioral

diagram defined by and created from a Use-case analysis. Its purpose is to present a
graphical overview of the functionality provided by a system in terms of actors, their
goals (represented as use cases), and any dependencies between those use cases.

The main purpose of a use case diagram is to show what system functions are
performed for which actor. Roles of the actors in the system can be depicted.

Use cases
A use case describes a sequence of actions that provide something of measurable value
to an actor and is drawn as a horizontal ellipse.

Actors
An actor is a person, organization, or external system that plays a role in one or more
interactions with the system.

System boundary boxes

A rectangle is drawn around the use cases, called the system boundary box, to indicate
the scope of system. Anything within the box represents functionality that is in scope
and anything outside the box is not.

25
 5.2.1 USE CASE DIAGRAM FOR ADMINISTRATOR

Use Case Diagrams

1.Administrator

Login

Add,Del,up
dealer

Add,Del,up
Sup

View Report
Administrator
Payment

Generate

26
 5.2.1 USE CASE DIAGRAM FOR DEALER

2.Dealer

Register

Approval

Log in

Req For goods

Goods Shipper
Dealer
Submit

Complaint

5.2.1 USE CASE DIAGRAM FOR SUPERVISOR

3.Supervisor

Login

Req For Admin

Give The List

Tax Payment
Supervisor
Get Emp det

Submit

27
5.3 CLASS DIAGRAM
Class diagrams are widely used to describe the types of objects in a system and their
relationships.  Class diagrams model class structure and contents using design elements
such as classes, packages and objects. Class diagrams describe three different
perspectives when designing a system, conceptual, specification, and implementation. 
These perspectives become evident as the diagram is created and help solidify the
design.  This example is only meant as an introduction to the UML and class diagrams. 
If you would like to learn more see the Resources page for more detailed resources on
UML.
Classes are composed of three things: a name, attributes, and operations.  Below is an
example of a class.
5.3.1 SIMPLE CLASS DIAGRAM

Class diagrams also display relationships such as containment, inheritance, associations

and others.

5.3.2 CLASS DIAGRAM FOR ALL ADMIN, DEALER, SUPERVISOR

Class Diagram

Administrator Dealer
1…………*
- Logid - Logid
- password - password
+ Name

-CreateDealer()
- CreateSupervisor()
-AddDealer()
-DeleteDealer()
-AddSupervisor() Supervisor -ReqForAdmi()
-DeleteSupervisor()
-Report() - Logid -GiveTheList()
- password
-payment() -TaxPayment()
-Generator()
-GetEmpDetails()
-SubmitEmpSal()

- Register()
- Approval()
- reqforgoods()
- GoodsShipper()
- Submit()
- Complaint

28
5.4 SEQUENCE DIAGRAM
UML sequence diagrams are used to represent or model the flow of messages,
events and actions between the objects or components of a system. Time is represented
in the vertical direction showing the sequence of interactions of the header elements,
which are displayed horizontally at the top of the diagram.
Sequence Diagrams are used primarily to design, document and validate the
architecture, interfaces and logic of the system by describing the sequence of actions
that need to be performed to complete a task or scenario. UML sequence diagrams are
useful design tools because they provide a dynamic view of the system behavior, which
can be difficult to extract from static diagrams or specifications.
Although UML sequence diagrams are typically used to describe object-oriented
software systems, they are also extremely useful as system engineering tools to design
system architectures, in business process engineering as process flow diagrams, as
message sequence charts and call flows for telecom/wireless system design, and for
protocol stack design and analysis.

5.4.1SEQUENCE DIAGRAM FOR ADMIN

Sequence
Log in Dealer Supervisor Report Payment Generate

Log in Add,
Update
Dealer

Add,del
Administrator Supervisor

View
Report

Payment

Generate

5.4.2 SEQUENCE DIAGRAM FOR DEALER

29
 Register Approval Log in For Goods Goods & Sup Submit

Register

Approv

Dealer Log in

For Goods

Goods
And Sup

Submit

5.5 ER DIAGRAMS
The entity Relationship Diagram (ERD) depicts the relationship between the data
objects. The ERD is the notation that is used to conduct the date modeling activity the
attributes of each data object noted is the ERD can be described resign a data object
descriptions.
The set of primary components that are identified by the ERD are

 Data object
 Relationships
 Attributes
 Various types of indicators.

The primary purpose of the ERD is to represent data objects and their relationships.

30
 5.5.1 ER DIAGRAM FOR ADMINISTRATOR

E R Diagram :
1.Administrator Tax-name
Assigned By
Invoice Tax
Amount

Super-id Super-name
Submit Payment Tax

Administrator Response Supervisor

Dealer-Id Dealer-name Super-id Super-name

maintains

Complaints
Payment
Dealer Payment

Report Dealer-id

5.5.2 ER DIAGRAM FOR DEALER

2.Dealer Tax-name
Tax-id

Tax
Assigned by

Dealer-name Dealer-id Product-id

view

Dealer Order products

Amount Product-name
Payment Report Requests

payment
Super-id
supervisor

Tax
Super-name

31
 5.5.3 ER DIAGRAM FOR SUPERVISOR

3.supervisor

Super-name Super-id Tax-id Tax-name

Supervisor creates tax

payment Tax assigned by

32
6. SOURCE CODE

33
6. CODING TEMPLATES
6.1 CODE FOR UPDATING DEALERS PROFILE
<%--
Document : update
Created on: May 20, 2011, 10:39:49 PM
Author : MySyS
--%>
<%@page import="java.util.*" %>
<%@page import="java.sql.*" %>
<%@page content Type="text/html" page Encoding="UTF-8"%>
<! DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Update</title>
</head> <body>
<% String s1=request.getParameter("fname");
String s2=request.getParameter("lname");
String s3=request.getParameter("uname");
String s4=request.getParameter("pass");
String s5=request.getParameter("rpass");
String s6=request.getParameter("phone");
String s7=request.getParameter("mobile");
String s8=request.getParameter("email");
String s9=request.getParameter("address");
String s10=request.getParameter("city");
String s11=request.getParameter("state");
String s12=request.getParameter("count");
String s13=request.getParameter("bname");
String s14=request.getParameter("bloc");

34
 String s15=request.getParameter("bphone");
String s16=request.getParameter("bmail");
String s17=request.getParameter("badd");
RequestDispatcher rd=request.getRequestDispatcher("home.jsp");
try
{
Class.forName("oracle.jdbc.driver.OracleDriver");
Connection
con=DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe","system","ai
shu");
Statement stm=con.createStatement();
PreparedStatement pt=con.prepareStatement("update tradetax4 set
lname='"+s2+"',uname='"+s3+"',
pass='"+s4+"',rpass='"+s5+"',phone='"+s6+"',mobile='"+s7+"', email='"+s8+"',
address='"+s9+"' ,city='"+s10+"' ,state='"+s11+"' ,count='"+s12+"' ,bname='"+s13+"'
,bloc='"+s14+"' ,bphone='"+s15+"' ,bmail='"+s16+"' ,badd='"+s17+"' where
fname='"+s1+"'");
// PreparedStatement pt=con.prepareStatement("update tradetax4 set
email='"+s8+"' where fname='"+s1+"'");
int n=pt.executeUpdate();
if(n!=0)
out.println("<h1>insert success</h1>");
else
out.println("<h1>insert failure</h1>");

}
catch(Exception e)
{
out.println("<h1>error has occured"+e+"</h1>");
} %> </body> </html>

35
6.1.1 DATA BASE TABLE FOR UPDATING DEALER’S PROFILE
Field Type Size Constraint Description
Fname Varchar 20 Primary key First name
Lname Varchar 20 Not null Last name
Uname Varchar 20 Not null User name
Pass Varchar 20 Not null password
Rpass Varchar 20 Not null Repeat
password
Phone Number 20 Not null Phone num
Mobile Number 20 Not null Mobile
Email Varchar 30 Not null Email id
Address Varchar 30 Not null Address
City Varchar 20 Not null City
State Varchar 20 Not null State
Count Varchar 20 Not null Country
Bname Varchar 20 Not null Business n
Bloc Varchar 20 Not null Business
location
Bphone Number 20 Not null Business phone
Bmail Varchar 30 Not null Business mail
Badd Varchar 30 Not null Business
address

6.2 CODE FOR ENTERING DETAILS/REGISTERING(PL/SQL)

<%--
Document : regmember
Created on : May 18, 2011, 6:44:23 PM
Author : sandeep

36
 --%>
<%@page import="java.util.*" %>
<%@page import="java.sql.*" %>
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>Register</title>
</head>
<body background="blackboard-1024-x-768.jpg">
<%
String fname=request.getParameter("fname");
String lname=request.getParameter("lname");
String uname=request.getParameter("uname");
String pass=request.getParameter("pass");
String rpass=request.getParameter("rpass");
String phone=request.getParameter("phone");
String mobile=request.getParameter("mobile");
String email=request.getParameter("email");
String address=request.getParameter("address");
String city=request.getParameter("city");
String state=request.getParameter("state");
String count=request.getParameter("count");
String bname=request.getParameter("bname");
String bloc=request.getParameter("bloc");
String bphone=request.getParameter("bphone");
String bmail=request.getParameter("bmail");
String badd=request.getParameter("badd");
try

37
 {
Class.forName("oracle.jdbc.driver.OracleDriver");
Connection
con=DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe","system","ai
shu");
PreparedStatement pt=con.prepareStatement("insert into dealog
values(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)");
PreparedStatement pt1=con.prepareStatement("insert into deareg values(?,?)");
pt.setString(1,fname);
pt.setString(2,lname);
pt.setString(3,uname);
pt.setString(4,pass);
pt.setString(5,rpass);
pt.setString(6,phone);
pt.setString(7,mobile);
pt.setString(8,email);
pt.setString(9,address);
pt.setString(10,city);
pt.setString(11,state);
pt.setString(12,count);
pt.setString(13,bname);
pt.setString(14,bloc);
pt.setString(15,bphone);
pt.setString(16,bmail);
pt.setString(17,badd);
pt1.setString(1,uname);
pt1.setString(2,pass);
int m=pt1.executeUpdate();
int n=pt.executeUpdate();
if(n>0&&m>0)
{
out.println("<h1 color='white' align='center'> success</h1>");
38
 RequestDispatcher rd=request.getRequestDispatcher("show.jsp");
rd.include(request,response);
}
Else
out.println("<h1>insert failure</h1>");
}
catch(Exception e)
{
out.println("<h1>error has occured"+e+"</h1>");
}
%>
</body>
</html>

6.2.1 DATABASE FOR ENTERING DETAILS

Field Type Size Constraint Description
Fname Varchar 20 Primary key First name
Lname Varchar 20 Not null Last name
Uname Varchar 20 Not null User name
Pass Varchar 20 Not null password
Rpass Varchar 20 Not null Repeat
password
Phone Number 20 Not null Phone num
Mobile Number 20 Not null Mobile
Email Varchar 30 Not null Email id
Address Varchar 30 Not null Address
City Varchar 20 Not null City
State Varchar 20 Not null State
Count Varchar 20 Not null Country
Bname Varchar 20 Not null Business n
Bloc Varchar 20 Not null Business
location
Bphone Number 20 Not null Business phone
Bmail Varchar 30 Not null Business mail
Badd Varchar 30 Not null Business
address

39
6.3 CODE FOR DELETING USER FROM DATA BASE
<%--
Document : delete
Created on : May 21, 2011, 11:51:47 AM
Author : My SyS
--%>
<%@page import="java.util.*" %>
<%@page import="java.sql.*" %>
<%@page contentType="text/html" pageEncoding="UTF-8"%>
<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>delete</title>

</head>
<body>
<%
String Value = request.getParameter("uname");
try{
Class.forName("oracle.jdbc.driver.OracleDriver");
Connection
con=DriverManager.getConnection("jdbc:oracle:thin:@localhost:1521:xe","system","ai
shu");
Statement stm=con.createStatement();
String Query = "Delete from supereg where uname='"+Value+"'";
int result = stm. executeUpdate(Query);
if( result > 0)
{
out.println("Deleted from the database sucessfully");

40
 RequestDispatcher rd=request.getRequestDispatcher("delsuper.jsp");
rd.include(request,response);
}
else
{
out.println("Deletion not done..please try again");
RequestDispatcher
rd=request.getRequestDispatcher("showsuper.jsp");
rd.include(request,response);
}
}
catch(Exception e)
out.println("Error"+e+" please try again");
}
%>
</body>
</html>

41
 8. SYSTEM TESTING

7. TESTING
Testing is a process of executing a program to find out errors. If testing is
conducted successfully, it will uncover all the errors in the software. Any testing
can be done basing on two ways:
7.1.1 WHITE BOX TESSTING

It is a test case design method that uses the control structures of the
procedural design to derive test cases. using this testing a software Engineer can
derive the following test cases:

42
Exercise all the logical decisions on either true or false sides. Execute all
loops at their boundaries and within their operational boundaries. Exercise the
Internal data structures to assure their validity.

7.1.2 Black Box Testing

It is a test case design method used on the functional requirements of the software.
It will help a software engineer to derive sets of input conditions that will exercise
all the functional requirements of the program. Black Box testing attempts
to find errors in the following categories:

Incorrect or missing functions

Interface errors
Errors in data structure
Performance errors
Initialization and termination errors

By black box testing we derive a set of test cases that satisfy the following criteria:
Test cases that reduce by a count that is greater than one, the number of additional test
cases that must be designed to achieve reasonable testing.
Test cases that tell us something about the presence or absence of classes of errors
rather than errors associated only with a specific test at hand.

7.2 TEST APPROACH

7.2.1 REQUIREMENT SPECIFICATION TEST PHASE TABLE

No. Requirement Essential Description of the Remarks
Or Requirement
Desirable
RS1 The system should have a Essential A login box should The logins are
login appear when the system assigned by
is invoked. the mail-

43
 admin
RS2 The system should ‘lock’ Desirable This feature will Since the
the login id if wrong improve the robustness application is
password is entered 3 of the application going to be
times in a row used only by
the employees
of the
organization,
this feature is
not essential.

7.3 TEST PLAN(TP)

The test-plan is basically a list of test cases that need to be run on the system. Some of
the test cases can be run independently for some components (report generation from
the database, for example, can be tested independently) and some of the test cases
require the whole system to be ready for their execution. It is better to test each
component as and when it is ready before integrating the components. It is important to
note that the test cases cover all the aspects of the system .

7.3.1 TABLE FOR TEST PLAN SPECIFICATION

No. Test case Title Description Expected The Result
Outcome requirement
in RS that is
being tested
1 Successful The login to the Login RS1 Passed
User system should be should be
Verification tried with the login successful
assigned by the and the user
admin and the should
correct password enter in to
44
 the system
2 Unsuccessful Login to the system Login RS1 Passed
User with a wrong should fail
Verification password with an
due to wrong error
password ‘Invalid
Password’
3 Unsuccessful Login to the system Login RS1 Passed
User with a invalid login should fail
Verification id with an
due to invalid error
login id ‘Invalid
user id’

45
46
7. OUTPUT SCREENS

7.1 LOGIN PAGE FOR DEALER

7.2 DEALER PAGE

47
7.3 DEALER REGISTRATION PAGE

7.4 SUPERVISOR REGISTRATION PAGE

48
7.5 PRODUCT LIST PAGE

49
7.6 ADD PRODUCT PAGE

7.7 ADMIN LOGIN PAGE

50
7.8 ADMIN PAGE

7.9 SUPERVISOR LOGIN PAGE

51
7.10 SUPERVISOR PAGE

52
8. CONCLUSION

53
8. Conclusion

The Information System For trade Tax is an intranet based application that can be
accessed throughout the organization or a specified group or department. This system
can be used to automate the work flow of leave applications and their approvals. There
are features like e-mail notifications, cancellation of leave ,automatic approval of leave,
report generators etc in this system. This system is important to any kind of an
organization .

54
 9. BIBILIOGRAPHY

9. Bibiliography

55
 Books

· The Complete Reference JAVA2

- Patric Naughton Herebet Schildt.

· Internet & World Wide Web

- H.M. Deitel , P.J Deitel , T.R. Nieto .

· JAVA Data base Programming with JDBC

-Pratik Patel, Karl Moss.

 Software Engineering

-Pressmen

 Web programming

-Chris Bates

SITES

· www.javadevelopers.com

· www.w3schools.com

· www-128.ibm.com/developerworks/web/library/wa-dbdsgn1.html

· www-128.ibm.com/developerworks/webservices/library/co-

design6.html

56