INDIAN LEGAL ADVISE AND

GUIDELINES SYSTEM

Under the Guidance: presented By:

M . Sridhar MCA ,PHD G. Srinivas Reddy
Associate. Professor Y18CA014
RVR&JC College of Engineerring
Guntur
 CONTENTS
 Abstract
 Existing system
 Disadvantages
 Proposed system
 Advantages
 System Requirement Specification
 Sequence diagrams
 Entity relationship model
 Class Diagrams
 Use case Diagrams
ABSTRACT:

The Development of Indian Legal Advise and guidelines System is a web

application which systematizes functions of large law firms, which have large
number of clients. The proposed Development Application for Indian Legal Advise
and guidelines will enable the operations of the law firms to be conducted more
effectively. The need will be felt more in the coming days when the profession of act
will be opened up for foreign competition .Proposed system provides information
on the multiple facts of laws such as the Constitution of India, which is a basic
legislature dealing with fundamental rights, duties of the citizens of India, laws
relating to the establishment of family courts and the rules of procedure of the
courts, case, sections , and cause lists etc..,
EXISTING SYSTEM:
It does not provide complete information about law,
courts and sections related to constitutions of India.
Ineffectiveness of generating case history details.
This system is not providing secure registration and
profile management of all the users properly.
Disadvantages
Existing system does not provide case hearing alerts.
Information is not provided to general users.
PROPOSED SYSTEM:

The development of this new system contains the

following activities, which try to automate the entire
process keeping in the view of database integration
approach.
It provides complete information about law, courts
and sections related to constitutions of India.
Providing previous case hearing details.
Manages case evidence type and witness details.
Providing proper managing of client profile details
Advantages
Authentication is provided to only registered users.
The user’s information can be stored in centralized
database which can be maintained by the system.
Searching facility provided.
User friendliness is provided in the application with
various controls provided by system rich user
interface.
NUMBER OF MODULES:

User Registration.
Law, Court and Section Management.
Case Management.
Security.
Reports.
Charges
Modules Description
 Users Registration
 This module authenticates different types of users.
 Administrator
 General User
 Client
 Lawyer
Law , Court And Section Management

 Administrator performs following operations.

 Adding Law types
 Adding and Updating Court Details.
 Adding and Updating Sections.
Case Management
 This module manages the following details.
 Case evidence details.
 Case witness details.
 Case hearing details.
 Case member details.
. Security
 This System provides security with different kind of accessing levels.
Reports

 User Profiles.
 Law, Court and Sections Reports
 Case hearing report.
SOFTWARE REQUIREMENTS:
 Operating System : Windows XP/2003 or Linux (Any OS)
 User Interface : HTML, CSS
 Client-side Scripting : JavaScript
 Programming Language : Java
 Web Applications : JDBC, Servlets, JSP
 IDE/Workbench : My Eclipse 8.6
 Database : Oracle 10g XE
 Server Deployment : Tomcat 5.x
HARDWARE REQUIREMENTS:

 Processor : Core 2 Duo

 Hard Disk : 160GB
 RAM : 1GB or more
 Non Functional Requirements

The major non-functional Requirements of the system are as follows

Usability
The system is designed with completely automated process hence there is no or less
user
Intervention.

Reliability
The system is more reliable because of the qualities that are inherited from the chosen
platform java. The code built by using java is more reliable.
Performance
This system is developing in the high level languages and using the advanced
front-end and back-end technologies it will give response to the end user on
client system with in very less time.

Supportability
The system is designed to be the cross platform supportable. The system is supported
on a wide range of hardware and any software platform, which is having JVM, built
into the system.

Implementation
The system is implemented in web environment using struts framework. The apache
tomcat is used as the web server and windows xp professional is used as the platform
SDLC METHODOLOGIES
 This document play a vital role in the development of life cycle (SDLC) as it describes the
complete requirement of the system. It means for use by developers and will be the basic during
testing phase. Any changes made to the requirements in the future will have to go through formal
change approval process.
SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of
Software Development and Enhancement. This model was not the first model to discuss iterative
development, but it was the first model to explain why the iteration models.
The steps for Spiral Model can be generalized as follows:
The new system requirements are defined in as much details as possible. This usually involves
interviewing a number of users representing all the external or internal users and other aspects of
the existing system.
A preliminary design is created for the new system.
A first prototype of the new system is constructed from the preliminary design. This is usually a
scaled-down system, and represents an approximation of the characteristics of the final product.
A second prototype is evolved by a fourfold procedure:
1. Evaluating the first prototype in terms of its strengths, weakness, and risks.
2. Defining the requirements of the second prototype.
3. Planning an designing the second prototype.
4. Constructing and testing the second prototype.
Risk factors might involved development cost overruns, operating-cost miscalculation, or any
other factor that could, in the customer’s judgment, result in a less-than-satisfactory final product.
The existing prototype is evaluated in the same manner as was the previous prototype, and if
necessary, another prototype is developed from it according to the fourfold procedure outlined
above.
The preceding steps are iterated until the customer is satisfied that the refined prototype represents
the final product desired.
The final system is constructed, based on the refined prototype.
The final system is thoroughly evaluated and tested. Routine maintenance is carried on a
continuing basis to prevent large scale failures and to minimize down time.
THE FOLLOWING DIAGRAM SHOWS HOW A SPIRAL MODEL ACTS LIKE:
ADVANTAGES OF SPIRAL MODEL:

Estimates (i.e. budget, schedule etc .) become more relistic as work progresses,
because important issues discoved earlier.It is more able to cope with the
changes that are software development generally entails. Software engineers can
get their hands in and start woring on the core of a project earlier.
E-R DIAGRAM
 INDIAN LEGAL
