Lenin Peter

DATA LEAKAGE DETECTION
System
PROJECT REPORT
Submitted by
LENIN PETER.L
REG.NO. 721516621315
in partial fulfilment for the award of the degree of
MASTER OF COMPUTER APPLICATIONS
IN
DEPARTMENT OF COMPUTER APPLICATIONS
NEHRU INSTITUTE OF INFORMATION TECHNOLOGY
AND MANAGEMENT, COIMBATORE – 641 105.
ANNA UNIVERSITY,CHENNAI - 600 025
APRIL- 2019
1
ANNA UNIVERSITY: CHENNAI 600 025
BONAFIDE CERTIFICATE
Certified that this Report titled “DATA LEAKAGE DETECTIVE SYSTEM” is the
bonafide of Mr. Lenin Peter.L (721516621315) who carried out the work under my
supervision. Certified further that to the best of my knowledge the work reported herein does not
form part of any other thesis or dissertation on the basis of which a degree or award was
conferred on an earlier occasion on this or any other candidate.
Dr. R. Thiyagarajan M.Sc., M.C.A., Ms. C. Meera Bai M.C.A., M.Phil.

M.Phil.,Ph.D.
Head of the Department Supervisor
Department of Computer Applications Department of Computer Applications
Nehru Institute of Information Nehru Institute of Information
Technology and Management Technology and Management
Coimbatore 641105 Coimbatore 641105
Submitted for the project Viva – Voce examination held on __________
Internal Examiner External Examiner
2
DECLARATION
I affirm that the project work titled “DATA LEAKAGE DETECTIVE
SYSTEM” being submitted in partial fulfilment for the award of Master of Computer
Applications is the original work carried out by me. It has not formed the part of any other project
work submitted for award of any degree or diploma, either in this or any other
University.
LENIN PETER.L
721516621315
I certify that the declaration made above by the candidate is true.
Signature of the Supervisor

Ms.Meera Bai M.C.A., M.Phil.
Asst. Professor
Department of Computer Applications
3
ACKNOWLEDGEMENT
I would like convey my sincere thanks to Adv. Dr. P. Krishna Das - Managing Trustee and
Dr.P. Krishnakumar MBA, PhD - CEO & Secretary, Nehru group of Institutions, Coimbatore
for supporting us and completing our needs.
I would like to express my gratitude to Dr.R.Mosses Daniel M.B.A., Ph.D., PGDCA, PGDIM,
Principal, Nehru Institute of Information Technology and Management, Coimbatore for giving
me an opportunity and facility to complete this project.
I express heartfelt thanks to my Head of the Department Dr.R.Thiyagarajan M.Sc., M.C.A.,

M.Phil., Ph.D, Nehru Institute of Information Technology and Management, Coimbatore for her
energetic encouragement.
I render my sincere gratitude to my Project Guide Ms.Meera Bai, M.C.A., M.Phil., Assistant
Professor-MCA, NIITM and all other staff of Department of Computer Applications for their
constant motivation and valuable help throughout the project.
I am thankful to the management and Mr.Shameer Project Manager of Sinet Logics,

Perinthalmanna. And all the staffs who gave me necessary details and extended all facilities to
complete the Project.
I am also thankful to my family members, friends and all other well-wishers who have helped me
in completing the Project.
4
Abstract
Traditional judicial system is blamed for its long delay for processing legal issues and not giving
timely judgment. We are continuously witnessing lots of civil or criminal cases has been lagging
for years. As a big secular democratic country we have thousands of legal fighting between
persons, states, political parties, NGOs etc. We know that in India any attempt to eliminate or to
reduce the unfair delay of legal processing will be appreciated.
The Online legal service enhancement system is such an attempt to reduce the irritating lag in
judicial services. Here the system focusing different agencies or personnel those involved in
judicial system to integrate, share, process them better. The transparencies in the legal trials are
very important and it can be maintained here very effectively.
In a nutshell the judicial processing is the flow of process from the submitting of a case diary
by the investigation team/ officer to court with adequate proofs, witness details, investigation
findings etc.. This Data has to learn by the public prosecutor and should available to magistrate
for trial in different way.
The project include five modules such as Investigation officer, Public Prosecutor, Judge,
Shirasthar, Admin. Investigation officer can login into the system using ‘case number’ and
‘password’. He /she can submit investigation report for a particular case. Shirasthar assigns judge
or public prosecutor for a particular case, and general trial data is updated by the shirasthar on
time. The general trial data is updated by the shirasthar on time. Public prosecutor can login into
the system. He/she can see the Case details after selecting the case number. He sees the case trial
orders of Judge. Public prosecutor see his own trial data and personal notes about a case. Judge
Can write personal notes about a particular case .Portal administrator is approving different login
credentials.
5
TABLE OF CONTENTS
SI.NO CHAPTERS PAGE.NO
1 ABSTRACT I
2 LIST OF TABLES
3 LIST OF FIGURES
4 LIST OF SYMBOLS
INTRODUCTION
5 1.1 Project Introduction 1
6 1 1.2 Company Profile. 2
SYSTEM STUDY
7 2.1. Existing System 4
8 2.2. Proposed System 4
SYSTEM ANALYSIS
9 3.1.Introduction . 5
10 3.1.1 Problem definition 6
11 3.1.2 Requirement analysis 6
12 3.2. Feasibility Study 7
13 3.2.1. Operational Feasibility 7
14 3.2.2. Technical Feasibility 7

15 3.2.3. Economical Feasibility 8
16 3.2.4. Social Feasibility 8
SYSTEMS SPECIFICATION
17 4 4.1 Hardware Specification 9
6
18 4.2 Software Specification 9
SOFTWARE DESCRIPTION
19 5 5.1 UserInterface 10
20 5.2 Back-end 12
PROJECT DESCRIPTION
21 6.1 Overview of the Project 15
22. 6.2 Module Description 16
SYSTEM DESIGN
23 7.1. Data Flow Diagram 17
24 7.2. ER Diagram 22
25 7.3. Database Table Structure 23
26 7.4. Input Design 29
27 7.5. Output Design 29
28 7.6. Database Design 30

SYSTEM TESTING
29 8.1 . Introduction. 31
30 8.2 . Types of Testing 31
8.2.1. Unit Testing 32
32 8.2.2 Requirement Testing 33
34 8.2.3 User Testing 33

