JUDICIAL BIOGRAPHY SYSTEM

Project Report

Submitted for the partial fulfillment for the award of degree of

BACHELOR OF COMPUTER APPLICATIONS

By

Name
Register Number

Under the Guidance of

Guide Name

DEPARTMENT OF COMPUTER APPLICATIONS (UG)

SACRED HEART COLLEGE (AUTONOMOUS) TIRUPATTUR,

TIRUPATTUR DIST-635 601

JUNE 2022

1
 CERTIFICATE

This is to certify that the report entitled

WEBSITE FOR YOUTH SOCIAL RESPONSIBILITY

Being submitted to the Thiruvalluvar University, Vellore

By

Name

Register Number
For the partial fulfillment for the award of degree of

BACHELOR OF COMPUTER APPLICATIONS

Is a bona-fide record of work carried out by her under my guidance and Supervision.

Signature of the Guide Signature of the Head

Date:

Submitted for the viva-voce examination held on _____________ Examiners:

1.

2.

2
ACKNOWLEDGEMENT

At the very outset I offer my sincere thanks to Almighty God for the grace and blessings
that made me to complete the project in a successful manner.

I would also like to thank my second god my parents and my friends gave me this life and
guiding all my way to success.

As I submit the project report it gives me great pleasure to acknowledge my gratitude to

various persons who were instrumental in the completion of this project.

I offer my humble gratitude to Rev. Dr. JohnAlexander SDB, Rector and

Rev. Dr. D Maria Antony Raj SDB, Principal, Sacred Heart College Tirupattur for
permitting me to have my project work.

I place a record of my deep gratitude to Rev. Dr . K.A. MARIA AROKIA RAJ SDB,
Additional Principal, Sacred Heart College Tirupattur, for sharing his expertise in various
fields.

I am indebted to Mr. A. John Martin, M. C. A, M. Phil., Head, Department of Computer

Applications (UG), Sacred Heart College, for his valuable guidance.

I thank to my project Supervisor, Dr. Merlin Florrence J Assistant professor Department

of Computer Applications (UG) Sacred Heart College Tirupattur for her good
encouragement and valuable guidance.

3
 TABLE OF CONTENT

S.No Content Page No

1 Abstract
Introduction
Project Overview
Existing Work
2 Proposed Work
Problem Statement
Problem Positioning Statement
Summary
System Requirement Specification
Introduction
Software Requirement
3
Hardware Requirement
Feasibility Study
Summary
System Analysis and Design
Introduction
Modules Description
Use Case Diagram
Data Flow Diagram
Architecture Diagram
4 Class Diagram
Sequence Diagram
Component Diagram
Deployment Diagram
E-R Diagram
Table Design
Summary
System Implementation
5
Development Environment

4
 Software Testing
Test Cases
Summary
6 Future Enhancement
7 Conclusion
8 References
Appendices
9 Source Code
User Interface Design

5
Abstract:

Normally the Indian laws with section wise can‟t be understood by all. Even the lawyers and

judges have to struggle to find the judgment for the previous cases which is similar to the

current cases. If they know the judgment details of the cases then easily they can make an

argument on the cases to find the good result within short period.

This system will help to the people to know ongoing process of their cases and

judgment details to the lawyers and judges. Even the details of the case entry will help to the

people to have a brief idea about the process.

The main objectives of this system is used to view the Indian Judicial cases like civil,

criminal, cyber crime cases etc. regarding this the students, professionals, and General public

can rectify their doubts regarding the cases what they needed .So this application is provide

information as in the form of sample cases like finished case or ongoing sample cases .By use

of this they can be benefited.

This system considers the various users and developed. Depends on the user type the

functionality will be differed. For the professionals and the students this system is used for

the reference purpose. For the general users it is used to give some idea about the judicial

cases and also they can view their personal case details instead meeting their advocate each

time to know their case status. This system will be user friendly.

6
 1. INTRODUCTION
1.1 Project Overview
Purpose:

Maintaining various case details in court. This system has two aspects. One is, it can be used
in magistrate court and the other one is this system can also be used for the advocate for his
own reference and his trainee students and clients.

Scope:

The main objectives of this system is used to view the Indian Judicial cases like civil, criminal, cyber

crime cases etc. regarding this the students, professionals, and General public can rectify their doubts

regarding the cases what they needed .So this application is provide information as in the form of

sample cases like finished case or ongoing sample cases .By use of this they can be benefited.

