DIGITAL SOLUTION TO COMBAT BRIBERY AND

JUSTICE RESTORATION SYSTEM

A MINI PROJECT REPORT

Submitted by

P.NISCHAL (Regd.No.19891A1242)
E.SHIVARAM (Regd.No.19891A1223)
B.RAJASREE (Regd.No.19891A1211)
CH.TAPASWI (Regd.No.19891A1220)

Under the guidance of

Dr. M. PRABHAKAR
Assistant Professor

in partial fulfillment for the award of the degree of

BACHELOR OF TECHNOLOGY
in
INFORMATION TECHNOLOGY

DECEMBER,2022
 DECLARATION

We hereby declare that project entitled ―Digital Solution to Combat Bribery and Justice
Restoration System ‖ is bonafide work duly completed by us. It does not contain any part of
the project or thesis submitted by any other candidate to this or any other institute of the
university.

All such materials that have been obtained from other sources have been duly acknowledged.

P.NISCHAL
(Regd.No.19891A1242)

E.SHIVARAM
(Regd.No.19891A1223)

B.RAJASREE
(Regd.No.19891A1211)

CH.TAPASWI
(Regd.No.19891A1220)

i
 DEPARTMENT OF INFORMATION TECHNOLOGY
CERTIFICATE

This is to certify that the thesis work titled―”Digital Solution to Combat Bribery
and Justice Restoration System” submitted by P.Nischal(reg.no.19891A1242),E.Shivaram
(reg.no.19891A1223), B.Rajasree(reg.no.19891A1211), CH.Tapaswi(reg.no.19891A1220), in
partial fulfillment of the requirements for the award of the degree of Bachelor of Technology
in Information Technology to the Vignan Institute of Technology And Science, Deshmukhi
is a record of bonafide work carried out by them under my guidance and supervision.

The results embodied in this project report have not been submitted in any university for the
award of any degree and the results are achieved satisfactory

Dr. M. PRABHAKAR Prof. B.V. CHOWDARY

Assistant Professor Professor & Head of the
Department
Guide Information Technology

External Examiner

ii
 ACKNOWLEDGEMENT

Every project big or small is successful largely due to the effort of a number of
wonderful people who have always given their valuable advice or lent a helping hand. We
sincerely appreciate the inspiration; support and guidance of all those people who have been
instrumental in making this project a success.

We thank our beloved Chairman, Dr. L Rathaiah Sir, who gave us great
encouragement to work.

We thank our beloved CEO, Mr. Boyapati Shravan Sir, we remember him for his
valuable ideas and facilities available in college during the development of the project.

We convey our sincere thanks to Dr. G Durga Sukumar Sir, Principal of our
institution for providing us with the required infrastructure and a very vibrant and supportive
staff

We would like to thank our Head of the Department of Information Technology

Prof.B.V.Chowdary a distinguished and eminent personality, whose strong recommendation,
immense support and constant encouragement has been great help to us. We intensely thank
him for the same.

We would like to express our sincere appreciations to our project coordinator

Mrs.G.Sirisha for guidance , continuous encouragement and support during the project.

We would like to thank our guide of the project, Dr.M.Prabhakar (Assistant

Professor) who has invested his full effort in guiding the team in achieving the goal.

Special thanks go to my team mates, who helped me to assemble the parts and gave
suggestions in making this project. We have to appreciate the guidance given by other
supervisor as well as the panels especially in our project presentation that has improved our
presentation skills thanks to their comment and advice's. We take this opportunity to thank all
our lecturers who have directly or indirectly helped our project. We pay our respects and love to
our parents and all other family members and friends for their love and encouragement
throughout our career.

iii
 ABSTRACT

With our aim to fight against bribery, we seek Digital Solution to Combat Bribery & Justice
Restoration System for better policing and improved public delivery system. Solution should (1)
Provide efficient ways of public delivery system for combating bribery (2) Reporting bribery
incidences to authorities. This Application will help the common people to register complaint against
bribery through a web application in a short period of time. The existing Handling System is not
centralized, it is manual approach, and user has to call to authorities to register their complaints, so
the communication between authorities is not fast. This proposed application provides an interface to
register one’s complained and follow it up. Users can upload the videos, images or audio files as
evidence. If complaint is once registered, will be send to specific Investigation department by admin.
The proposed application makes the communication between different investigation departments to
complete with in less amount of time.

iv
 LIST OF TABLES AND FIGURES

Fig 1: Waterfall model diagram……………...……………….

……………………………….14
Fig 2: Technical architecture of project……...…………………………………………….
….19
Fig 3:
Essential elements of class diagram……...……………...
……………………………………...22
Fig example
3.1:of dependency relation……......
……………………………………………..23
Fig 3.2 : example of generalization relation…..…………...……………………………….…
23
Fig 3.3: example of association relation.……..
……………………………………………...23
Fig 4 : Class Diagram………………………………..………………………………………………..23
Fig 4.1 : Sequence Diagram……………………..…...............................................…………
24
Fig 4.2 : Deployment Diagram .…………………..
………………………………………….25
Fig 4.3 : example of use case diagram……………….……………………………….………26
Fig 4.4: Use case diagram…………………………...….…………………………………….27
Fig 5: Database table for user information…………………………………………….….
…..29
Fig 5.1: Database table for admin information…………...….
………………………………..29
Fig 6: Activity Diagram……………………………………...……………………………….…
32
Fig 7: Block Diagram ………………………………………........................................................……33
Fig 8: Programming-1………………………………………………………………….
…….37
Fig 8.1: Programming-2……………………………….…...............................................……
38
Fig 8.2 : Java IDE………………………………………….…………………………………38
Fig 8.3: Java Platform ………………………………………..………………………………39
Fig 9 : Table for test
cases…………………………………………………………………….50
Fig 10: Login page ……………………………………………………………………………………
51

v
Fig 10.1 : user registration
page………………………………………………………………………..51
Fig 10.2 : View complaint page
………………………………………………………………………..52
Fig 10.3:Update complaint
page……………………………………………………………………….52
Fig 10.4:User complaint view page…………………………………………………………………....53
Fig 10.5 : user registration
page………………………………………………………………………..53

vi
TABLE OF CONTENTS