REGISTRATION
ADVISE AND
GUIDELINES LAW TYPE
SYSTEM
USE
RNA
LO COURT
ME
Admin GIN
HOME
DETAILS

PASSWO
RD SECTIONS

LAWERDETAILS

ID L
O CLIENT DETAILS
LAWER GI
PASSWO N
RD LAW TYPE

HOME COURT DETAILS

SECTIONS

LAWERDETAILS

ID
LAW TYPE
LO
CLIENT GIN
PASSW
ORD COURT
HOME DETAILS

SECTIONS

MONEYPA LAWERDETAI
Y LS
UML DIAGRAMS
The Unified Modeling Language allows the software engineer to express an analysis model using
the modeling notation that is governed by a set of syntactic semantic and pragmatic rules.
A UML system is represented using five different views that describe the system from distinctly
different perspective. Each view is defined by a set of diagram, which is as follows.
1. User Model View.
2. Structural Model View.
3. Behavioral Model View.
4. Implement Model View.
5. Environmental Model View.
UML is specifically constructed through two different domains they are:
UML Analysis modeling, this focuses on the user model and structural model views of the system.
UML design modeling, which focuses on the behavioral modeling, implementation modeling and
environmental model views.
CLASS DIAGRAM
USE CASE DIAGRAMS
System use case diagram:

System

ADMIN

Date-user
ONLINE LEGAL INFORMATION SYSTEM

LAWYER

CLIENT

GENERAL USER
Admin Use Case Diagram

Add..

Law types
Edit

delete

Add..
Court details
Edit

Admin Delete

Sections.

Add..
Data user

Edit

Delete

Add..
Lawyer Details

Edit

Delete
Lawyer Use Case Diagram Diagram:

view
Law types..

view.
Court Details

add.. Data user

Lawyer.
case hearing details
View

Sections.. View.

Lawyer Details.. View.

Client Use Case Diagram

Add,
Case Registration

VIEW,

Law Types

VIEW,
Case hearing details

Data user
Court Details..
VIEW,

CLIENT.
Lawyer Details...

sections
VIEW,

Case Status

Guidelines post query

log out
SEQUENCE DIAGRAMS
Admin Sequence Diagram

Admin Authentication Home Law Types Court details Sections Lawyer Details logout

1 : login check()

2 : if success()

3 : if f ails()
4 : add law ty pes()

5 : Edit lawty pes()

6 : Delete lawty pes()

7 : Add court details()

8 : Edit court details()

9 : Delete court details()

10 : add sections()

11 : Edit sections()

12 : delete sections()

13 : add lawyer details()

14 : Edit lawyer details()

15 : delete lawy er details()

16 : log out()
Lawer sequence diagram
lawyer Authentication Home Law Types Court details Sections Case hearing details Lawyer Details logout

1 : login check()

2 : if success()

3 : if fails()

4 : view law types()

5 : view court details()

6 : View sections()

7 : add case hearing details()

8 : v iew casehearing details()

9 : View lawyer details()

10 : log out()
Client Sequence Diagram:

Client Authentication Home Case Registration Law Types Court details Sections Case hearing details Lawyer Details Case Status Guidelines logout

1 : login check()

2 : if success()

3 : if fails() 4 : add case()

5 : view case details()

6 : view law types()

7 : view court details()

8 : View sections()

9 : view casehearing details()

10 : View lawyer details()

11 : view case status()

12 : post query()

13 : log out()
COLLABORATION DIAGRAM
Admin Collaboration Diagram

Sections
Court details

Lawyer Details

7 : Add court details()

10 : add sections()

13 : add lawyer details()

8 : Edit court details()
11 : Edit sections()

9 : Delete court details() 14 : Edit lawyer details()

12 : delete sections()

15 : delete lawyer details()

Authentication 2 : if success()
Home 16 : log out()

logout

4 : add law types()

1 : login check()

5 : Edit lawtypes()
3 : if fails()

6 : Delete lawtypes()

Admin
Law Types
Lawer Collaboration Diagram:

Court details Sections Case hearing details

Lawyer Details

Law Types 6 : View sections()

9 : View lawyer details()

5 : view court details() 7 : add case hearing details()

8 : view casehearing details()

4 : view law types()

lawyer 10 : log out() logout

Home

1 : login check()

2 : if success()
3 : if fails()

Authentication
Client User Collaboration Diagram:

Case Status Lawyer Details

Guidelines

logout

12 : post query()
11 : view case status()
13 : log out()
Case hearing details

10 : View lawyer details()

9 : view casehearing details()

Client

Home

1 : login check() 8 : View sections()

Sections

3 : if fails() 2 : if success() 7 : view court details()

4 : add case() 6 : view law types()

5 : view case details()

Court details
Authentication Case Registration Law Types
ACTIVITY DIAGRAMS
 Admin

Authentication

if no

if yes

Lawyer Details
Home Law Types Court Details Sections
Log out

Delete add Edit Delete add Edit Delete add Edit Delete
Add lawtypes Edit lawtypes
Lawer Activity Diagram Lawyer

Authentication

if no

if yes

Home Court Details

Law Types Sections
Lawyer Details Case hearingdetails Log out

view view view view add case hearing details view

Client Activity Diagram client

Authentication

if no

if yes

Home
Case Registration Law Types
Court Details Sections
Lawyer Details Case hearingdetails Log out

add case view view view view view view

 user

register

loginfail

home

admint lawer
client
General user

lagout