1.2 Existing Work

 This system is not a convenient way for interaction.

 The interaction may be done through this system by only in the form of oral.

 This process will not be a time consuming one

1.3 Proposed Work

The proposed system is designed to provide a solution for the drawbacks of present system. It

aims to:

 This system is very convenient one for interacting the queries regarding Indian law

cases.

 By use of this process the online transaction have been done.

 This process will provide quicker results regarding the queries.

 The needed documents can be downloaded by the user at any time.

7
1.4 Problem Statement

Existing system is containing all the details in

The problem of the form of hard copy which is not very easy to
search
Affects User

User has to visit the court every time for the

The impact of which
reference

Having the details in the system which could

A successful solution would be
be accessed via web

1.5 Problem Positioning Statement

Name Represent Roles

User Students, professionals and User satisfied with their
general users needs.
Admin To secure and manage the Making sure about the
information with confidential information and case details

1.6 Summary

The chapter describes the problem statement, existing work and proposed work.

8
 2. SYSTEM REQUIREMENT SPECIFICATION
2.1 Introduction
Systems Study is the analysis of sets of interacting entities, including computer systems
analysis. This field is closely related to requirements analysis. The development of a
computer-based information system includes a systems analysis phase which produces or
enhances the data model which itself is a precursor to creating or enhancing a database. There
are a number of different approaches to system analysis. When a computer-based information
system is developed, systems analysis (according to the Waterfall model) would constitute
the following steps:

 The development of a feasibility study, involving determining whether a project is

economically, socially, technologically and organizationally feasible.
 Conducting fact-finding measures, designed to ascertain the requirements of the system's
end-users. These typically span interviews, questionnaires, or visual observations of work
on the existing system.
 Gauging how the end-users would operate the system (in terms of general experience in
using computer hardware or software), what the system would be used for and so on

Another view outlines a phased approach to the process. This approach breaks systems
analysis into 5 phases:

 Scope Definition
 Problem analysis
 Requirements analysis
 Logical design
 Decision analysis
Use cases are a widely used systems analysis modeling tool for identifying and expressing the
functional requirements of a system. Each use case is a business scenario or event for which
the system must provide a defined response. Use cases evolved out of object-oriented
analysis; however, their use as a modeling tool has become common in many other
methodologies for system analysis and design.

9
2.2. Software Requirements

The configuration of the software used in the design of the system is listed below.

Project Name : Judicial Biographical System

Application : Web Application
Issues : To maintain server and updates on information
Scope : To update daily record and maintain the records

Working Environment : JSP, SQL Server

Operating System : Windows 7, 8,9,10.

Editor : Netbeans IDE

Language : JSP

RDBMS : SQL Server

2.3 Hardware Requirements

i. System : Intel Core I3 Processor

ii. CPU : Intel I3
iii. Clock Speed : 2.4 MHz
iv. Main Memory (RAM) : 8GB DDR 4
v. Secondary Memory : 1 TB SSD
vi. Monitor : 18.5” Samsung LED Widescreen
Monitor

vii. Printer : Canon LBP 2900 Laser Printer

(80 Column Printer)

viii. Operating System : MS-Windows 11

ix. Environment : Windows 7,8,9,10,11
x. Mouse : Logitech PS/2

2.4. Feasibility Study

An important outcome of the preliminary investigation is the confirmation that the

10
system requested is feasible. The Youth for Social Responsibility is application used for
website. The existing system of website process is very slow and to maintain the documents
manually in note books.
This is offline application and single user application

Scope
An important outcome of the preliminary investigation is the affirmation that system
requested is feasible. The three types of feasibility studies which helped me to identity the
solutions are stated below:

 Technical Feasibility
 Economical Feasibility
 Operational Feasibility
Technical Feasibility
In order to identity whether it is technical feasible, technology platform, supporting software
and tools ad work area have to be given the first priority. Further, this system requires the
duration of three months to complete.
The objectives of new tool are to maximum scalability and security of the business
application.
And the feasibility study resulted in „yes‟ for the following question:

 Does the necessary technology exist to do what is suggested?

 Does the proposed equipment have the technical capacity to hold the data
 required to use the new tool?
 Can the system be upgraded if developed?

The result „yes‟ to the above questions and the proposed system requires the duration of six
months to complete.

Economic Feasibility
The website owners must buy the software and hardware which are required; no initial cost
regarding that is incurred.