ACKNOWLEDGEMENT.........................................................................................................…Ⅲ
ABSTRACT.................................................................................................................................…Ⅳ
1. INTRODUCTION……………………………………………………...……………………1
1.1. Purpose of the system……………………………………………………………..…………………2
1.2. Scope……………………………………………………………………………..……………….....3
2. LITERATURE SURVEY……………………………………………………...…………...4
3. SYSTEM ANALYSIS………………………………………………………………...…….7
3.1. Existing System……………………………………………………………………...…….7
3.1.1. Disadvantages of Existing System………………………………………………………7
3.2. Proposed System…………………………………………………………………………...8
3.2.1. Advantages of Proposed System………………………………………………...……....8
3.3. Software Requirement Specification……………………………………………………...12
3.3.1 Hardware Requirements………………………………………………………………...16
3.3.2. Software Requirements..................................................................................................16
4. SYSTEM DESIGN................................................................................................................20
4.1. Introduction........................................................................................................................20
4.2. Data Flow Diagrams...........................................................................................................21
4.3. UML Diagrams...................................................................................................................22
4.3.1. Class Diagram.................................................................................................................23
4.3.2. Sequence Diagram.........................................................................................................24
4.3.3. Deployement Diagram...................................................................................................25
4.3.4. Use Case Diagram..........................................................................................................27
4.3.5. Activity Diagram...........................................................................................................32
4.3.6. Block Diagram..............................................................................................................33
5. SYSTEM IMPLEMENTATION.........................................................................................35

vii
 5.1. Modules..............................................................................................................................35
5.1.1 Module Description..........................................................................................................35
5.2. Java Technology.................................................................................................................36
5.2.1. Classes involved..............................................................................................................41
6. RESULTS & DISCUSSION................................................................................................51
6.1.1. Login interface............................................................................................................................ 51
6.1.2. user registration page.................................................................................................................. 51
6.1.3. View complaints.........................................................................................................................52
6.1.4. Extracting Real Images............................................................................................................... 69
6.1.5. Extracting Fake Images...............................................................................................................70
6.1.6. Training the Model..................................................................................................................... 71
6.1.7. Training Graph – Plot.png...........................................................................................................71
7. CONCLUSION....................................................................................................................54
8. FUTURE SCOPE.................................................................................................................55
REFERENCES…………………................................................................................................56

viii
 1.INTRODUCTION

The purpose of the Digital Solution to Combat Bribery & Justice Restoration System is to
assist the responsible coordinating body to meet the national / international standards required
for the fight against bribery . The Digital Solution to Combat Bribery & Justice Restoration
System provides the necessary IT support for the management of an anti-bribery action plan,
anti-bribery measures, anti-bribery activities and the source of funding of those activities.

As this system provides an total online based process starting from complaint posting to
complaint result. Every update will be received by the complaint raiser via email, hence there
will be no lack of communication. Hence, the online complaint system will make the user to
deal with the complaint without any interaction with the organization or any form of
interaction. Those the user ,admin, employee this three also no need of any interaction. This
system is very user friendly and very interactive for the user and organizational employee.

Thus, as you can see from the definition, there are some defining characteristics of
this System:

 It is interactive with the end user.

 Gives an best and safe approach for a user to access their confidential information or
applications.

 The system will make complaints easier to coordinate, monitor, track and resolve.

 The system provides an online way of resolving problems.

 Prevents unauthorized users from accessing the private data.

1
 Range of Expertise Includes:

 Software Development Services

 Engineering Services
 Systems Integration
 Customer Relationship Management
 Product Development
 Electronic Commerce
 IT Outsourcing

We apply technology with innovation and responsibility to achieve two broad objectives:

 Effectively address the business issues our customers face today.

 Generate new opportunities that will help them stay ahead in the future.

1.1 Purpose of the System:

 To provide flexibility to the users, the interfaces have been developed that are accessible
through a browser. The top level GUI have been used to implement this project

 Digital Solution to Combat Bribery & Justice Restoration System is a capstone project that is
design to serve as a platform to address complaints and resolve disputes.

 The system provides an online way of resolving problems faced by the public or people
within the organization.

 The system will make complaints easier to coordinate, monitor, track and resolve. The
existing way of managing complaints are done manually and involve loads of paper works.

 The conventional way is time consuming for both the complainant and those who attend to
the complaints.

 Complaints are hard to manage, monitor and resolve. The existing manual way is
considered as inefficient especially in responding quickly to the complaint. Filing and
addressing the complaint takes a lot of time and effort for both parties.

2
1.2 Scope

The aim of this project is to reduce the bribery that is happening in the society by changing to
digital. When we do a transaction digitally it will be legal and countable. In government
offices even nowadays the bribery is going on through money in physical form. To reduce
that we developed an application by using Java technology in Eclipse this provides user an
interface to compliant against the corrupted persons with the proof.

To address the problems encountered in manually managing the complaint, the researchers of
this study design and develop an digital solution to combat bribery & justice restoration
system to eliminate the existing manual system of complaint management. The digital
solution to combat bribery & justice restoration system is an effective tool to handle
complaints, determine target problem areas and resolve problems. Digital Solution to Combat
Bribery & Justice Restoration System is a tool in assessing, analyzing and responding to
user’s complaints mostly customer complaints.

The proposed database driven application can be applied to various organizations such as the
academic institution, business organization, local government units and many more. Database
system is very vital to the success of the organization’s processes. Digital Solution to Combat
Bribery & Justice Restoration System is an example of a database system that organizes the
records in terms of customer or stakeholders complaints and queries.

3
 1. LITERATURE SURVEY

Reference 1:

Title: ‘‘E-government and access to information’’.

Author: Bhatnagar, S.

Description: The government's use of technology, particularly web-based Internet

applications to enhance the access to and delivery of government information and service to
citizens, business partners, employees, other agencies, and government entities.

Reference 2:

Title: “E-government, transparency and anti-corruption”.

Author: Zhang, Z.

Description: Today, E-government's potential to increase transparency and combat corruption

in government administration is gaining popularity in communities of e-government
practitioners and researchers. Based on their experiences and literature, we study the E-
government measures to combat corruption in China. This paper firstly illustrates the
corruption in today China and the relation among E-government, transparency and anti-
corruption and tries to find out the main causes of the corruption today in China. To fight and
stand against the crime ,they developed this system to provide justice for the people.

4
Reference 3:

Title: “Online anti-corruption tools in Latin America”.

Author: Matheus, R. and Ribeiro, M.M.

Description:  The study highlights experiences of several Latin American countries that have
opted to implement the anti-corruption web as a tool for fighting corruption. We will study
and compare these cases to identify what level of effectiveness this tool achieved in terms of
expansion of interaction spaces and participatory involvement of social actors against the
corruption.

Reference 4:

Title: “Combating corruption through e-governance in public service delivery system”.

Author: Singla, S. and Aggarwal, H.

Description: It has been observed that the primary objective of different e-governance
projects was to provide services and information to the people and organizations. Both of
them have been successful curbing or reducing the corruption by providing the transparency
in service delivery system. The present study is in depth analysis of some successful e-
governance projects implemented in Punjab. This study shows that E-Governance projects
resulted in elimination of corruption totally or substantially in many of the places. This
reduction in corruption has resulted in efficient public delivery system leading to uplifting the
poor and improving transparency. Hence, this research proves that e-governance can be an
anti corruption weapons for the development of transparent public delivery system in Punjab.

5
Reference 5:

Title: “The role of ICTs in reducing administrative corruption in the South African public
sector”.

Author: Habtemichael, F. and Cloete, F.

Description: Issues, such as fraud and corruption, emanating from lack of transparency and
accountability in public administration are receiving considerable attention. Public funds
management is an area of concern as public funds are prone to misuse if proper control
mechanisms are not in place. A number of suggestions are found in the literature on how to
prevent or reduce public funds misuse including curbing corrupt behaviour.

6
 2. SYSTEM ANALYSIS

This part of our project documentation focuses on existing system, proposed system,
advantages of proposed system, modules in the project along with their description and the
system requirements.

3.1. Existing System:

The Handling System is not centralized, it is manual approach, and user has to call to
authorities to register their complaints, so the communication between authorities is not fast.
The conventional way of storing the information is not secure as there is the possibility of
loss of the records, while retrieving any information to cross check the data takes too much
time.

3.1.1. Disadvantages of Existing System:

• Consume more time.
• There is a chance of fake complaints.
• Too much paper work.
• Errors during data entry and expensive.

7
 3.2. Proposed System:

This application provides an interface to register one’s complained and follow it up. Users
can upload the videos, images or audio files as evidence. If complaint is once registered, will
be send to specific Investigation department by admin. The proposed application makes the
communication between different investigation departments to complete with in less amount
of time. While it will provide the status of grievance of people and notify once it will
complete or user can track their complaints easily.

3.2.1. Advantages of Proposed System:

• Consumes less time.

• Result can be known quickly.
• No chance for fake complaints.
• We can access from anywhere.

8
Requirements Analysis

The minimum requirements of the project are listed below:

 Examine the tools and methodologies required to gain an overview of the system
requirements for the proposed database.

 Examine suitable database management systems that can be used to implement the
proposed database.

 Evaluate appropriate website authoring and web graphic creation tools that can be
used to develop web based forms for the proposed database

 Produce and apply suitable criteria for evaluating the solution

FUNCTIONAL REQUIREMENTS:

Functional requirement should include function performed by a specific screen outline work-
flows performed by the system and other business or compliance requirement the system
must meet.

Functional requirements specify which output file should be produced from the given file
they describe the relationship between the input and output of the system, for each functional
requirement a detailed description of all data inputs and their source and the range of valid
inputs must be specified.

The functional specification describes what the system must do, how the system does it is
described in the design specification.

If a user requirement specification was written, all requirements outlined in the user
requirements specifications should be addressed in the functional requirements.

 Registration
 Login
 Post Complaint
 View Complaint
 Update Complaint
 Report Complaint

9
NON-FUNCTIONAL REQUIREMENTS:

Describe user-visible aspects of the system that are not directly related with the functional
behavior of the system. Non-Functional requirements include quantitative constraints, such as
response time (i.e. how fast the system reacts to user commands.) or accuracy (i.e. how
precise are the systems numerical answers.).

 Performance: Performance is measured in terms of output provided by the web

application i.e., it will give response to the end user on the client system within very
short time.

 Accuracy: The data provided in the website is accurate.

 Security: Only users who are logged in can access the data . They can only view and
download files but cannot perform any modifications on them.

 Usability: Admin can upload and users can download the files easily.

UI Requirements

Administrative user interface: The ‘administrative user interface’ concentrates on the

consistent information that is practically, part of the organizational activities and which needs
proper authentication for the data collection. These interfaces help the administrators with all
the transactional states like Data insertion, Data deletion and Date updating along with the
extensive data search capabilities.

The operational or generic user interface: The ‘operational or generic user interface’ helps the
end users of the system in transactions through the existing data and required services. The
operational user interface also helps the ordinary users in managing their own information in
a customized manner as per the included
Flexibilities. This application consists following modules.

10
Design Requirements:

User Interface Design

The user interface is designed using Adobe Dreamweaver CS3. The complete website focuses
more on efficiency in understanding the IVR rather than the look and feel of the system as the
system is primarily developed for the blind people to whom the look and feel won’t be of that
primary importance as the efficiency of understanding the prompting would be.

Database Design

Our system maintains a database for user validation and storing complaints of the user. There
are a total of five tables. The Users, Employees, Complaints, Login and Status

11
3.3. Software Requirement Specification:

What is SRS?

Software Requirements Specification (SRS) is the starting point of the

software developing activity. As system grew more complex it became evident that the goal
of the entire system cannot be easily comprehended. Hence the need for the requirement
phase arose. The software project is initiated by the client needs. The SRS is the means of
translating the ideas of the minds of clients (the input) into a formal document (the output of
the requirement phase).

The SRS phase consists of two basic activities:

Problem/Requirement Analysis:

The process is order and more nebulous of the two, deals with understand the problem, the
goal and constraints.

Requirement Specification:

Here, the focus is on specifying what has been found giving analysis such as representation,
Specification languages and tools, and checking the specifications are addressed during this
activity.

The requirement phase terminates with the production of the validate SRS document.
Producing the SRS document is the basic of this phase.

Role of SRS:

The purpose of the SRS is to reduce the communication gap between the clients and the
developers. SRS is the medium though which the client and user needs are accurately
specified.

It forms the basis of software development. A good SRS should satisfy all the parties
involved in the system.

Purpose:

The purpose of this document is to describe all external requirements for the Complaint
Management System. It also describes the interfaces for the system.

12
Scope:

This document is the only one that describes the requirements of the system. It is meant for
the use by the developers, and will also by the basis for validating the final deliver system.
Any changes made to the requirements in the future will have to go through a formal change
approval process. The developer is responsible for asking for clarifications, where necessary,
and will not make any alternations without the permission of the client.

Overview:

The SRS begins the translation process that converts the software Requirements into the
language the developers will use. The SRS draws on the Use Cases from the user
Requirement Document and analyses the situations from a number of perspectives to discover
and eliminate inconsistencies, ambiguities and omissions before development progresses
significantly under mistaken assumptions.

Proposed System UI Architecture:

The proposed system is built around conventional three-tier architecture. The

three-tier architecture for web development allows programmers to separate various aspects
of the solution design into modules and work on them separately. That is, a developer who is
best at one part of development, say UI development need not worry about the
implementation levels so much. It also allows for easy maintenance and future enhancements.
The three-tiers of the solution include:

 The web-tier: This tier is at the uppermost layer and is closely bound to the user, i.e., the
users of the system interact with it through this tier.

 The business-tier: This tier is responsible for implementing all the business rules of the
organization. It operates on the data provided by the users through the web-tier and the
data stored in the underlying data-tier. So in a way this tier works on data from the web-
tier and the data-tier in order to perform task for the users in agreement with the business
rules of the organization.

 The data-tier: This tier contains the persist able data that is required by the business tier
to operate on. Data plays a very important role in the functioning of any organization.
Thus, persisting of such data is very important. The data tier performs the job of
persisting the data.