35 8.2.2. Validation Testing 33
36 8.2.3.Integration Testing 34
37 8.2.4.User Acceptance Testing 34
38 8.3.Test Cases 34
SYSTEM IMPLEMENTATION
38 9.1 Implementation Planning. 37
39 9 9.2 Implementation Phase in this project 37
7
40 9.3 Maintenance 38
41 9.4 Methods of implementation 38
42 CONCLUSION & FUTURE 39
43 ENHANCEMENTS
44 Source Code 40
45 Screenshots 50
46 REFERENCES
8
LIST OF TABLES
Table Number Table Name Page Number
1 Login 21
2 Accusetion 21
3 Districttness Information 22
4 Evidence Details 23
5 Mahassar Details 23
6 Charge Sheet. 24
7 Admin Login. 25
8 Case Trail 25
9 Patitioner Information 26
10 Judge Activity
11 Feedback
12 State
13 Prosecutor Activity
14 Shirasthar Reg
15 Prosecutor Reg
16 Case Reg
9
LIST OF SYMBOLS
Sl. No. Symbol Purpose
(INPUT/OUTPUT)
2 PROCESSES
DATAFLOWS
3
10
CHAPTER 1
INTRODUCTION
PROJECT INTRODUCTION
Traditional judicial system is blamed for its long delay for processing legal issues and not
giving timely judgment. We are continue sly witnessing lots of civil or criminal cases has been
lagging for years. As a big secular democratic country we have thousands of legal fighting
between persons, states, political parties, NGOs etc. We know that in India any attempt to
eliminate or to reduce the unfair delay of legal processing will be appreciated.
The online legal service management system is such an attempt to reduce the irritating
lagging in judicial service. Here we are focusing different agencies or personal those involved in
Judicial system to integrate, share, process them better. The transparency in the legal trials are
very important and it can be maintained here very effectively.
In a nutshell the judicial processing is the flow of process from the submitting of a
case diary by the investigation team/ officer to court with adequate proofs, witness details,
11
investigation findings etc.. This Data has to learn by the public prosecutor and should available
to magistrate for trial in different way.
Each trials has to be scheduled, tracked and maintained to avoid delay in

processing.The software provides a best tool for managing their roles for investigation officers,
Magistrates, Shirasthars, Clerks, Public Prosecutor and even public as per its confidentiality and
need.
COMPANY PROFILE
Swift Institute of Next Education and Technology is a platform for the association,
formed after the conceptual merging of a long chain of branded and non branded training centers,
Placement cells, BPO Agencies , Manpower Recruiting Agencies across the country, to provide
cutting edge industry endorsed quality education with affordable cost. SINET has been acts as
high quality resource center for the prospective employees to leverage the up coming
opportunities effectively.
Sinet Logics is the software development division of Swift Institute of Next Education
and Technology One of the biggest information technology training brand established in south
India. SINET LOGICS is a leader and innovator in providing Outsourcing, Technology &
Consulting solutions. Over the past few years, we have delivered solutions for companies of all
sizes and in all stages of the corporate lifecycle across the globe, enabling higher performance,
delivering growth and profit generating opportunities. Our primary market focus in the shipping,
Cargo, Automobiles, Media & Entertainment and Utilities industries.
12
CHAPTER 2
SYSTEM STUDY
2.1 Existing System
The existing Judicial system does not have a complete integration of legal service activities
and legal personnel such as investigation officer, public prosecutor, judge and shirasthar. Lots of
civil or criminal cases has been lagging for years and not giving timely judgement.
The ONLINE LEGAL SERVICE ENHANCEMENT SYSTEM is a best solution for the existing
system as it has a complete integration of various authorities in a judicial system. We know that
in India any attempt to eliminate or to reduce the unfair delay of legal processing will be
appreciated. Drawbacks of the system:
13
Currently, in a court we can see that all records are handled manually in the form of files. All
records produced at the court are in the form of paper, due to this reason it is very difficult task to
keep the records.
The current Indian Legal System emphasizes less on technology and more on paperwork.
The absence of a complete integration of legal service activities and legal personalities in a
judicial system will cause case lagging and not giving timely judgment.
2.2 Proposed System

The ONLINE LEGAL SERVICE ENHANCEMENT SYSTEM is to help make legal
processes easier and more accessible to legal personalities such as investigation officer,
shirasthar, judge, public prosecutor and also press/public involved in the judicial system .
Investigation officer can login into the system using ‘case number’ and ‘password’. He /she can
then digitally enter investigation report on the case. These notes will be synchronized with the
main database, available to both public prosecutor and judge involved in the case. shirasthar
assign public prosecutor and judge for a particular case. Then they can digitally enter personal
notes on the case.
CHAPTER 3
SYSTEM ANALYSIS
3.1 Introduction
System analysis includes the investigation and possible changes to the existing system.
Analysis is used to gain an understanding of the existing system and what is required of it. At the
conclusion of the system analysis, there is a system description and a set of requirements for a
new system.
A detailed study of the process must be made by various techniques like interviews,
questionnaires etc. The data collected by these sources must be scrutinized to arrive to a
conclusion. The conclusion is an understanding of how the system functions. This system is
called the existing system. Now the existing system is subjected to close study and problem areas
14
are identified. The designer now functions as a problem solver and tries to sort out the difficulties
that the enterprise faces. The solutions are given as proposals. The proposal is then weighed with
the existing system analytically and the best one is selected. The proposal is presented to the user
for an endorsement by the user. The proposal is reviewed on user request and suitable changes
are made. This is loop that ends as soon as the user is satisfied with proposal. Preliminary study
is problem solving activity that requires intensive communication between the system users and
system developers. It does various feasibility studies. In these studies a rough figure of the
system activities can be obtained, which can be used to take decisions regarding strategies to be
followed for an effective system development.
The various task to be carried out in system analysis involves: examining the document
and the relevant aspects of the existing system, its failures and problems; analyse the findings and
record the results; define and document in outline the proposed system; test the proposed design
against the known facts; produce a detailed report to support the proposals; estimate the resource
required to design and implement the proposed system. The objective of this system study is to
determine whether there is any need for the new system. All the levels of the feasibility measures
have to be performed. Thereby knowing the performance by which a new system has to be
performed.
3.1.1 Problem definition