11
Operational Feasibility
The system is developed using the front-end that is used that case coding, as it is more a web
application rather than giving much concentration on network and their implementations.
Backend requires having capability to store Data.
Thus economically and technically the new system tool is feasible. The operational feasibility
is to take into consideration of the user‟s acceptance of the system. Any new system,
especially a monitoring system, can result in users going against it since they may feel that it
intruders into their privacy. However, properly specifying the merits of system can help
overcome the initial rejection.

Summary
This chapter concludes with the summary and objectives of the project. The next chapter
describes the requirements analysis of the project.

12
 3. SYSTEM ANALYSIS AND DESIGN
3.1 Introduction
This chapter describes the modules that are implemented in the software with UML diagrams

and use case designs.

3.2 Modules Description

It is the web-based technology, which is used to set the biography of the judicial
process management system.

Modules:

This Judicial Biography contains seven modules they are;

 Case Detail Entry

 Details of the Lawyer And Judges

 Maintaining Witness of the Cases

 Day-to-day Update of case Hearing

 Making ongoing cases as finished case

 Uploading the details of case and judgment

 Reports Generation

1) Searching by case No

2) Searching by giving case type

3) Searching by keyword

4) Searching by judge

5) Searching by lawyer

6) Searching by date

Module Specification:

Case Detail Entry:

Purpose:

13
 This module is used to register the case details or add new case details.

Overview:

This module is used to enter the whole details regarding the case. It is
accessed by the admin.

Responsible:

The admin

Entry Criteria:

Admin alone has the right to enter the case detail

Input:

Case type, Plaintiff, no of witness, place, time, date, culprit, address, phone
no, lawyer name, and case hearing details

Steps involved:

1. Admin opens details page to fill the details

2. The details of the case has entered carefully

3. The data are stored in the database

Exit Criteria:

Admin should save the data carefully without mistakes

Output:

This is used to track the details of the cases history very easier.

Details of the Lawyer And Judges:

Purpose:
This module is used to know the details of lawyer, who is handling the
case and also see the judgment details of the cases and who all the judges for
the case are.

Responsible:

The lawyer

Input:

LID, uname, fullname, address, Phno, email

14
 Entry criteria:

Lawyer can register his details for the reference.

Exit criteria:

Details will be confidential.

Output:

This could be useful to the user those who are searching the lawyer

Maintaining Witness of the Cases:

Purpose:
This module is used to view details of the witness
Responsible:

The admin

Input:

WID, Case no, case status, witness no, witness name, Intro, confession, date

Entry Criteria:

Details of the witness of the particular case are entered.

Exit criteria:

The details are stored in the database.

Output:

Records are saved successfully.

Day-To-day Updating of case Hearing:

Purpose:
Regarding the cases the day-to-day Updating will be done.

Responsible:

The Admin

Input:

HID, case no, date hearing, activities, judge notification, next hearing

Entry criteria:

15
 Here the admin will update the ongoing cases hearing details and also
already finished cases hearing details.

Exit criteria:

Updates are stored carefully

Output:

Information are updates carefully as per needed.

Making ongoing cases as finished case:

Purpose:
In this module the process of changing the ongoing cases into finished cases
and vice versa.

Responsible:

The admin

Input:

Case no, case type, judicial area, district, defendant, plaintiff, file under sec, fir
no, case desc, attorney, plaintiff counsel, defendant counsel, judge, judgment
date, judgment desc, no. of witness, keyword, case Added on

Entry criteria:

The case details for ongoing and finished case are entered clearly

Exit criteria:

The details are saved in the database

Output:

This process is used to convert the case types.

Uploading the details of case and judgment :

Purpose:
Here the admin will upload the case details time by time. So he will track the
cases detail very closely and also judgment details that should be uploaded.

Responsible:

The admin

Input:

16
 Case no, case type, judicial area, district, defendant, plaintiff, file under sec, fir
no, case desc, attorney, plaintiff counsel, defendant counsel, judge, judgment
date, judgment desc, no. of witness

Entry Criteria:

Case is selected by using case no and the required fields are uploaded

Exit criteria:

Records are uploaded and saved successfully.

Output:

Records are added in the database

Reports Generation :

Purpose:
This process is used to search the cases from the case lists

Responsible:

The Admin

Input:

Case no, case type, keyword, judge name, lawyer name

Entry criteria:

Reports can be viewed by searching case by no, type, date, lawyer, judgment