13
Life Cycle Models and Methodologies:

Waterfall Model

Description:

The Waterfall Model is a linear sequential flow. In which progress is seen as flowing steadily
downwards (like a waterfall) through the phases of software implementation. This means that
any phase in the development process begins only if the previous phase is complete. The
waterfall approach does not define the process to go back to the previous phase to handle
changes in requirement. The waterfall approach is the earliest approach and most widely
known that was used for software development.

Fig 1: waterfall model

The usage

Projects which not focus on changing the requirements, for example, projects initiated from
request for proposals (RFPs), the customer has a very clear documented requirements

14
Advantages and Disadvantages:

Advantages:

 Easy to explain to the users.

 Structures approach.
 Stages and activities are well defined.
 Helps to plan and schedule the project.
 Verification at each stage ensures early detection of errors/misunderstanding.
 Each phase has specific deliverables.

Disadvantages:

 Assumes that the requirements of a system can be frozen.

 Very difficult to go back to any stage after it finished.

 A little flexibility and adjusting scope is difficult and expensive.

 Costly and required more time, in addition to the detailed plan.

15
3.3.1 Hardware Requirements:
 Hardware : Pentium

 RAM : 1GB

 Hard disk : 20 GB

Additional Tools:

 HTML Designing : Dream weaver Tool

 Development Tool kit : pring tool suite

3.3.2. Software Requirements:

 Operating System : Windows

 Technology : Java and J2EE

 Web Technologies : Html, JavaScript, CSS

 IDE : Spring tool suite

 Web Server : Tomcat

 Database : Oracle

 Java Version : J2SDK1.5

16
Modules:

Users:

In this module user can register and upload the complaints anyone (who has been asked to
pay a bribe or anyone who has information of corruption) can write a complaint to the digital
solution to combat bribery & justice restoration system . This application will help user to
track the details as the user will be getting regular update at each step through registered
gmail. The email is sent from the admin or organization email.

Admin:

In this module admin can login into application and admin can view the complaints of users.
Admin can assign the complaint to specific employee to process the complaint, and can view
the complaint status also.He can acsess all the records of complaints , and also he can delete
the complaints if needed in case of fake complaints.

Employee:

In this module authorities can view the assigned complaints and they keeps up to date about
complaints in the application . He can update the status of the complaint on the basis of the
work he done on the complaint via the evidences of any type of source provided. The
employee updated status will be sent as an update to the user.

17
FEASIBILITY STUDY

The next step in analysis is to verify the feasibility of the proposed system. “All
projects are feasible given unlimited resources and infinite time“. But in reality both
resources and time are scarce. Project should confirm to time bounce and should be optimal
in there consumption of resources. These places a constant are approval of any project.

Feasibility has applied to Maintenance of Elementary School Data pertains to the following
areas:

 Technical feasibility

 Operational feasibility

 Economical feasibility

TECHNICAL FEASIBILITY:

To determine whether the proposed system is technically feasible, we should take into
consideration the technical issues involved behind the system.

Maintenance of Elementary School Data uses the web technologies, which is

rampantly employed these days worldwide. The world without the web is incomprehensible
today. That goes to proposed system is technically feasible.

OPERATIONAL FEASIBILITY:

To determine the operational feasibility of the system we should take into

consideration the awareness level of the users. This system is operational feasible since the
users are familiar with the technologies and hence there is no need to gear up the personnel to
use system. Also the system is very friendly and to use.

18
ECONOMIC FEASIBILITY

To decide whether a project is economically feasible, we have to consider various factors

as:

 Cost benefit analysis

 Long-term returns

 Maintenance costs

Technical Architecture:

Request
Database
Browser
Web Server
(MYSQL)
HTML/JSP
JSP
Response

Fig 2: Technical architecture of project

SYSTEM DESIGN:
19
4.1. Introduction
Software design sits at the technical kernel of the software engineering process and is
applied regardless of the development paradigm and area of application. Design is the first
step in the development phase for any engineered product or system. The designer‘s goal is to
produce a model or representation of an entity that will later be built. Beginning, once system
requirement has been specified and analysed, system design is the first of the three technical
activities -design, code and test that is required to build and verify software.

The importance can be stated with a single word ―Quality‖. Design is the place
where quality is fostered in software development. Design provides us with representations of
software that can assess for quality. Design is the only way that we can accurately translate a
customer‘s view into a finished software product or system. Software design serves as a
foundation for all the software engineering steps that follow. Without a strong design we risk
building an unstable system – one that will be difficult to test, one whose quality cannot be
assessed until the last stage. The purpose of the design phase is to plan a solution of the
problem specified by the requirement document. This phase is the first step in moving from
the problem domain to the solution domain. In other words, starting with what is needed,
design takes us toward how to satisfy the needs. The design of a system is perhaps the most
critical factor affection the quality of the software; it has a major impact on the later phase,
particularly testing, maintenance. The output of this phase is the design document. This
document is similar to a blueprint for the solution and is used later during implementation,
testing and maintenance. The design activity is often divided into two separate phases System
Design andDetailed Design.

System Design also called top-level design aims to identify the modules that should be in
the system, the specifications of these modules, and how they interact with each other to produce
the desired results. At the end of the system design all the major data structures, file formats,
output formats, and the major modules in the system and their specifications are decided. During,
Detailed Design, the internal logic of each of the modules specified in system design is decided.
During this phase, the details of the data of a module is usually specified in a high-level design
description language, which is independent of the target language in which the software will
eventually be implemented.

20
 In system design the focus is on identifying the modules, whereas during detailed
design the focus is on designing the logic for each of the modules. In other works, in system
design the attention is on what components are needed, while in detailed design how the
components can be implemented in software is the issue. Design is concerned with
identifying software components specifying relationships among components. Specifying
software structure and providing blue print for the document phase. Modularity is one of the
desirable properties of large systems. It implies that the system is divided into several parts.
In such a manner, the interaction between parts is minimal clearly specified.

During the system design activities, Developers bridge the gap between the
requirements specification, produced during requirements elicitation and analysis, and the
system that is delivered to the user. Design is the place where the quality is fostered in
development. Software design is a process through which requirements are translated into a
representation of software.

4.2.Data Flow Diagrams:

A graphical tool used to describe and analyse the moment of data through a system
manual or automated including the process, stores of data, and delays in the system. Data
Flow Diagrams are the central tool and the basis from which other components are developed.
The transformation of data from input to output, through processes, may be described
logically and independently of the physical components associated with the system. The DFD
is also known as a data flow graph or a bubble chart.

 DFDs are the model of the proposed system. They clearly should show the requirements on
which the new system should be built. Later during design activity this is taken as the basis
for drawing the system‘s structure charts. The Basic Notation used to create a DFD‘s are as
follows:

 Dataflow: Data move in a specific direction from an origin to a destination.