Problem Definition deals with observations, site visits and discussions to identify
analyze and document project requirements and carry out feasibility studies and technical
assessments to determine the best approaches for full system development.
Traditional judicial system is blamed for its long delay for processing
legal issues and not giving timely judgment. We are continue sly witnessing lots of civil or
criminal cases has been lagging for years. As a big secular democratic country we have
thousands of legal fighting between persons, states, political parties, NGOs etc. We know that in
India any attempt to eliminate or to reduce the unfair delay of legal processing will be
appreciated.
15
3.1.2 Requirement analysis
Requirements analysis in systems engineering and software engineering, encompasses
those tasks that go into determining the needs or conditions to meet for a new or altered product
or project, taking account of the possibly conflicting requirements of the various stakeholders,
analyzing, documenting, validating and managing software or system requirements.
Requirements analysis is critical to the success of a systems or software project Requirement
analysis for the Digital Security Surveillance system outputs the following results.
System analysis is a detailed study of various operations performed by a system
within and outside the system. One aspect of analysis is defining the boundaries of the system
and determining whether or not a candidate system should consider other related system. During
analysis data are collected on available file, no such existing system, analysis defines only the
requirements. Once the analysis is completed; the system analyst has a firm understanding of
what is to be done.
The online legal service management system is such an attempt to reduce the irritating
lagging in judicial service. Here we are focusing different agencies or personal those involved in
Judicial system to integrate, share, process them better. The transparency in the legal trials are
very important and it can be maintained here very effectively.In a nutshell the judicial processing
is the flow of process from the submitting of a case diary by the investigation team/ officer to
court with adequate proofs, witness details, investigation findings etc.. This Data has to learn
by the public prosecutor and should available to magistrate for trial in different way.
The various techniques used in the study of present system are
• Observation
• Documentation
• Discussion
The objectives of the system analysis phase are establishments of requirements for the
system to be acquired, developed, and installed. Analyzing the product to understand the
intricacy forms the vital part of the system study. Problematic areas are indentified and
information is collected. Fact-finding or information gathering is essential to any analysis of
requirements.
16
3.2 FEASIBILITY STUDY
The feasibility of the project is analysed in this phase and business proposal is put
forth with a very general plan for the project and some cost estimates. During system analysis the
feasibility study of the proposed system is to be carried out. This is to ensure that the proposed
system is not a burden to the company.
Three key considerations involved in the feasibility analysis are
• Operational feasibility
• Technical feasibility
• Economic feasibility
• Social feasibility
3.2.1 Operational feasibility

The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the user about the system and
to make him familiar with it. His level of confidence must be raised so that he is also able to
make some constructive criticism, which is welcomed, as he is the final user of the system.
3.2.2 Technical feasibility

This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the available
technical resources. This will lead to high demands on the available technical resources being
placed on the client. The developed system must have a modest requirement, as only minimal or
null changes are required for implementing this system.
3.2.3 Economical feasibility

This study is carried out to check the economic impact that the system will have on the
organization. The amount of fund that the company can pour into the research and development
17
of the system is limited. The expenditures must be justified. Thus the developed system as well
within the budget and this was achieved because most of the technologies used are freely
available. Only the customized products had to be purchased.
3.2.4 Social feasibility

The aspect of study is to check the level of acceptance of the system by the user. This
includes the process of training the user to use the system efficiently. The user must not feel
threatened by the system, instead must accept it as a necessity. The level of acceptance by the
users solely depends on the methods that are employed to educate the user about the system and
to make him familiar with it. His level of confidence must be raised so that he is also able to
make some constructive criticism, which is welcomed, as he is the final user of the system.
CHAPTER 4
SYSTEM SPECIFICATION
4.1 Hardware Requirements
Following are the hardware minimum required for the proposed system
Processor : Intel(R) Core