Exit criteria:

They can retrieve the concern case information by giving anyone.

Output:

This is useful way to get the case details.

3.3 Use Case Design:

17
 login

register

enter case details

view case details

admin professional

view lawyer details

update case details

update personal details

view reports

18
 login

register

view case details

general user
student

view lawyer details

update personal details

USE CASE DESCRIPTION

The admin and user to log In order to start
Login
their work.
Various kind of users can register their
registration
details
Enter Case Details Admin enters the case details

View Case Details Admin and users can view the case details

View lawyer and judge details User case view admin and lawyers details

Update details Users can update their details if necessary

Admin maintains the case details and update
Update case details
them daily
Logout Admin and user can logout

19
 3.4 Data Flow Diagram

3.5 Architecture Diagram

20
3.6 Class Diagram

Student
-id : char
CaseDetails
-name : char
-uname : char -caseno : char
-password : char *..* -casetype : char
-email : char -date : Date
-phno : char -hearingdate : char
-univ : char -plaintiff : char
-witness : char
1..* +view()
-plaintiffcounsel : char
+update()
-defendantcounsel : char
+logout()
Admin -judge : char
-ID : char 1..* -judgement : char
-uname : char -status : char
-password : char Professional -nexthearing : char
-secretQuestion : char -judicialarea : char
-LID : char
-secretAnswer : char 1..* -address : char
-name : char
-district : char
+login() -uname : char
+register() -password : char *..* +finishedcase()
+logout() -address : char +ongoingcase()
-phno : char +hearing()
-univ : char +update()
1..* +add()
+view()
+view()
+update()
+logout()
+logout()

GeneralUser
-Id : char
-uname : char *..*
-password : char
+view()
+update()
+logout()

21
3.7 Sequence Diagram
Admin

admin:login judicial
admin : admin

login()

conformation

register()

add()

view()

update()

delete()

logout()

rofessional:

professional : professional: judicial

professional login

login()

conformation

register()

add()

view()

update()

logout()

22
Student:

student:
student :
login
student login()

judicial
conformation

register()

view()

update()

logout()

General User:

general user :
general user
general judicial
user : login

login()

conformation

register()

add()

view()

update()

logout()

23
3.8 Component Diagram

User

Home Page

Case Details

Registration Login Lawyer Details

Search Case Entry

Update Own Details

Admin Home Page

Maintain Case Details

Login

Controls All Details

Report

24
3.9 Deployment Diagram

<<Device>>: Application Server

Case detail entry

Details of Lawer and Judge

<<Device>>
Maintaing witness's details <<Database
: Browser
>> : MS
SQL
Making ongoing case as finished case

Uploading judgment of case

Report generation

25
 3.10 E-R Diagram

3.9
Password College
Password Address Degree
User
Name
name

Admin Maintains Student Address

Name
Address

Ma Phno
Email in t
a in s
Case Case s
Case no fer Email
Phone Type Status Re
no

Hearing

Judicial
area
Date Cases

Defendant
Maintains

Refers
Judgement

Judge Lawyer
Plaintiff
name name
ew

Re
Vi

fe
rs

Name Name

Uname Password
General user Refers Professional

Password
Phno
Gender
Address
Phno Email
Email
DOB
Address
Position

3.11 Table Design:

Database design is necessary to group the given data and to give them a logical
structure. The overall objective in the development of a database is to treat data as an
organizational resource and as an integrated whole.

A database is a repository of information. It 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 users. In this
project, we are mainly concerned with relational databases. Relational database stores data in

26
tables, which in turn are composed of rows, also known as records, and columns also known
as fields. The System has six tables that can be described as follows.

All these tables are in the normalized form, so that there may not arise any problem of
consistency and integrity.

Login:

NAME DATA TYPE SIZE CONSTRAINTS

50
FirstName Text Primary Key
50
LastName Text _
25
Password Text _
255 _
Address Text
50 _
State Text
50 _
City Text
_ _
Pincode Long

Student Details

NAME DATATYPE SIZE CONSTRAINTS

RegNo Text 10 Primary Key

Name Text 30 Not Null

Course Text 3 Foreign Key

Date of Birth Date _ _

Address Text 255 _

Date of Joining Date _ _

27
 Application No Text 5 _

Email Id Text 50 _

Telephone Number Text 25 _

Roll No Text 10 _

Academic Year Integer _ _

Community Text 3 Foreign Key

Occupation Text 3 Foreign Key