21
 Process: People, procedures, or devices that use or produce (Transform) Data. The physical
component is not identified.

22
  Source: External sources or destination of data, which may be People, programs,
organizations or other entities.

 Data Store: Here data are stored or referenced by a process in the System
4.3.UML Diagrams:
Class Diagram:
Class diagram gives an overview of a software system by displaying classes, attributes,
operations, and their relationships. This Diagram includes the class name, attributes, and
operation in separate designated compartments.

Fig 3: Essential elements of class diagram

Essential elements of A UML class diagram:
 Class Name
 Attributes
 Operations
Class Name:
The name of the class is only needed in the graphical representation of the class. It appears inthe
topmost compartment. A class is the blueprint of an object which can share the same
relationships, attributes, operations, & semantics. The class is rendered as a rectangle, including
its name, attributes, and operations in sperate compartments.

Attributes:
An attribute is named property of a class which describes the object being modeled. In the class
diagram, this component is placed just below the name-compartment.A derived attribute is
computed from other attributes.

22
22
23
Relationships:
There are mainly three kinds of relationships in UML:
 Dependencies
 Generalizations
 Associations
Dependency:
A dependency means the relation between two or more classes in which a change in one may
force changes in the other. However, it will always create a weaker relationship.

Fig 3.1: example of dependency relation

Generalization:
A generalization helps to connect a subclass to its superclass. A sub-class is inherited from its
superclass.Class diagram allows inheriting from multiple superclasses.

Fig 3.2: example of generalization connection

Association:
This kind of relationship represents static relationships between classes A and B.

Fig 3.3:
example of association
connection

23
Fig 4: Class Diagram

23
Sequence Diagrams:

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.

Fig 4.1: Sequence Diagram

24
Deployement Diagram:
UML Deployment diagram is used to define the hardware requirements for the particular
product to execute the software, basically it maps the software design requirement to the
physical system which executes the software design and visualize how software interact with
hardware to complete the test execution. To design the deployment diagram node,
component, artifact and interface notation are used.
The Main Purpose of the Deployment Diagram

 To represent the hardware topology of a system.

 Represent how different hardware components are inter-connected and how these
hardware components are used to deploy software components.

25
Fig 4.2: Deployement Diagram

25
Use Case Diagram:

Use case diagrams model the functionality of a system using actors and use cases. Use cases
are services or functions provided by the system to its users. Use case diagram is useful for
representing the functional requirements of the system using various notations like system,
use case, actors, and relationships.Basic Use Case Diagram Symbols and Notations System
Draw your system's boundaries using a rectangle that contains use cases. Place actors outside the
system's boundaries.

Fig 4.3: example of use case diagram

Use Case:
Draw use cases using ovals. Label with ovals with verbs that represent the system's functions.

Actors:
Actors are the users of a system. When one system is the actor of another system, label the
actor system with the actor stereotype.

26
Relationships:
Illustrate relationships between an actor and a use case with a simple line. For relationships
among use cases, use arrows labelled either "uses" or "extends." A "uses" relationship
indicatesthat one use case is needed by another in order to perform a task. An "extends"
relationship indicates alternative options under a certain use case.

27
Fig 4.4: Use case Use Diagram

26
ER Diagram:

Data models are tools used in analysis to describe the data requirements and assumptions in
the system from a top-down perspective. They also set the stage for the design of databases
later on in the SDLC.

There are three basic elements in ER models:

 Entities are the "things" about which we seek information.

 Attributes are the data we collect about the entities.

 Relationships provide the structure needed to draw information from multiple entities.

Developing an ERD:

Developing an ERD requires an understanding of the system and its components. Its
components are:

 Rectangles: These are used for representing entity sets.

 Ellipses: These are used for representing attributes.

 Diamonds: These are used for representing relationship sets.

 Lines: These are used for linking attributes to entity sets and entity sets to relationship
sets.

 Start an ERD:

 Define Entities :

 These are usually nouns used in descriptions of the system, in the discussion of business
rules, or in documentation.

 Define Relationships:

 These are usually verbs used in descriptions of the system or in discussion of the
business rules (entity _ entity).

 Add attributes to the relations:

 These are determined by the queries, and may also suggest new entities, e.g. grade; or
they may suggest the need for keys or identifiers.

 Add cardinality to the relations:

28
 Many-to-Many must be resolved to two one-to-many with an additional entity.