Hard Disk : 240 GB
RAM : 4 GB
18
Speed : 2.0 GHz
Monitor : Compaq 18.5 inches
4.2 Software requirements
Following are the software minimum required for the proposed system
User-Interface : PHP
Language used : PHP, HTML, BOOTSTRAP, JavaScript
Software Tools : WAMP server
DBMS : Mysql
Web Server : WAMP server
Operating System : Windows 10
CHAPTER 5
SOFTWARE DESCRIPTION
5.1 PHP:
PHP is a powerful tool for making dynamic and interactive Web pages. I is the
widely used, free, and efficient alternative to competitors such as Microsoft's ASP.PHP
files can contains text, html tags and scripts. The PHP files returned to the browser as
plain HTML.
The extension of PHP files are “.php”, “.php3”, “.phtml”.It is a server-side scripting
language, like ASP. It supports many databases (MySQL, Informix, Oracle, Sybase, Solid
etc.
19
5.2 MySQL SERVER :
MySQL is an open source, SQL Relational Database Management System

(RDBMS) that is free for many uses. Early in its history, MySQL occasionally faced
opposition due to its lack of support for some core SQL constructs such as sub selects and
foreign keys. Ultimately, however, MySQL found a broad, enthusiastic user base for its
liberal licensing terms, perky performance, and ease of use. Its acceptance was aided in
part by the wide variety of other technologies such as PHP, Java, Perl, Python, and the like
that have encouraged its use through stable, well-documented modules and extensions.
5.3 JAVASCRIPT:
JavaScript is an object-oriented scripting language used to enable programmatic

access to objects with both the client application and other applications .It is primarily
used in the form of client-side JavaScript, implemented as an integrated component of the
web browser, allowing the development of enhanced user interface and dynamic website.
5.4 WAMP
WAMP are packages of independently-created programs installed on computers

that use a Microsoft Windows operating system. The interaction of these programs
enables dynamic web pages to be served over a computer network, such as the internet or
a private network.
“WAMP” is an acronym formed from the initials of the operating system (windows)
and the package’s principal components: Apache, MySQL and PHP(or Perl or python).
Apache is a web server, which allows people with web browsers like Internet Explorer or
Firefox to connect to a computer and see information there as web pages. MySQL is a
20
database manager that keeps track of data in a highly organized way. PHP is a scripting
language which can manipulate information held in a database and generate web pages
afresh each time an element of content is requested from a browser. Other programs may
also be included in a package, such as phpMyAdmin which provides a graphical interface
for the MySQL database manager, or the alternative scripting languages Python or Perl.
5.5 SUBLIME TEXT
Sublime Text is a proprietary cross-platform source code editor with a Python

application programming interface (API). It natively supports many programming languages
and markup languages, and functions can be added by users with plugins, typically
community-built and maintained under free-software licenses. Sublime Text contains 23
different visual themes, with the option to download additional themes and configure custom
themes via third-party plugins. The minimap feature shows a reduced overview of the entire
file in the top-right corner of the screen. The portion of the file visible in the main editor pane
is highlighted and clicking or dragging in this view scrolls the editor through the file. The
program offers a number of screen modes including panels that can show up to four files at
once as well as full screen and distraction free modes which only show one file without any
of the additional menus around it.
CHAPTER 6
PROJECT DESCRIPTION
6.1 Overview of the Project

Digitizing the legal system will eliminate the problem of storage of documents.
Successful automation of court procedures will reduce lagging in judicial system and giving
timely judgement.
Information available – The main advantage of an ONLINE LEGAL SERVICE

ENHANCEMENT SYSTEM is that the public prosecutor and judge can available the entire
information related to all assigned cases through online.
21
Easy access – With the help of internet, the documents of a case can be accessed easily from
anywhere at anytime.
Better court operation management –The ONLINE LEGAL SERVICE ENHANCEMENT

SYSTEM would help in the computerization of work flow management in courts. Thus, it would
help to create a better court operation management. And each trials has to be scheduled, tracked
and maintained to avoid delay in processing.
MODULES
• Investigation Agency
• Public Prosecutor
• Magistrate
• Court Office
• Administrator
• Press and Publics
6.2 MODULE DESCRIPTION
INVESTIGATION OFFICER
• Registration for a particular case.
• Submit Case data like First Investigation Report, Witness Details, Evidence List
etc..
• Edit submitted data before Approving Court Admin ( 24 Hours)
• View submitted data about a particular case

(Submitted Data, Trial history, Next Trial Date..)
SHIRASTHAR
• Enter General trial Data against a particular case
22
• Enter the detailed court orders, sub orders, law points, findings etc..
• Assign judge or public prosecutor for a particular case.
ADMINISTRATOR
• Processing and approval of new users.
• Handling of primary information for the system.
• Deal with the feedbacks, Complaints etc
• Setting Privileges to Investigators, Public Prosecutor, Magistrate and shirasthar
• Providing functional security to modules
• Defining various reports
• Maintaining log data for complete activities.
JUDGE
• He can view the details of all assigned cases
• View all case data excluding the personal Notes of Public prosecutor
• View the trial history of a selected case
• View the general Data posted by Shirasthar / Clerks
Can write personal notes about a case
PUBLIC PROSECUTOR
• See the Case data after selecting the case number as he is responsible to attend in
trial.
23
• Update the trial data after login See the case trial orders of Judge
CHAPTER 7
SYSTEM DESIGN
7.1 Data Flow Diagram
Data flow diagram is a way of representing system requirements in a graphic form. A

DFD also known as “Bubble Chart” has the purpose of clarifying system requirements and
identifies major transformations that will become program in system design. So it is the starting
point of design phase that functionally decomposes the requirements specifications down to the
lowest level of details. A DFD consist of series of bubbles joined by lines. The bubbles represent
data transformation and the lines represent data flow in the system.
24
Level-0
25
Administrator
Public Investigator
Online
Legal
Service
Shirasthar Public Prosecutor
Judge
26
Level-1
Submit
Investigator case and
login
Attend
Public Prosecutor
cases
Judgem dblegal
Judge ent
Case
Shirasthar submiss
ion
Verify
Administrator the
users
View
Public cases and
feedback
27
Level-2.1
28
Level-2.2
29
Level-2.3
30
Level-2.4
31
Level-2.5
32
Level-2.6
Feedback feedback
Public
Case tbl_casetrial
Trails
DFD Symbols
In a DFD there are four symbols
A square defines a source or destination of system data.
An arrow identifies data flow in motion. It is a pipeline through which in

format flows
33
A circle or a bubble represents a process that transforms
incoming data flows into going data flows.
An open rectangle is a data source or data at rest or a temporary of

data constructing a DFD.
Rules in drawing DFD’s
• Process should name and numbered for easy reference.
• The direction of flow is from top to bottom and from left to right. Data traditionally flow
from source to destination, although they may flow from source.
• When a process is exploded into lower levels, they are numbered.
• The names of data source, sources and destination are written in capital letters. process
and data flow names have the first letter of each word capital
A DFD is often used as a preliminary step to create an overview of the system, which can
later be elaborated. The DFD is designed to aid communication. The rule of thumb is exploding
the DFD to a functional level, so that the next sublevel does not exceeds to process. Beyond that
it is best to take each function separately and expand it to show the explosion of single process.
Data flow diagrams are one of the three essential perspectives of the structured-systems analysis
and design method SSADM. With a data flow diagram, users are able to visualize how the
system will operate, what the system will accomplish, and how the system will be implemented.
34
It is a common practice to show the interaction between the system and external agents which act
as data sources and data sinks.
7.2 ER Diagram
35
36
7.3 Database Table Structure
TBLADMINLOGIN
Fieldname Type Null Default
Username Varchar(50) Not null Null
Password Varchar(50) Not null Null
Primary Key: Username
TBLACCUSED_INFO
Field Name Type Null Default
Accuse_No Int(11) Not null Null
Case_No Int(11) Not null Null
Name Varchar(50) Not null Null
Address Varchar(100) Not null Null
Age Varchar(11) Not null Null
Telephone Varchar(11) Not null Null
Status Varchar(50) Not null Null
Gender Varchar(10) Not null Null
Primary Key : Accused_No
Foreign Key : Case_No TBLDISTRICT
37
Field Name Null Default
District_id Not null Null
Name Not null Null
State_id Not null Null
Primary Key : District_id
Foreign Key : State_id
TBLWITNESS_INFO
Case_no Int(11) Not null Null
Witness_No Int(11) Not null Null
Date_of_birth Date Not null Null
Phone_no Varchar(10) Not null Null
Primary Key : Witness_No
Foreign Key : Case_no TBLEVIDENCE DETAILS

Evidence_No Int(50) Not null Null
Officer_Name Varchar(50) Not null Null
Date_of_submission Date Not null Null
38
Title Varchar(500) Not null Null
Script Varchar(50) Not null Null
Attachment’s Varchar(50) Not null Null
PrimaryKey : Evidence_No
Foreign key : Case_No
MAHASSAR
Mahassar_No Varchar(10) Not null Null
Case_No Varchar(10) Not null Null
Attachments Varchar(50) Not null Null
Primary key : Mahassar_No

Foreign Key : Case_No CHARGE_SHEET
Charge_sheet _No Int(11) Not null Null
39
Primary Key : Charge_sheet _No
Foreign Key : Case_No
TBLADMINLOGIN
Adminid Int(11) Not null Null
Primary Key : Adminid TBL_CASE TRIAL

Trial_No Int(10) Not null Null
Date_of_trial Date Not null Null
Title_of_case Varchar(50) Not null Null
Magistrate Varchar(50) Not null Null
Prosecutor_incharge Varchar(50) Not null Null
Trial_description Varchar(100) Not null Null
Trial_order Varchar(100) Not null Null
Next_trial_date Date Not null Null
Primary Key : Trial_No Foreign Key : Case_No
40
TBL_PATITIONER
Age Int(11) Not null Null
Contact Varchar(10) Not null Null
File_Name Varchar(40) Not null Null
Foreign Key : Case_No
TBL_JUDGEACTIVITY
Activity_no Varchar(50) Not null Null
Date Date Not null Null
Note Varchar(500) Not null Null
Description Varchar(200) Not null Null
Attach Varchar(50) Not null Null
Primary Key : Activity_no Foreign Key : Case no
41
FEEDBACK
F_id Int(11) Not null Null
Message Text Not null Null
Contact Varchar(20) Not null Null
Primary Key : F_id
TBLSTATES
Null Default
Fieldname Type
Not null Null

State_id Int(11)
Not null Null

Name Varchar(200)
Primary Key : State_id
TBLINVESTIGATOR_REG
User_id Int(11) Not null Null
State_id Int(11) Not null Null
District_id Int(11) Not null Null
Office Varchar(50) Not null Null
42
Position Varchar(50) Not null Null
Phone Varchar(10) Not null Null
Email Varchar(50) Not null Null
Primary Key : User_id
Foreign Key : State_id, District_id TBLPP_ACTIVITY

Activity_no Int(11) Not null Null
Trial_description Varchar(500) Not null Null
Note Varchar(500) Not null Null
Attach Varchar(50) Not null Null
Primary Key : Activity_no
Foreign Key : Case_no TBLSHIRASTHAR_REGISTER
43
User_id Int(10) Not null Null
User_name Varchar(50) Not null Null
Office Varchar(50) Not null Null
State Int(11) Not null Null
District Int(11) Not null Null
Name_court Varchar(50) Not null Null
Mobile Varchar(10) Not null Null
Land Varchar(10) Not null Null
Primary Key : User_id
Foreign Key : State, District TBLPROSECUTER_REG
field_name Type Null Default
Not null Null

Prosecutor_id Int(11)
Not null Null

Fname Varchar(50)
Not null Null

Lname Varchar(50)
44
Not null Null
Password Varchar(300)
Not null Null

Address Varchar(500)
Not null Null

State Int(11)
Not null Null

Gender Varchar(10)
Not null Null

Age Int(11)
Not null Null

Phone Varchar(11)
Primary Key : Prosecutor_id
Foreign Key : State, District TBLCASE_REG

State Int(11) Not null Null
Police_Station Varchar(50) Not null Null
Time Time Not null Null
Tittle Varchar(50) Not null Null
45
Fir_No Int(11) Not null Null
Attach_File Varchar(50) Not null Null
Judge Varchar(50) Not null Null
Primary Key : Name
Foreign Key : Case_No, State, District
7.4 INPUT DESIGN
Input design is a part of overall system design, which requires careful attention. It is the
process of converting user-originated inputs to a computer-based format. The major objective of
the input design is to make data entry easy, logical and error free.
As a beginner it is easy to start with PHP. The user just have to add a few PHP-tags with
e.g. a for-loop in it's existing HTML-files and then upload it to the server and see the result or an
error message. Dynamic typing and associative arrays makes it also easier to start using PHP.
Easy to use Compared to most solutions like e.g. Java, PHP doesn't need to be compiled, so it's
just to write the script and then upload it to the server and then update the browser.
This application has been developed in a user-friendly manner. The layout of the form is
made in such a way that the user will not find any difficulty in going from one field to other by
just pressing the tab. During the processing the cursor is placed in the position where the data
must be entered.
The user is also provided with an option of selecting an appropriate input from a list of
values. Necessary dropdown list boxes and combo boxes are included for necessary fields so that
the user need not remember all the data and can just select from it.
46
Validation is made for each and every data entered. Help messages are also provided
whenever the users enter a wrong data into a particular field. This makes the user to understand
what is to be entered, moreover whenever an erroneous data is entered the error message is
displayed and the user can move to the next field only after entering the correct data.
The clear label for the menus and fields are also provided. Consultations are provided so
that a user can view the details of any process at any time.
7.5 OUTPUT DESIGN
One of the most important features of a system for users in the output it produces. Output
design should improve the system’s relationship with the user and help in decision-making.
Considering the future use of output required, and depending on the nature, it is displayed on the
monitor for immediate need of obtaining the hard copy.
The objective of output design is to define the controls and format of all printed
documents and reports and of screens that will be produced by the system. Computer output is
the most important and direct source of information to the user.
Objectives Of Output Design
1. Design output to serve the intended purpose.
2. Deliver the appropriate quality of output.
3. Choose the right output method.
4. Provide output on time.
47
Output, generally refers to the results that are generated by the system. The output of the
system is designed so as to include number of reports. Reports reflect the output design.
7.6 DATABASE DESIGN
The activity deals with the design of the database. A key is to determine how the access
paths are to be implemented. A physical path is derived from a logical path. The general theme
behind database is to handle information as a whole. A database is a collection of interrelated
data stored with minimum redundancy to serve many users quickly and efficiently.
The general objective is to make information access easy, quick, inexpensive and flexible
for the user. Database design is the most critical part of the design phase. An elegantly designed,
well-defined database is a strong foundation for the whole system. Files in a relational database
are called as tables. Columns of tables represent data and rows represent the records in
conventional technology.
48
CHAPTER 8
SYSTEM TESTING
8.1 Introduction
Software testing is an investigation conducted to provide stakeholders with information
about the quality of the product or service under test. Software testing also provides an objective,
independent view of the software to allow the business to appreciate and understand the risks at
implementation of the software. Test techniques include, but are not limited to, the process of
executing a program or application with the intent of finding software bugs.
8.1.1 Testing Objective

• Testing is a process of executing a program with the intend of finding an error.
• A good test case is one that has high probability of finding an undiscovered error.
• A successful test is one that uncovers an as-yet undiscovered error.
8.1.2 Testing Principles

• All tests should be traceable to customer requirements.
• Test should be planned long before testing begins.
• The Pareto principle can be applied to software testing is 80% of all errors uncovered
during testing will likely be traceable to 20% of all program modules.
49
• Testing should begin “in the small” and progress toward testing “in the large”.
• To be most effective, testing should be conducted by an independent third party.
8.2 Types of Testing
There are different types of testing techniques used in software engineering. Out of these
DSS uses Unit Testing, Integration Testing, Validation Testing, Output Testing and User
Acceptance Testing.
System testing includes code testing which examines the logic of the program. Each and
every part of the program is checked or executed individually to find out the errors. Once the
errors in the program are found out, they are debugged. If wrong data is entered, an error
message is displayed on the screen so that the user can correct the data at that time itself.
System testing is actually a series of different tests whose primary purpose is to fully
exercise the computer based system. A series of testing are performed for the proposed system
before the system is ready for the user acceptance test. A candidate system is subject to variety
of tests – volume, stress, recovery, security and usability tests.
The steps in the system testing can be categorized as follows:
• Unit Testing
• Requirement Testing
• User Testing
• Validation Testing
50
• Integration Testing
• User Acceptance Testing
8.2.1 Unit Testing

Unit testing focuses on verification efforts on the smallest unit of software design i.e., the
module. The unit testing is always white box oriented and the step can be conducted in parallel
for modules. The module interface is tested to ensure that information properly flows in and out
of the program unit under test. The ‘local data structures ‘ are examined to ensure that data stored
temporarily maintains its integrity during all steps in an algorithm execution.” Boundary
Conditions” are tested to ensure that the module operates properly at boundaries established to
limit or restrict processing. All ‘independent paths ‘ through the control structures are exercised
to ensure that all statement in a module have been executed at least once. Finally all “
ErrorHandling “ are tested.
8.2.2 Requirement Testing

The main aim of this test plan is to see whether the outputs created and inputs were given
according to the user requirements and specifications that have been established. This was done
in the security department by having the developer as a secondary person and another employee
who conducted the actual test. Some Suggestion was made while requirement testing was done
that has been incorporated.
8.2.3 User Testing

During the testing the tester places the role of the individual who desires to penetrate the
system. The tester may attempt to acquire passwords through external clerical means and may
attack the system with the custom software design to break down any defenses that have been
constructed. The tester may also overwhelm the system thereby denying service to other s and
may purposely cause system errors to penetrate during recovery and may browse through
insecure data, hoping to find key to system entry.
51
8.2.4 Validation Testing
At the end of user testing, software is completely assembled as a package, interfacing errors
have now being uncovered and correcting test begins. Software testing and validation are
achieved through a serious black box tests that demonstrate conformity with the requirement.
A plan outlines the classes of tests to be conducted and test procedure defines specific
cases that will be used to demonstrate conformity with requirements. Both the plan and the
procedure are designed to ensure that all functional requirements are achieved, documentation is
correct and other requirements are met. After the validation test, one of the conditions exists.
They are,
The function or performance characteristics confirm to specification and are accepted. A
deviation from the specification is uncovered and a deficiency list is created. The deviation or
error discovered at this stage in a project can rarely be corrected prior to scheduled completion. It
is necessary to negotiate with the customer to establish methods.
8.2.5 Integration testing

Integration testing is a systematic technique for constructing the program structure while
conducting tests to uncover errors associated with interfacing. The objective is to take unit
testing modules and build a program structure that has been dictated by design.
There is often a tendency to attempt non incremental integration; that is to construct the
program using “big-bang” approach. All modules are combined in advance. The entire program
is tested as a whole. When a set of errors is encountered, correction is difficult because isolation
of causes is complicated by the vast expanse of the entire program. Once these errors are
corrected new ones appear and the process continues in a seemingly endless loop.
Incremental integration is the antithesis of big-bang approach. The program is constructed
and tested in small sequence, where errors are easier to isolate and correct; interfaces are more
likely to be tested completely; and a systematic test approach may be applied.
52
8.2.6 User acceptance testing
Acceptance testing involves planning and execution of functional tests, performance test,
and stress tests to verify that the implemented system satisfies its requirements. Acceptance tests
are typically performed by quality assurance and/or customer organizations. Functional and
performance tests are performed to determine the limitations of the system. Typically ,
acceptance typically, acceptance test will incorporate test cases developed during unit testing and
integration testing. Additional test cases are added to achieve desired level of functional ,
performance, and stress testing of the entire system. Tools of Special importance during
acceptance testing include a test Coverage analyzer, a timing analyzer, and a coding standards
checker. A test coverage analyzer records the control paths followed for each test case. Timing
analyzer reports the time spent in various regions of the source code and different test cases.
passed or failed such a test is known as a test oracle. In some settings, an oracle could be a
requirement or use case, while in others it could be a heuristic. It may take many test cases to
determine that a software program or system is considered sufficiently scrutinized to be released.
Test cases are often referred to as test scripts, particularly when written - when they are usually
collected into test suites. IN order to fully test that all the requirements of an application are met,
there must be at least two test cases for each requirement: one positive test and one negative test.
If a requirement has sub-requirements, each sub-requirement must have at least two test cases.
Keeping track of the link between the requirement and the test is frequently done using a
traceability matrix.
53
8.3 Sample Test Cases
Investigation officer reg.php
Test Case Actual Result Expected Result Test Result
Error in Email ID Display Message “ Display Message Passed
The email must be in “The email must be in a
valid format ” valid format ”
Error in Phone Display Message “ Display Message “ Passed
Number Invalid Phone Invalid Phone
Number” Number
”
Registered user Display Message Display Message Passed
trying to register “User already “ Email already
available” available”
Error in every field Display Message “ Display Message Passed
with null value. Name must be filled “* The field is
out ” required”
All required fields Display Message Display Message Passed
entered with correct “successfully “successfully
values Registered” Registered”
Public prosecutor Registration

Number” Number
”
out ” required”
54
Judge registration
Number” Number
”
out ” required”
Field require only Display Message Display Message Passed
numeric values
“only numeric “only numeric
values accept” values accept”
Investigation_officer login
Test case Actual result Expected Result Test result
Error in every field Display message “The field is passed

with null value required”
Display Message “The
field is required”
55
Error in user name and Display Message ” passed
password Your Login Name or
Display Message ” Your
Password is invalid” Login Name or Password is
invalid”
Admin login
Test case Actual result Expected Result Test result
Error in every field Display Message “The Display message “The field is passed
with null value field is required” required”
Error in user name and Display Message ” Your passed

password
Login Name or
Display Message ” Your
Password is invalid” Login Name or Password is
invalid”
56
CHAPTER 9
SYSTEM IMPLEMENTATION
9.1 Implementation Planning:

This section describes about the Implementation of the Safe application and the details of
how to access this control from any application.
Implementation is the process of assuring that the information system is operational and
then allowing users take over its operation for use and evaluation. Implementation includes the
following activities.
• Obtaining and installing the system hardware.
• Installing the system and making it run on its intended hardware.
• Providing user access to the system.
• Creating and updating the database.
• Documenting the system for its users and for those who will be responsible for
maintaining it in the future.
• Making arrangements to support the users as the system is used.
57
• Transferring ongoing responsibility for the system from its developers to the operations or
maintenance part.
• Evaluating the operation and use of the system.
9.2 Implementation Phase in this project:

The new system of Electronic Land Information Management System has been
implemented. The present system has been integrated with the already existing hardware. The
database was put into the WAMP server. This was connected by PHP. The database is accessible
through Internet on any geographic location. Documentation is provided well in such a way that
it is useful for users and maintainers.
9.3 Maintenance:
Maintenance is any work done to change the system after it is in operational. The term
maintenance is used to describe activities that occur following the delivery of the product to the
customer. The maintenance phase of the software life cycle is the time period in which a software
product performs useful work.
Maintenance activities involve making enhancements to products, adapting products to new
environments, correcting problems.
In this be retrieve the data from the database design by searching the database. So, for
maintaining data our project has a backup facility so that there is an additional copy of data,
which needs to be maintained.
9.4 Methods of implementation:
The four basic methods of implementation are:
1. Parallel system method.
58
2. Direct cut over method.
3. Pilot system method.
4. Phase in method.
59
CHAPTER 10
CONCLUSION AND FUTURE ENHANCEMENT
10.1 CONCLUSION
“Online legal service enhancement system “is successfully designed and implemented
according to the requirements and specifications. It helps the people and authorities to get
the legal service easily and transparently without lagging.
This software is designed in such a way that anyone without having much
knowledge about the computer can be used. Instinct and common sense can guide a user.
Point and click method is used. The necessary information can be fed into the input
screens. The user does not meet with any complication when using the system. The
customized modules satisfy the user needs.
The system is done with insight into the necessary modifications that may
be required in the future. Hence the system can be maintained successfully without much
rework. The system was tested with proper user gets timely and accurate information from
this system.
10.2 Scope for Future Enhancement

The Online legal service enhancement system has been designed and developed
according to the current information and records of the Judicial First class Magistrate
Court. This system is very flexible so that the maintenance and further amendments based
on the changing environment and requirements can be made easily with adding further
information.
Further enhancement is possible to updating Court functions and activities. This can be
restructured as required.
In order to make modifications effectively there should be more communications update with
admin and the user.
1) Reusability – It is possible as and when require in this application. we can