Meeting Schedule:

NAME DATATYPE SIZE CONSTRAINTS

8
Date Date _
25 _
Time Text
30 _
Place Text
30 _
Contact Person Text
15 _
Contact Person Text

Phone Number
30 _
Prepared By Text

Attendance :

NAME DATATYPE SIZE CONSTRAINTS

28
 20
Regno Text _
50 _
Name Text
10 _
Course Text
2 _
Dept Integer
8 _
DOA Date with Time
10 _
Status Text
Plan Saplings:

NAME DATATYPE SIZE CONSTRAINTS

8
Date Date _
25 _
Time Text
30 _
Place Text
30 _
Responsible Person Text
30 _
Sapling Name Text
20 _
Types Text
_ _
Total Saplings Long
Sponsor Details

NAME DATATYPE SIZE CONSTRAINTS

Events Name Text 50 Primary Key

Sponsors Name Text 30 Not Null

Email Text 25 _

Phone Number Text 15 _

Address Text 255 _

29
 Sponsored Amount Long _ _

Collected By Text 30 _

FeedBack:

NAME DATATYPE SIZE CONSTRAINTS

50
Name Text _
255 _
Address Text
50 _
E-Mail Id Text
255 _
Feedback Text

3.12 Summary

30
 4. SYSTEM IMPLEMENTATION
4.1 Development Environment
4.1.1. Development Environment:

The development environment is essential for the development of any software tool.
Suitable selection of hardware and software not only reduces development time but also
ensures product success.

The hardware and software used for Judicial Biographical System development are discussed
in length below.

Hardware and Software Requirement:

The hardware used in the development of the tool:

 Front End - J2EE

 Back End - Microsoft SQL Server 7.0
 Programming Interface - JSP
 Programming Tool - Netbeans 7.1.1
 Visio - UML modeling
 Rational Rose - To draw Sequence and Collaboration diagram,

4.1.2. Implementation:

Implementation of Judicial Biographic System was done using the JSP language.
Each and every module can be run independently and also in a sequence starting from the
first module until the last. Once installed, applications are often used for many years without
any problems. However, both the company and the users will change, and the environment
will be different over months and years. Modifications and changes will be made to software
files or procedures to meet emerging user requirements.

This Integrated Software System was designed and developed based on the Iteration
Model. This model particularly expresses the interaction between subsequent phases. Testing
software is not an activity, which strictly follows the implementation phase. In each phase of
the software development process, the results obtained against that which is required was
compared. In all phases quality has to be assessed and controlled.

31
 Requirements Analysis

Verification and Validation

Design

Verification and Validation

Implementation

Verification and Validation

Testing

Verification and Validation

Maintenance

Verification and Validation

4.2 Software Testing

Software testing is a critical element of software quality assurance and represents
the ultimate review of specification, design and code generation. Testing is a process of
executing a program with the intent of finding error. A good test case is one that has a high
probability of finding as an-yet-undiscovered error. A successful test is one that uncovers an
as-yet-discovered error. A strategy for software testing may also be viewed in the context of
spiral. Unit testing begins at the vortex of the spiral and concentrates on each unit of the
software as implemented in source code. Testing progresses by moving outward along the
spiral to integration testing, where the focus is on design and the construction of the software
architecture. It also encounters validation testing. Finally, we arrive at system testing, where
the software and other system elements are tested as a whole.

System Testing

. System testing is a critical element of software quality assurance and represents the ultimate
review of specification, design, and coding

32
Testing Objectives
1. Testing is a process of executing a program with the intent of finding an error.
2. A good test case is one that has a high probability of finding an as-yet un discovered
error.
3. A successful test is one that uncovers an as-yet-undiscovered error.
4. The objective is to design tests that systematically uncover different classes of errors
and do so with a minimum amount of time and effort. If testing is conducted
successfully, it will uncover errors in the software. As a secondary benefit, testing
demonstrates that software functions appear to be working according to specification
and that performance requirements appear to have been met. In addition, data
collected as testing is conducted provides a good indication of software reliability and
some indication of software quality as a whole.

Testing Principles
The following are the set of testing principles

 All testing should be traceable to customer requirements.

 Tests should be planned long before testing begins.
 Testing should begin “in the small” and progress toward testing “in the large”.
 Exhaustive testing is not possible.
 To be most effective, testing should be conducted by an independent third party.

Unit Testing