Automatically happens. Sometimes involves introduction of a link entity (which will b

28
Database Design:

Fig 5: Database table for user information

Fig 5.1: Database table for admin information

29
Activity Diagram:

An activity diagram illustrates the dynamic nature of a system by modelling the flow of
control from activity to activity. An activity represents an operation on some class in the
system that results in a change in the state of the system. Typically, activity diagrams are used
to model workflow or business processes and internal operation. Because an activity diagram
is a specialkind of state chart diagram, it uses some of the same modelling conventions.

Basic Activity Diagram Symbols and Notations

Action states:
Action states represent the non-interruptible actions of objects. You can draw an action state
in Smart Draw using a rectangle with rounded corners.

Action Flow:
Action flow arrows illustrate the relationships among action states.

Object Flow

Object flow refers to the creation and modification of objects by activities. An object flow
arrow from an action to an object means that the action creates or influences the object.

An object flow arrow from an object to an action indicates that the action state uses the
object.

30
Initial State:

A filled circle followed by an arrow represents the initial action state.

Final State:

An arrow pointing to a filled circle nested inside another circle represents the final action
state.

Branching:

A diamond represents a decision with alternate paths. The outgoing alternates should be
labelled with a condition or guard expression. You can also label one of the paths "else."

31
31
Synchronization:
A synchronization bar helps illustrate parallel transitions. Synchronization is also called
forking and joining.

Swimlanes - Swimlanes group related activities into one column.

Fig 6: Activity Diagram

32
Block Diagram:

A Block Diagram is a drawing illustration of a system whose major parts or components are
represented by blocks. These blocks are joined by lines to display the relationship between
subsequent blocks.

Block in Block Diagram is the representation of several known properties such that when
summed together, they make up the central block diagram. The blocks portray a system as a
collection of components responsible for specific tasks in a particular setting.

Basic block components are mainly five and include:

Block: it represents the logical and physical components of the system.

Part: it comprises all aspects modeled using aggregation and association.

Reference: it has all the parts which were developed using aggregation and association.

Standard Port: this is the point of interaction between a system block and the corresponding
environment.

Flow Port: this is the point of interaction where a block can emerge from or to.

Association: it explains the communication amongst the blocks.

Request
Database
Browser
Web Server
(MYSQL)
HTML/JSP
JSP
Response

Fig 7: Block Diagram

33
What significant role do Block Diagrams play? Well, a Block Diagram is a fundamental
way that hardware and software developers utilize to describe these systems while illustrating
their workflows and processes. Electricians, on another hand, need them to represent systems
and their shifting, for example, the mechatronic systems in the trucking industry.

More often than not, block diagrams are of great assistance when a clear picture of
information or control flows is required, besides when a project has a myriad of processes.
They make it easier to represent complicated algorithms or flows of details or communication
among precise components, for instance, in a mass production facility. Graphically
represented project processes are less strenuous to understand than when they are in text
form.

When you walk into a room with a block diagram, you will be able to easily decipher the
system’s details, interface, and such as structure aspects. It is all thanks to how the blocks are
connected intellectually to one another by lines. Blocks are convenient when designing new
processes and upgrading those that already exist.

34
 5. SYSTEM IMPLEMENTATION

5.1 Modules:

5.1.1Module Description:

Users:

In this module user can register and upload the complaints anyone (who has been asked to
pay a bribe or anyone who has information of corruption) can write a complaint to the digital
solution to combat bribery & justice restoration system . This application will help user to
track the details as the user will be getting regular update at each step through registered
gmail. The email is sent from the admin or organization email.

Admin:

In this module admin can login into application and admin can view the complaints of users.
Admin can assign the complaint to specific employee to process the complaint, and can view
the complaint status also.He can acsess all the records of complaints , and also he can delete
the complaints if needed in case of fake complaints.

Employee:

In this module authorities can view the assigned complaints and they keeps up to date about
complaints in the application . He can update the status of the complaint on the basis of the
work he done on the complaint via the evidences of any type of source provided. The
employee updated status will be sent as an update to the user.

35
JAVA TECHNOLOGY:

Java technology is both a programming language and a platform.

The Java Programming Language

The Java programming language is a high-level language that can be characterized by all of
the following buzzwords:

 Simple

 Architecture neutral

 Object oriented

 Portable

 Distributed

 High performance

 Interpreted

 Multithreaded

 Robust

 Dynamic

 Secure

With most programming languages, you either compile or interpret a program so that you can
run it on your computer. The Java programming language is unusual in that a program is both
compiled and interpreted. With the compiler, first you translate a program into an
intermediate language called Java byte codes —the platform-independent codes interpreted
by the interpreter on the Java platform.

The original and reference implementation Java compilers, virtual machines, and class
libraries were developed by Sun from 1991 and first released in 1995. As of May 2007, in
compliance with the specifications of the Java Community Process, Sun relicensed most of its
Java technologies under the GNU General Public License.

36
 Fig 8: Programming-1

You can think of Java byte codes as the machine code instructions for the Java
Virtual Machine (Java VM). Every Java interpreter, whether it’s a development tool or a Web
browser that can run applets, is an implementation of the Java VM. Java byte codes help
make “write once, run anywhere” possible. You can compile your program into byte codes on
any platform that has a Java compiler. The byte codes can then be run on any implementation
of the Java VM.

37
`

Fig 8.1: Programming-2

THE JAVA PLATFORM

The Java platform has two components:

 The Java Virtual Machine (Java VM)

 The Java Application Programming Interface (Java API)

You’ve already been introduced to the Java VM. It’s the base for the Java platform and is
ported onto various hardware-based platforms.

The Java API is a large collection of ready-made software components that provide many
useful capabilities, such as graphical user interface (GUI) widgets. The Java API is grouped
into libraries of related classes and interfaces; these libraries are known as packages. The next
section, What Can Java Technology Do? Highlights what functionality some of the packages
in the Java API provide.The following figure depicts a program that’s running on the Java
platform. As the figure shows, the Java API and the virtual machine insulate the program
from the hardware.

Fig 8.2: Java IDE

38
 Fig 8.3 : Java Platform

Native code is code that after you compile it, the compiled code runs on a specific
hardware platform. As a platform-independent environment, the Java platform can be a bit
slower than native code. However, smart compilers, well-tuned interpreters, and just-in-time
byte code compilers can bring performance close to that of native code without threatening
portability.

How does the API support all these kinds of programs? It does so with packages of
software components that provides a wide range of functionality. Every full implementation
of the Java platform gives you the following features:

 The essentials: Objects, strings, threads, numbers, input and output, data structures,
system properties, date and time, and so on.

 Applets: The set of conventions used by applets.

 Networking: URLs, TCP (Transmission Control Protocol), UDP (User Data gram
Protocol) sockets, and IP (Internet Protocol) addresses.

 Internationalization: Help for writing programs that can be localized for users
worldwide. Programs can automatically adapt to specific locales and be displayed in the
appropriate language.

 Security: Both low level and high level, including electronic signatures, public and
private key management, access control, and certificates.

 Software components: Known as JavaBeansTM, can plug into existing component

architectures.

 Object serialization: Allows lightweight persistence and communication via Remote

Method Invocation (RMI).

39
 Java Database Connectivity (JDBCTM): Provides uniform access to a wide range of
relational databases.

39
 History of web Application:

Earlier in client- server computing, each application had its own client program and
it worked as a user interface and need to be installed on each user's personal computer.

Introduction to Web Server:

A Web Server is a computer on the World Wide Web that stores Html
documents that can be retrieved via a Web browser.

It is a computer that delivers web pages.

 Container: Container is nothing but a Java application which controls servlets. Tomcat is
one of the examples of a container. It is the container which calls the servlet's methods like
doPost() and doGet().

 Get and Post Methods of Http: The Get is one the simplest Http method. Its main job is
to ask the server for the resource. The post method is more powerful request. By using Post
we can request as well as send some data to the server.

About JSP :

Java is known for its characteristic of "write once, run anywhere”. JSP pages
are platform independent. A Java Server Page is a simple text file consisting of HTML or
XML content along with JSP elements (a sort of shorthand for Java code). When a client
requests a JSP page of the web server and it has not

40
been run before, the page is first passed to a JSP engine which compiles the page to a servlet,
runs it and returns the resulting content to the client. Thereafter, the web server's servlet
engine will run the compiled page. JSP pages are high level extension of servlet and it enables
the developers to embed java code in html pages. JSP files are finally compiled into a servlet
by the JSP engine. Compiled servlet is used by the engine to serve the requests.

Classes involved:

The javax.servlet.jsp package defines two classes:

 JSP Page

 Http Jsp Page

Interfaces involved:These classes define the interface for the compiled JSP page. These
Interfaces are:

JspInit ()

JspDestroy ()

JspService(HttpServletRequest request,HttpServletResponse response)

In the compiled JSP file these methods are present. Programmer can define jspInit()
and jspDestroy() methods, but the _jspService(HttpServletRequest
request,HttpServletResponse response) method is generated by the JSP engine.

About Servlets: Servlets are the Java platform technology of choice for extending and
enhancing Web servers. Servlets provide a component based platform independent method
for building Web-based applications. Servlets have access to the entire family of Java APIs,
including the JDBC API to access enterprise databases. Servlets can also access a library of
HTTP-specific calls and receive all the benefits of the mature Java language, including
portability, performance, reusability, and crash protection.

Today servlets are a popular choice for building interactive Web

applications. Third-party servlet containers are available for Apache Web Server, Microsoft
IIS, and others. Servlet containers are usually a component of Web and application servers,
such as BEA Web Logic Application Server, IBM Web Sphere,

Sun Java System Web Server, Sun Java System Application Server, and others.

Java servlet technology lets you define HTTP-specific servlet classes. A servlet
class extends the capabilities of servers that host the applications that are accessed by way of
41
a request-response programming model. Although servlets can respond to any type of request.

41
 Servlet Packages: The javax.servlet and javax.servlet.http packages provide interfaces
and classes for writing servlets. All servlets must implement the Servlet interface, which
defines life-cycle methods. When implementing a generic service, you can use or extend the
GenericServlet class provided with the Java Servlet API. The HttpServlet class provides
methods, such as doGet and doPost, for handling HTTP-specific services.

 Servlet life cycle: The life cycle of a servlet is controlled by the container in which the
servlet has been deployed. When a request is mapped to a servlet, the container performs the
following steps. If an instance of the servlet does not exist, the web container Loads the
servlet class. Creates an instance of the servlet class Initializes the servlet instance by calling
the init method. Invokes the service method, passing request and response objects. If the
container needs to remove the servlet, it finalizes the servlet by calling the servlet's destroy
method.

 Initializing a Servlet: After the web container loads and instantiates the servlet class and
before it delivers requests from clients, the web container initializes the servlet. To
customize this process to allow the servlet to read persistent configuration data, initialize
resources, and perform any other one-time activities, you override the init method of the
Servlet interface. A servlet that cannot complete its initialization process should throw
Unavailable Exception.

 Writing Service Methods: The service provided by a servlet is implemented in the

service method of a Generic Servlet, in the doMethod methods (where Method can take the
value Get, Delete, Options, Post, Put, or Trace) of an Http Servlet object, or in any other
protocol-specific methods defined by a class that implements the Servlet interface. In the rest
of this presentation, the term service method is used for any method in a servlet class that
provides a service to a client.

42
 The general pattern for a service method is to extract information from the request, access
external resources, and then populate the response based on that information. For HTTP
servlets, the correct procedure for populating the response is to first retrieve an output stream
from the response, then fill in the response headers, and finally write any body content to the
output stream. Response headers must always be set before the response has been committed.
Any attempt to set or add headers after the response has been committed will be ignored by
the web container.

 Advantages:

The servlet advantages are as follows.

 Portability

 Powerful

 Efficiency

 Safety

 Integration

 Extensibility

 Inexpensive

About HTML:HTML (hyper text markup language) is a language used to create hyper text
documents that have hyper links embedded in them. It consists of tags embedded in the text
of a document with HTML. We can build web pages or web documents. it is basically a
formatting language and not a programming language. The browser reading the document
interprets mark up tags to help format the document for subsequent display to a reader.
HTML is a language for describing structured documents. HTML is a platform independent.

43
 WWW (World Wide Web) pages are written using HTML. HTML tags
control in part the representation of the WWW page when view with web browser. The
browser interprets HTML tags in the web document and displays it. Different browsers show
data differently.

Examples of browsers used to be web pages include:

We use spring tool suite IDE.

Spring Tool Suite (STS) is an Eclipse-based IDE which is dedicated for developing Spring-
based projects. It is actively developed and maintained by the SpringSource community. STS
facilitates and simplifies Spring-based applications development by providing robust project
templates such as Spring Batch, Spring Integration, Spring Persistence (Hibernate + JPA),
Spring MVC, etc. In addition, with Maven integration, STS releases developers from
manually managing Spring jar files in their projects. You always get the latest update of
Spring artifacts from Maven repository.

You can choose to download and install STS in one of three ways:

 Download and install STS from an installer program.

 Install STS through Eclipse update.

 Download and extract zip archive.

The Eclipse platform which provides the foundation for the Eclipse IDE is composed of plug-
ins and is designed to be extensible using additional plug-ins. Developed using Java, the
Eclipse platform can be used to develop rich client applications, integrated development
environments and other tools. Eclipse can be used as an IDE for any programming language
for which a plug-in is available. The Java Development Tools (JDT) project provides a plug-
in that allows Eclipse to be used as a Java IDE, PyDev is a plugin that allows Eclipse to be
used as a Python IDE, C/C++ Development Tools (CDT) is a plug-in that allows Eclipse to be
used for developing application using C/C++, the Eclipse Scala plug-in allows Eclipse to be
used an IDE to develop Scala applications and PHPeclipse is a plug-in to eclipse that provides
complete development tool for PHP.

44
Licensing

Eclipse platform and other plug-ins from the Eclipse foundation is released under the Eclipse
Public License (EPL). EPL ensures that Eclipse is free to download and install. It also allows
Eclipse to be modified and distributed.

Eclipse Releases

Every year, since 2006, the Eclipse foundation releases the Eclipse Platform and a number of
other plug-ins in June.

Installing Eclipse

To install on windows, you need a tool that can extract the contents of a zip file. For example
you can use −

 7-zip

 PeaZip

 IZArc

Using any one of these tools, extract the contents of the eclipse zip file to any folder of your
choice.

Launching Eclipse:On the windows platform, if you extracted the contents of the zip file to
c:\, then you can start eclipse by using c:\eclipse\eclipse.exe.When eclipse starts up for the
first time it prompts you for the location of the workspace folder. All your data will be stored
in the workspace folder. You can accept the default or choose new location.

If you select "Use this as the default and do not ask again", this dialog box will not come up
again. You can change this preference using the Workspaces Preference Page

45
About Tomcat:
Tomcat is an application server from the Apache Software Foundation that executes Java
servlets and renders Web pages that include Java Server Page coding. Described as a
"reference implementation" of the Java Servlet and the Java Server Page specifications,
Tomcat is the result of an open collaboration of developers and is available from the Apache
Web site in both binary and source versions. Tomcat can be used as either a standalone
product with its own internal Web server or together with other Web servers, including
Apache, Netscape Enterprise Server, Microsoft Internet Information Server (IIS), and
Microsoft Personal Web Server. Tomcat requires a Java Runtime Enterprise Environment that
conforms to JRE 1.1 or later.

About MySQL Database:

MySQL is a fast, easy-to-use RDBMS being used for many small and big businesses.
MySQL is developed, marketed and supported by MySQL AB, which is a Swedish company.
MySQL is becoming so popular because of many good reasons −

MySQL is released under an open-source license. So you have nothing to pay to use it.

MySQL is a very powerful program in its own right. It handles a large subset of the
functionality of the most expensive and powerful database packages.

MySQL uses a standard form of the well-known SQL data language.

MySQL works on many operating systems and with many languages including PHP, PERL,
C, C++, JAVA, etc.

MySQL works very quickly and works well even with large data sets.

MySQL is very friendly to PHP, the most appreciated language for web development.

MySQL supports large databases, up to 50 million rows or more in a table. The default file
size limit for a table is 4GB, but you can increase this (if your operating system can handle it)
to a theoretical limit of 8 million terabytes (TB).

MySQL is customizable. The open-source GPL license allows programmers to modify the
MySQL software to fit their own specific environment

46
 DEPLOYMENT DIRECTORIES FOR DEFAULT WEB APPLICATION:

HTML and JSP Files:

 Main Location

$CATALINA_HOME/webapps/ROOT

 Corresponding URLs.

http://host/SomeFile.html

http://host/SomeFile.jsp

 More Specific Location (Arbitrary Subdirectory).

$CATALINA_HOME/webapps/ROOT/SomeDirectory

 Corresponding URLs

http://host/SomeDirectory/SomeFile.html

http://host/SomeDirectory/SomeFile.jsp

 Main Location (Classes without Packages).

$CATALINA_HOME/webapps/ROOT/WEB-INF/classes

 Corresponding URL (Servlets).

http://host/servlet/ServletName

 More Specific Location (Classes in Packages).

$CATALINA_HOME/webapps/ROOT/WEB-INF/classes/packageName

 Corresponding URL (Servlets in Packages).

 http://host/servlet/packageName.ServletName

 Servlet and Utility Class Files Bundled in JAR Files

 Location

$CATALINA_HOME/webapps/ROOT/WEB-INF/lib

 Corresponding URLs (Servlets)

http://host/servlet/ServletName

47
http://host/servlet/packageName.ServletName

47
SOFTWARE TESTING
Software testing is a critical element of software quality assurance and represents the
ultimate review of specification, design and code generation.

TESTING OBJECTIVES

 To ensure that during operation the system will perform as per specification.

 TO make sure that system meets the user requirements during operation

 To make sure that during the operation, incorrect input, processing and output will be
detected

 To see that when correct inputs are fed to the system the outputs are correct

 To verify that the controls incorporated in the same system as intended

 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

The software developed has been tested successfully using the following testing
strategies and any errors that are encountered are corrected and again the part of the program
or the procedure or function is put to testing until all the errors are removed. A successful test
is one that uncovers an as yet undiscovered error.

Note that the result of the system testing will prove that the system is working
correctly. It will give confidence to system designer, users of the system, prevent frustration
during implementation process etc.,

White box testing:White box testing is a testing case design method that uses the control
structure of the procedure design to derive test cases. All independents path in a module are exercised
at least once, all logical decisions are exercised at once, execute all loops at boundaries and within
their operational bounds exercise internal data structure to ensure their validity. Here the customer is
given three chances to enter a valid choice out of the given menu. After which the control exits the
current menu.

Black Box Testing:

Black Box Testing attempts to find errors in following areas or categories, incorrect or
missing functions, interface error, errors in data structures, performance error and
initialization and termination error. Here all the input data must match the data type to
become a valid entry.

48
The following are the different tests at various levels:

Unit Testing:

Unit testing is essentially for the verification of the code produced during the coding
phase and the goal is test the internal logic of the module/program. In the Generic code
project, the unit testing is done during coding phase of data entry forms whether the functions
are working properly or not. In this phase all the drivers are tested they are rightly connected
or not.

Integration Testing:

All the tested modules are combined into sub systems, which are then tested. The goal
is to see if the modules are properly integrated, and the emphasis being on the testing
interfaces between the modules. In the generic code integration testing is done mainly on
table creation module and insertion module.

Validation Testing:

This testing concentrates on confirming that the software is error-free in all respects.
All the specified validations are verified and the software is subjected to hard-core testing. It
also aims at determining the degree of deviation that exists in the software designed from the
specification; they are listed out and are corrected.

System Testing:

This testing is a series of different tests whose primary is to fully exercise the computer-based
system. This involves:

 Implementing the system in a simulated production environment and testing it.

 Introducing errors and testing for error handling.

49
Test Cases:
Tested Test name Inputs Expected Actual status
output output
1 Login test Username, Need to Its success
password validate on successfully
database validated
on the
database
2 Registration Registration Need add Data added success
details the data in successfully
the table
3 Post Name, Need add Complaint success
Complaint description, the details
proof complaint added
details on
database
4 View Get the Need to Complaints success
Complaints Complaint display the displayed
from all the
different Complaints
sender from users
5 Update Complaint Need to Status success
Complaint update the successfully
Complaint updated
with given
details

Fig 9 : Table for test cases

50
6. RESULTS AND DISCUSSION

Fig 10: Login page

Fig 10.1 : user registration page

51
Fig 10.2: View complaint page .

Fig 10.3 :Update complaint page.

52
53
Fig 10.4: User complaint view page

53
 7.CONCLUSION
Now a day as technology is increasing usage are also increasing so Complaints is also
increasing. It demands for developing new Complaint management applications which have
attracting features. As this system provides an total online based process starting from
complaint posting to complaint result. Every update will be received by the complaint raiser
via email, hence there will be no lack of communication. Hence, the online complaint system
will make the user to deal with the complaint without any interaction with the organization or
any form of interaction. Those the user ,admin, employee this three also no need of any
interaction. This system is very user friendly and very interactive for the user and
organizational employees.

54
55
 8.FUTURE SCOPE
Furthermore, this system is only intended for use by the manager of one particular
Application. It could be expanded to encompass all the Application. Hence complaints occur
in every field ,it can be implemented easily for every organization. Hence, the system has
limitations in these stage it can be implemented or can be tend to use it every field .This
application can be extended as a mobile application for ease of use.

55
REFERENCES:

 “Central Vigilance Commission” http://portal.cvc.gov.in/cvproject/

 ”Complaint Management ”

 https://www.acc.org.bt/sites/default/files/Complaint%20Management%20Policy%20and
%20Procedures%20Manual_1.pdf

 Osman Nasr , Enayat Alkhide. “Online Complaint Management System”.

 “Proposal on Corruption Complaints Management in Greece: The Role of the General

Secretariat Against Corruption”

 https://www.oecd.org/governance/ethics/proposal-corruption-complaints-management-
gsac-greece-e.

56
Steps for implementation:

 Install all the softwares mentioned in the requirements.

 Open the tomcat server make sure it started the service.
 Launch an workspace in the spring tool suite.
 Add all the justice restoration system files into the workspace.
 Select the servers at the bottom of the workspace window.
 Select tomcat server and click run button on the right.
 Once the tomcat server is showing “started, synchronized”, you’re good to go.
 Go to the browser(any) and enter the following link
http://localhost:8080/JusticeRestorationSystem
 Once the above link is open we can see the project
“Digital solution to combat bribery and justice restoration system”
 Now ,you can use the functionality of the system.

57