update its next version Reusable software reduces design, coding and testing
cost by amortizing effort over several designs.
60
2) High Court - We can share the data and merit of case to higher court if the case
of appeal.
61
APPENDICES
Source Code
Admin Login Page

<?php
// *** Validate request to login to this site.
if (!isset($_SESSION)) {
session_start();
$loginFormAction = $_SERVER['PHP_SELF'];
if (isset($_GET['accesscheck'])) {
$_SESSION['PrevUrl'] = $_GET['accesscheck'];
} if (isset($_POST['txtAdminid']))
$loginUsername=$_POST['txtAdminid'];
$password=$_POST['txtPassword'];
$MM_fldUserAuthorization = "";
$MM_redirectLoginSuccess = "verify.php";
$MM_redirectLoginFailed = "adminlogin.php";
$MM_redirecttoReferrer = false;
mysql_select_db($database_conLegal, $conLegal);
$LoginRS__query=sprintf("SELECT adminid, password FROM tbladminlogin WHERE adminid=%s

AND password=%s",
GetSQLValueString($loginUsername, "int"), GetSQLValueString($password, "text"));
62
$LoginRS = mysql_query($LoginRS__query, $conLegal) or die(mysql_error()); $loginFoundUser =
mysql_num_rows($LoginRS); if ($loginFoundUser) { $loginStrGroup = ""; if (PHP_VERSION
>= 5.1) {session_regenerate_id(true);} else {session_regenerate_id();}
//declare two session variables and assign them
$_SESSION['MM_Username'] = $loginUsername;
$_SESSION['MM_UserGroup'] = $loginStrGroup;
if (isset($_SESSION['PrevUrl']) && false) {
$MM_redirectLoginSuccess = $_SESSION['PrevUrl'];
header("Location: " . $MM_redirectLoginSuccess );
else {
//header("Location: ". $MM_redirectLoginFailed );
$error="Incorrect Admin ID Or Name Or Password";
?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"

"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" href="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/css/bootstrap.min.css">
63
<script src="https://ajax.googleapis.com/ajax/libs/jquery/3.2.1/jquery.min.js"></script>
<script src="https://maxcdn.bootstrapcdn.com/bootstrap/3.3.7/js/bootstrap.min.js"></script>
<title>Legal Service</title>
<script src="../SpryAssets/SpryValidationTextField.js" type="text/javascript"></script>
<script src="../SpryAssets/SpryValidationPassword.js" type="text/javascript"></script>
<link href="../SpryAssets/SpryValidationTextField.css" rel="stylesheet" type="text/css" />
<link href="../SpryAssets/SpryValidationPassword.js" rel="stylesheet" type="text/css" />
<link rel="stylesheet" href="../css/style.css" type="text/css" />
<link rel="stylesheet" href="../sty.css" type="text/css" />
<link rel="stylesheet" href="../css/ie.css" type="text/css" charset="utf-8">
<link href="../SpryAssets/SpryValidationSelect.css" rel="stylesheet" type="text/css" />
</script>

<link rel="stylesheet" href="../css/bootstrap.css" />
<link rel="stylesheet" href="../css/style.css" />

</head>
<body>
<div id="page">
<div id="header">
<a href="" id="logo"><img src="../images/llogo.png" alt="LOGO" height="150"></a>
<ul id="navigation">
<li class="selected">
<a href="../index.php" title="Home"></a>
64
</li>
<li>
<a href="../aboutt.php">About</a>
</li>
<li class="last-child">
<a href="../contacts.php">Contacts</a>
</li>
</ul>
</div>
<div id="headline"><div class="body">
<h2 align="center">ADMIN LOGIN</h2>
</div>
</div>
<div id="main">
<form action="<?php echo $loginFormAction; ?>" method="POST" name="admin">
<div class="col-sm-3"></div>
<div class="col-sm-5" align="center">
<div align="left" class="col-sm-12">
<span id="sprytextfield2">
<label for="txtAdminid">Admin ID:</label>
<input type="text" name="txtAdminid" id="txtAdminid" class="form-control"/>
<span class="textfieldRequiredMsg">A value is required.</span></span>
<p> </p>
</div>

65
<span id="sprytextfield1">
<label for="txtAdmin">Admin name:</label>
<input type="text" name="txtAdmin" id="txtAdmin" class="form-control"/>
<span class="textfieldRequiredMsg">A value is required.</span></span>
<p> </p>
</div>
<span id="sprypassword1">
<label for="txtPassword">Password:</label>
<input type="password" name="txtPassword" id="txtPassword" class="form-control"/>
<span class="passwordRequiredMsg">A value is required.</span></span>
<p> </p>
</div>
<div align="center" class="col-sm-4"></div>
<div align="center"><span class="col-sm-4">
<input name="btnLogin" type="submit" value="Login" class="btn-danger" />
</span>
<p> </p>
</div>
<div class="col-sm-12" style="color:#F00";><?php echo $error;?></di>
</div>
</form>
</div>
</div>
66
<div>
<div id="footer" class="col-sm-12" align="center">
<div class="connect">
</div>
</div>
</div>
<script type="text/javascript"> var sprytextfield1 = new
Spry.Widget.ValidationTextField("sprytextfield1"); var sprypassword1 = new
Spry.Widget.ValidationPassword("sprypassword1"); var sprytextfield2 = new
Spry.Widget.ValidationTextField("sprytextfield2");
</script>
</body>
</html>
67
7.4 Screen Shots
INDEX PAGE
68
USER LOGIN
ACCUSED INFORMATION
69
SHIRASTHAR CASE ASSIGN
EVIDENCE DETAILS
70
INVESTIGATION REPORT
MAHASSAR DETAILS
71
ADMIN LOGIN
ADMIN USER VERIFY
72
INVESTIGATOR REGISTRATION
JUDGE REGISTRATION
73
PROSECUTOR REGISTRATION
SHIRASTHAR REGISTRATION
74
ADD STATE
ADD DISTRICT
75
VIEW FEEDBACK
MANAGE DISTRICT
76
MANAGE STATE
WRONG PASSWORD
77
INVESTIGATOR PROFILE
CASE REGISTRATION
78
CASE LOGIN
PATITIONER INFORMATION
79
WITNESS DETAILS
MAHASSAR DETAILS
80
VIEW PATITIONER
81
VIEW ACCUSED
VIEW EVIDENCE
82
VIEW MAHASSAR
CASE OF JUDGE
83
PROFILE OF JUDGE
ACTIVITY OF JUDGE
84
ACTIVITY DETAILS OF JUDGE
CASE OF PROSECUTOR
85
LOGIN OF PROSECUTOR
86
ACTIVITY OF PROSECUTOR
CASE OF SHIRASTHAR
87
DETAILS OF CASE
ASSIGN CASE
88
MEMBERS
CASE TRAILS
89
REFERENCES
References
1. Lonnie D Bentley, "System Analysis and Design" - Galgotia Publications, 2006
2. Roger.S.Prssman,"Software Engineering" -Tata McGraw-Hill, 1999
3. Paul Dubois, "SQL Server Cookbook" -O’Reilly Media, 2007
Web Reference:
www.w3schools.com
www.microsoft.com
90
91

Lenin Peter

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Lenin Peter

Загружено:

Авторское право:

Доступные форматы

DATA LEAKAGE DETECTION

in partial fulfilment for the award of the degree of

MASTER OF COMPUTER APPLICATIONS

DEPARTMENT OF COMPUTER APPLICATIONS

NEHRU INSTITUTE OF INFORMATION TECHNOLOGY

AND MANAGEMENT, COIMBATORE – 641 105.

ANNA UNIVERSITY,CHENNAI - 600 025

Dr. R. Thiyagarajan M.Sc., M.C.A., Ms. C. Meera Bai M.C.A., M.Phil.

Submitted for the project Viva – Voce examination held on __________

Internal Examiner External Examiner

I affirm that the project work titled “DATA LEAKAGE DETECTIVE

I certify that the declaration made above by the candidate is true.

Signature of the Supervisor

I express heartfelt thanks to my Head of the Department Dr.R.Thiyagarajan M.Sc., M.C.A.,

I am thankful to the management and Mr.Shameer Project Manager of Sinet Logics,

6 1 1.2 Company Profile. 2

7 2.1. Existing System 4

8 2.2. Proposed System 4

12 3.2. Feasibility Study 7

13 3.2.1. Operational Feasibility 7

14 3.2.2. Technical Feasibility 7

22. 6.2 Module Description 16

23 7.1. Data Flow Diagram 17

25 7.3. Database Table Structure 23

26 7.4. Input Design 29

27 7.5. Output Design 29

28 7.6. Database Design 30

34 8.2.3 User Testing 33

Sl. No. Symbol Purpose

Each trials has to be scheduled, tracked and maintained to avoid delay in

2.1 Existing System

2.2 Proposed System

3.1.1 Problem definition

Three key considerations involved in the feasibility analysis are

3.2.1 Operational feasibility

3.2.2 Technical feasibility

3.2.3 Economical feasibility

3.2.4 Social feasibility

4.1 Hardware Requirements

Processor : Intel(R) Core

4.2 Software requirements

MySQL is an open source, SQL Relational Database Management System

JavaScript is an object-oriented scripting language used to enable programmatic

WAMP are packages of independently-created programs installed on computers

5.5 SUBLIME TEXT

Sublime Text is a proprietary cross-platform source code editor with a Python

6.1 Overview of the Project

Information available – The main advantage of an ONLINE LEGAL SERVICE

Better court operation management –The ONLINE LEGAL SERVICE ENHANCEMENT

6.2 MODULE DESCRIPTION

• Edit submitted data before Approving Court Admin ( 24 Hours)

• View submitted data about a particular case

• Assign judge or public prosecutor for a particular case.

• Handling of primary information for the system.

• Deal with the feedbacks, Complaints etc

• Setting Privileges to Investigators, Public Prosecutor, Magistrate and shirasthar

• Providing functional security to modules

• Defining various reports

• Maintaining log data for complete activities.

• He can view the details of all assigned cases

• View the trial history of a selected case

• View the general Data posted by Shirasthar / Clerks