Unit testing focuses verification effort on the smallest unit of software design-the module.
Using the procedural design description as a guide, important control paths are tested to
uncover errors within the boundary of the module. The relative complexity of tests and
uncovered errors is limited by the constrained scope established for unit testing. The unit test
is normally white-box oriented, and the step can be conducted in parallel for multiple
modules.

Integrated Testing

33
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
tested 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 a “big bang” approach. All modules are combined in advance. The entire
program is tested as a whole. A set of errors 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 the big bang approach. The program is constructed
and tested in small segments, where errors are easier to isolate and correct; interfaces are
more likely to be tested completely; and a systematic test approach may be applied.

Testing and Implementation in this Project

The testing has been made for the various modules involved in this system. The validations
also have been tested.

Initially, the login screen was tested. If both the user-id and the password values are entered
properly, the values will be checked with the database and it will go to the produce available
screen. If the values are not given either for the user id or for the password , or for the both, it
will show the error. If the user-id or password is invalid, the screen will be refreshed and
again it will ask for the both. The other operations sign up for the new user and the forget
password also tested. The sign me up form will be shown to the new user if that person clicks
the particular string from the index page. Then the new user has to fill the details in that form.
In this some of the fields are mentioned with the „*‟ symbol. That all fields should be filled.
Otherwise the submission of user details will not be accepted.

In the sign me up form, after every detail has been filled up properly, the user has to submit
his details. Then the details are checked with the database .If the user-id with that same name
already exists, then the system will ask for a new user-id. If the problem doesn‟t arise, it will
accept the new user details and store in the database. Then the user will be given the user-id
with that password.

34
The forget password also made to test. If the user failed to remember the password, then this
option will help the user to retrieve back the password. The user has to click the forget
password string from the index page. Then the user will be given some clues to retrieve the
password. That is, the user will be given an option to type the date of birth. If it is the user‟s
password, then the password will be checked with the database and it will return the true
message to the user. Otherwise the user has to go for some other attempts.

All the above-mentioned factors from the index page were tested with the validations. The
factors produced the best result when it was separate. The same result was given when they
were tested along with the whole process.

When the modules tested individually, they produced a good result. The result was better
when the whole process was tested. The whole process didn‟t make any problem when it was
tested. The level by level links, the validations for every module, and the whole process came
with a best result. Thus the whole process was tested.

4.3. Test Case Design

Purpose

The purpose of this document is to provide the test case specification for the use
cases.

Scope

This application applies to the Youth Social Responsibility System.

Overview

This software contains the test case specification for the various use cases. It's
identified in the software requirement specification (SRS).

Test Case (Table format ) : Login

Test Input Description Expected Result Pass/Fail

case
ID.

35
TC 01 Empty username, Empty username, Fields should not Pass
password, password, confirm be empty
password, address
confirm password,
and contact number
address and contact
given by user
number.

TC 02 Invalid username and An Invalid username username field Pass

valid id, password, given by user should be in
confirm password, specified
address and contact format
number

TC 03 Invalid username, An invalid username, Username, Pass

password, confirm password given by password field
password, valid user should be in
address and contact specified
format.

TC 04 Different password and Different password Password Pass

confirm password and confirm mismatch
provided. password provided
by user.

TC 05 Invalid address and An invalid address Address field Pass

valid first name, last provided by user. should be in
name, id, password, specified
confirm password and format.
contact number.

36
TC 06 Invalid contact number An invalid Contact number Pass
and valid first name, last contact number field should be
name, id, password, provided by in specified
confirm password and user. format.
address.

TC 07 Valid first name, last Valid first name, Registration Pass

name, id, password, last name, id, completed
confirm password, password, confirm success fully
address and contact password, address
number. and contact
number given by
user.

New Entry of YSR

Test Input Description Expected result Pass/Fail

case
ID

TC 01 Empty Reg no, Empty regno Fields should not be Pass

Name ,name and mail id empty
given by user

TC 02 Invalid regno and An Invalid regno regno field should Pass

valid name, and given by user be in specified
Description format

TC 03 Invalid regno, An invalid regno, regno, name Pass

name, valid name given by user field should be

37
 Description. in specified
format.

TC 04 Invalid An invalid Description field Pass

Description. and Description should be in
valid Regno, name provided by user. specified format.

TC 05 Valid Description. Valid Successfully Pass

regno, name Description. Navigate to next
Regno , name page.
provided by
user.

Summary

This System implementation, listed in detail on the hardware, software requirement and
during development. Other than that, it more importantly touched on the implementation of
Judicial Biographic System.

38
 5. Future Enhancement
 We can make the application specific to the user with valid id to communicate with
the application.
 A post back comment session can also be added to view and service the user problems
to make our application more users friendly.

39
 6. Conclusion:
 This project has been successfully developed according to the user requirement.
 The system produces accurate result and it also reduces a lot of overheads, which the
manual system faced.
 The system was thoroughly tested according to the testing methodology.
 This will save time in viewing the data when large numbers of users are connected to
the system.
7. It‟s an efficient, accurate, and distributed metadata-oriented scheme is required to
leverage the overall performance in large distributed storage systems.

40
References

 Ali Bahrami, “Object Oriented System Development”, McGraw Hill International

Edition, 1999.
 Craig Larman, Applying UML and Patterns, 2nd Edition, Pearson, 2002.
 Grady Booch, James Rumbaugh, Ivar Jacobson, “The Unified Modeling Language
User Guide”, Addison Wesley Long man, 1999.
 Bernd Bruegge, Allen H. Dutoit, Object Oriented Software Engineering using UML,
Patterns and Java, Pearson 2004
 http://www.tracemodeler.com/articles/a_quick_introduction_to_uml_sequence_diagra
ms/
 http://www.ibm.com/developerworks/rational/library/3101.html
 http://www.ibm.com/developerworks/rational/library/content/RationalEdge/sep04/bell
 http://www.objectmentor.com/resources/articles/umlClassDiagrams.pdf
 http://www.tutorialspoint.com/uml/uml_interaction_diagram.htm
 http://www.tutorialspoint.com/uml/uml_statechart_diagram.htm
 http://msdn.microsoft.com/en-us/library/ms188251.aspx
 http://en.wikipedia.org/wiki/Verification_and_validation_(software)
 http://softwaretestingfundamentals.com/verification-vs-validation/
 http://www.softwaretestingstuff.com/2008/04/what-is-security-testing.html
 http://teradata.uark.edu/research/wang/security.html --
 http://www.cigital.com/papers/download/bsi4-testing.pdf
 http://secappdev.org/handouts/2009/software%20security%20testing%20in%20the%2
0real%20world.pdf
 http://msdn.microsoft.com/en-in/library/ms181922(v=vs.80).aspx
 http://www.google.co.in/url?sa=t&rct=j&q=project%20implementation%20report%2
0template&source=web&cd=1&cad=rja&ved=0CC8QFjAA&url=https%3A%2F%2Fptop.only.wip.la%3A443%2Fhttp%2Fv
-c-s.org%2Fsites%2Fv-c-
s.org%2Ffiles%2FVCS%2520CCB%2520Monitoring%2520%2526%2520Implement
ation%2520Report%2520Template%2C%2520v3.0.doc&ei=cb9uUcu4Mcf3rQfz6oD
4CA&usg=AFQjCNHW8AT3hRP4B6ZJGUE3bilCahq4yA&bvm=bv.45368065,d.b
mk

41
  http://www.google.co.in/url?sa=t&rct=j&q=project%20deployment%20report%20&s
ource=web&cd=3&cad=rja&ved=0CDoQFjAC&url=https%3A%2F%2Fptop.only.wip.la%3A443%2Fhttp%2Fportal.hud.go
v%2Fhudportal%2Fdocuments%2Fhuddoc%3Fid%3Dpostdep-
temp2.docx&ei=e8BuUcrqCIyIrAezrIGYAg&usg=AFQjCNG0GycwwHWZy6Rvagc
jFVuHhQtaZA&bvm=bv.45368065,d.bmk
 http://www.lawadiv.com/index.php?show=e-munshi
 http://www.advocatekhoj.com/index.php
 http://research.cs.queensu.ca/~shepard/testing.dir/under.construction/tool_list.html
 https://sw.thecsiac.com/databases/url/key/2399/8547
 http://jakarta.apache.org/cactus/getting_started.html
http://www.tutorialspoint.com/more.htm

42
 APPENDIX

A. UI Design:

43
44
45
B. SOURCE CODE:
html>

<head>

<title><jsp:include page="include/Title.txt" flush="true" /></title>

<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">

<style type="text/css">

<!--

body

background-image: url("img1.jpg");

background-repeat: no-repeat;

</style>

<script language="JavaScript">

46
 function Validate(){

var docF=document.f1;

if(docF.UName.value==""){

alert("Plz Enter Your User Name.");

docF.UName.focus();

return false;

if(docF.Pass.value==""){

alert("Plz Enter Your Password.");

docF.Pass.focus();

return false;

return true;

</script>

</head>

<body link="#0000FF" vlink="#0000FF" alink="#00CC00" >

<form name="f1" action="General/ValidateLogin.jsp" onSubmit="return

Validate();" method="post">

<table height="25%" border = "0" background="img1.jpg" >

<tr> </tr>

</table>

<p>&nbsp;</p>

<table width="1012" height="448" border="0" bordercolor="#CCCCCC">

<tr><th width="1006" rowspan="6" valign="top" scope="row"><table

width="1001" height="338" border="0" bordercolor="#FFFFFF">

<tr>

47
 <th width="645" rowspan="6" align="left" valign="top"
scope="row"><p><img src="images/img2.jpg" width="306" height="276"></p>
</th>

<th height="21" colspan="2" bordercolor="#000000"

bgcolor="#996600" scope="row"><div align="center"><font color="#FFFFFF">Login
Form</font></div></th>

</tr><tr>

<th width="128" height="24" bordercolor="#000000"

bgcolor="#FFFFCC" scope="row"><div align="right"><font
color="#000000">Username :</font></div></th>

<td width="214" bordercolor="#000000" bgcolor="#FFFFCC""><div

align="right"><font color="#0000FF">

<input name="UName" type="text" size="35"

maxlength="30" class="txt" align=right >

</font></div></td>

</tr><tr>

<th height="24" bordercolor="#000000" bgcolor="#FFFFCC"

scope="row"><div align="right"><font color="#000000">Password :</font></div></th>

<td bordercolor="#000000" bgcolor="#FFFFCC"><div

align="right"><font color="#0000FF">

<input name="Pass" type="password" size="35"

maxlength="30" class="txt" align=right>

</font></div></td>

</tr> <tr>

<th height="26" bordercolor="#000000" bgcolor="#FFFFCC""

scope="row"><div align="right"><font color="#0000FF">

<input type="submit" action="General//ValidateLogin.jsp"

value=" Ok " class="but" >

</font></div></th>

<th height="26" bordercolor="#000000" bgcolor="#FFFFCC""

scope="row"><div align="left"><font color="#0000FF">

<input type="reset" value="Cancel" class="but">

48
 </font></div></th>

</tr>

<tr>

<th height="26" bordercolor="#000000" bgcolor="#FFFFCC"

scope="row"><div align="right"><font color="#0000FF"><a
href="General/ForgetPass.jsp">Forgot Password?</a></font></div>

<div align="right"></div></th>

<th height="26" bordercolor="#000000" bgcolor="#FFFFCC"

scope="row"><div align="left"><font color="#0000FF"><a
href="General/UserReg.jsp"><strong>New User
Registration</strong></a></font></div></th>

</tr>

<tr>

<th height="157" valign="top" bordercolor="#000000"

bgcolor="#FFFFFF"" scope="row"><div align="right"><font color="#0000FF"><a
href="General/ForgetPass.jsp"></a></font></div>

<div align="left"></div></th>

<th valign="top" bordercolor="#000000" bgcolor="#FFFFFF"

scope="row"><div align="left"><font color="#0000FF"><a
href="General/UserReg.jsp"></a></font></div></th>

</tr>

<tr align="left" valign="top">

<th height="21" colspan="3" scope="row">&nbsp;</th>

</tr>

<tr align="left" valign="top">

<th height="21" colspan="3" background="images/img3.jpg"

scope="row">&nbsp;</th>

</tr>

</table>

<p>&nbsp;</p>

</th>

49
 </tr>

</table>

</form>

</body>

</html>

50
 C. User Manual:

Description:

This is login form from which is used to allow the authorized user to access the
system.

Description:

This form is used to change password in the case of password is forgotten.

51
Description:

This form is used to register the details if the member is new to access the system.

Description:

This form is used to view the ongoing case details.

52
Description:

This form is used to edit the existing case details as per need.

Description:

This form is used to view the finished case details.

53
Description:

This form is used to edit the ongoing case details.

Description:

This form is used to view the ongoing case details

54
Description:

This form is used to search the case details by giving its number.

Description:

This form is used to view the personal profile.

55
Description:

This form is used to edit the personal details of the user.

56