Chapter 1

INTRODUCTION

1.1. PROJECT OVERVIEW

As we all know that every person who wants to meet a lawyer they have to go physically to
their office or court to approach them. The purpose of this project is to facilitate the public to
find an expert lawyer in the specific field for which they are facing a specific case.

People has to register on our portal so they can easily explore the different categories of the
lawyers in different fields i.e. Corporate Lawyer, Business Lawyer, Property Lawyer, Murder
Lawyer, Banking Lawyer, Family Courts Lawyers. People can also explore the lawyers on
the basis of courts, i.e. Civil Court, District Court, High Court, Supreme Court.

In this portfolio we will also categorize the lawyers as senior lawyer, junior lawyer or average
lawyers, so the people can find a best lawyer on the basis of their case and their availability of
funds. People can consult with the lawyer, get appointment and discuss their case with the
lawyer through our portal.

Lawyers will be registered on our portal and upload his or her data, experience and major
cases which they successively win. Our admin department will manage their profile and
categorise them in different categories as per their field of expertise and experience.

Every person who is registered on our portal can start a chat with a Lawyer with whom he
wants to discuss his or her case and also can send the case files (PDF Documents).
Whenever their appointment is set as they click on the “fix appointment” they will customize
the time and then reminder will automatically began.

The Lawyer and Client both will receive notification by our application. When the case began
in the Court Lawyer and the Client both will receive the case updates e.g. Suit for
Declaration, Plentive Evidence Date(exibit p1), Defendant Evidance Date( exibit d1), Final
arguments etc.

1.2. PROJECT AIMS

Our aim in this project is to design a platform for Lawyers and Clients who are not familiar
with the law or the system around them. We are focusing on the need of the society. This
application is much helpful for those persons who are facing difficulties in finding good
 Lawyers. And also to help those people who don’t know about the rules and regulation of the
Courts. It also help to understand the policies and pocedures of Courts.

1.3. PROJECT OBJECTIVES

Our application which includes:

 To register and verify Lawyers and Clients.

 To find the best Lawyer for their case.
 To start a chat with corresponding Lawyer.
 To trace the case of Court.
 To check the updates for their case.
 To give feedback to Lawyers.

1.4. SCOPE OF THE PROJECT

There are many people who spend their lot of time in finding the appropriate Lawyers so that
they can easily find the best Lawyer by spending their small chunk of time on our application.
And also they will recieve notifications of their case updates through our application.
It is most beneficial for the Lawyers who need to inform their Clients at every update. Client
will be registered on application as well as Lawyers are, So that the security for both parties
are secure. Further more when a client search for the Lawyers, Clients will have to on their
location so that according to their location Lawyers will be shown out on the application.

1.5. PROBLEM STATEMENT

If someone wants to hire a Lawyer he or she will feel less comfortable by going physically to
the court or to the Lawyer office. Or also if they want any kind of information about the case
they have to go to some expert Lawyer for discussion. Due to busy schedule of Lawyer
sometimes they won’t be able to give proper time to their Clients. They do not even meet
their Clients due to shortage of time. Including the busy schedule of Lawyers they can answer
them at any time in which they will be free. So therefore we are introducing the plateform
over which every person securily Find the Lawyer , Hire the Lawyer, Discuss any Query with
Lawyer and have the daily knowledge about their case.
1.6. PROPOSED SOLUTION

The propose system will reduce the paper work by which every person is being affected also
involves Clients to minimize their time to go outside and find a Lawyer.

With the help of this system people can firstly find the relavent Lawyer. The next step is they
can now start a chat with the corresponding Lawyer also they can send documents which the
Lawyer need initially. After it Lawyer will read all the case and then set a date to meetup with
the Client.

Now the next step is to notify the Client and the Lawyer about the case updates, Suit for
declaration, Plentive and Defendant exibit P1 and D1 etc. Clients Lawyers are now able to
receive all the notifications about their case. Our application is trying to reduce court
complexity.
1.7. LIFE CYCLE FOR THIS PROJECT

We will follow the incremental model due to the following aspects of the projects:

 Generates working software quickly and early during the software life cycle.
 More flexible – less costly to change scope and requirements.
 Easier to test and debug during a smaller iteration.
 Easier to manage risk because risky pieces are identified and handled during its
iteration.
 Each iteration is an easily managed milestone

We have selected to use the incremental model because it is a method of software

development where the model is designed, implemented and tested incrementally (a little
more is added each time) until the product is finished. It involves both development and
maintenance. The product is defined as finished when it satisfies all of its requirements.

Figure Error! No text of specified style in document.-1 Incremental Model

1.8. DEVELOPMENT REQUIREMENTS

1.8.1.Hardware Requirement:

The hardware required to develop the FYP Management Portal are as follow
 Processor 2.0GHz or faster processor

 RAM 1GB or higher Hard Disk 10GB of available hard disk space

 Resolution 1024* 768 or higher

 Internet Device
  Laptop

 Mobile Phone

 Computer

1.8.2. Software/Tools Requirement:

Following are all the possible technologies that will be required during the designing,
developmental and testing phases of the project:

 Operating System: Windows XP or higher

 Testing Device: Android Phone

 My SQL Server 2014

 Rational Rose 2007

 Adobe Photoshop

 Android Studio

 Microsoft Excel

 Microsoft Office Word

 Microsoft PowerPoint

 PDF Reader

 MS Visio

 Draw.io
1.8.3. Proposed Implementation Language(s):

 CSS

 C++

 Java

 JavaScript
 Chapter 2

REQUIREMENT ANALYSIS

2.1. SOFTWARE REQUIREMENTS SPECIFICATION (SRS)

A software requirement specification minimizes the time and effort required by

developers to achieve desired goals and also minimizes the development cost. A good
SRS defines how an application will interact with system hardware, other programs and
human users in a wide variety of real-world situations. Parameters such as operating
speed, response time, availability, portability, maintainability, security and speed of
recovery from adverse events are evaluated.

For developing the application the following are the software requirements:

Operating System: Windows 10

Languages: C#, Java, Xml, Asp.net MVC5, Json

Database: MS SQL Server

Tools:

 Adobe photoshop

 Android Studio

 Power point

 Microsoft Excel

 Rational Rose

 SQL Server

 Wamp Server
2.2. FUNCTIONAL REQUIREMENTS

Functional requirements are those requirements that define the functionality of the
project. In other words functional requirements are basically how the system works for
the users.

System features are described in detail as follows.

2.2.1User Registration

The registration of the user is done by completing a registration form.

1. Add new client information
The lawyer shall be able to add a new client information form

2. Search client information form

The lawyer shall be able to search client information form

3. Edit client information form

The lawyer shall be able to edit the client information form

4. Delete client information form

The lawyer shall be able to delete client information form

5. View client information form

The lawyer shall be able to view the client information form

6. Add a document
The lawyer shall be able to add a document to a specific client

7. Search document
The lawyer shall be able to search for the document that he has uploaded for a specific
client

8. Download a document
The lawyer shall be able to download the document he already uploaded for the specific
client he choose
 9. Delete a document
The lawyer shall be able to delete the documents he uploaded for his client

10. Chat with client

The lawyer shall be able to chat with his client and fix the meeting

2.3. NON-FUNCTIONAL REQUIREMENT

Non-functional requirements are those requirements that don’t define the actual working
of the system. Non-functional requirements are used to judge and evaluate the quality of
the system. Non-functional requirements cover all the remaining requirements which are
not covered by the functional requirements. They specify criteria that judge the operation
of a system, rather than specific behaviors. In the context of our project, it is pertinent to
consider the following non-functional requirements:

2.4. Usability

User friendly interface.

Easy to use GUI (Graphical User Interface) so User does not need to learn a new style of
interaction.
Interface of this system is intuitive so user can easily understand all the features of
application and application also have about us and contact us feature to help customer in
case of any difficulty.
User don’t require additional training to use this application, any normal user can easily
understand the working of this application.

2.5. Reliability

The application is reliable in such a way that any hardware failure, power failure, other
natural disaster can’t harm it, It can easily recover to its most recent valid state. This
application had less chances of error but if any error occurred application will
automatically sort out the problem and restart device by itself.
2.6. Integrity

Changes will only done by the System Admin. User can’t make any kind of changes in
the application not even the worker.

2.7. Performance

The system responds in real time. User hire handyman then system will generate request
in real time to the handymen.
 Chapter 3

DESIGN AND ARCHITECTURE

USE CASES (FULLY DRESSED)

Registration
Use Case Title

Use Case ID UC-Registration-01

Description
The client will register himself online while the admin will approve the registration.

Actor User,Admin

Actor Action Response

6.Server receives the detail

1. Client give name
2. Client give password
3. Client give email
7.server verify that this id does not exist already
8.Server create the user
9.Server gives confirmation of the registration

4.Client give Registration

number

5. Client click on the sign

up button

Pre-Condition Unregistered

Post-Condition Registered

Exception User already exist/Invalid email ID

Alternate Path Remain the same screen open and ask for the valid email
id and user details.

Table Error! No text of specified style in document.-1 Use Case of Registration

 Login
Use Case Title

Use Case ID UC-Login-02

Description
The registered Clients & Lawyers will login through valid user id and password.

Actor Admin,Clients,Lawyers

Actor Action Response

4.Server receives the detail

1.user give password
5.Server authenticates the details
6. If the details are correct user logged in
2. user give email 7. If details are incorrect server responds with message
incorrect id or password
3. User click on sign in
button

Pre-Condition User logged out

Post-Condition Successfully login

Exception Invalid User id or password

Alternate Path Remain the same screen open and display invalid user
id/password. Reenter the user id and password.

Table Error! No text of specified style in document.-2 Use Case of Login

 Search Lawyer
Use Case Title

Use Case ID UC-SearchLwyr-03

Description
Clients will search for the appropritate Lawyers through this usecase module.

Actor Clients

Actor Action Response

3. Server sends the details to the lawyers.

1. Clients go to menu
4. Lawyers will get notifications.

2. Clients Search for the

lawyers

3. Available Lawyers will

shown up.

Pre-Condition Request generated

Post-Condition Lawyers will shown up

Exception No invalid input

Alternate Path Try again after 2 min screen remain unchanged.

Table Error! No text of specified style in document.-3 Use Case of Search a Lawyer
 Lawyers List
Use Case Title

Use Case ID UC-Lawyerslist-04

Description
The Lawyers will be shown up in a list and user can select easily.

Actor Clients,Laywers,admins

Actor Action Response

1. Clients go to the 2.Server displays the Lawyers List.

Lawyers list.

Pre-Condition Lawyers List not viewed

Post-Condition Lawyers List viewed

Exception There is no List uploaded.

Alternate Path Upload list to view it.

Table Error! No text of specified style in document.-4 Use Case of View Lawyers list
 SelectLawyer
Use Case Title

Use Case ID UC- SelectLawyer -05

Description
Clients will select the lawyer.

Actor Client

Actor Action Response

1. User select the lawyers 2. Application check the list of Lawyers.

3. If Lawyers are available then the request will be send to
from the list
the corresponding lawyers.
4. If Lawyer is not available , the message will be shown
select another Lawyer.

Pre-Condition No LAwyer selected.

Post-Condition LAwyer selected.

Exception Lawyer not available.

Alternate Path Screen remain unchanged and message displayed “select

another Lawyer”

Table Error! No text of specified style in document.-5 Use Case of Select Lawyer
 StartCoversation
Use Case Title

Use Case ID UC- StartCoversation -06

Description
The student will submit proposal.

Actor Client

Actor Action Response

1. Student will start 2. The messages will began to store in the database.
3. Client will send the request to the Lawyer.
conversation with the
lawyer.

Pre-Condition Chat not started.

Post-Condition Chat started.

Exception Request not send.

Alternate Path Screen remain unchanged and message displayed

“request not send”

Table Error! No text of specified style in document.-1 Use Case of Start chat
 caseupdates
Use Case Title

Use Case ID UC- caseupdates -07

Description
The Clients can also check their case updates from this usecase.

Actor Client

Actor Action Response

3.Portal generates for the case updates.

1.Client will go to case
4.Portal shows the case updates.
updates module.

2.And choose their

corresponding case.

Pre-Condition The case not selected.

Post-Condition Case is selected.

Exception Not selected.

Alternate Path Try again.

Table Error! No text of specified style in document.-2 Use Case of Case Updates
 Edit Profile
Use Case Title

Use Case ID UC- Edit Profile-08

Description
The Clients And lawyers can update or edit teir profile.

Actor Client , Lawyers

Actor Action Response

1.Client have to choose

their profile to edit.
2.The admin will check the modifications of the
3.Lawyers have to choose
changes profile and then approve it.
their profile to edit.

Pre-Condition Profile not selected.

Post-Condition Profile selected.

Exception This changes can’t be done at this time.

Alternate Path Try other.

Table Error! No text of specified style in document.-3 Use Case of Edit Profile
 Submit Feedback
Use Case Title

Use Case ID UC- Submitfeedback -09

Description
The Clients can give feedback to their lawyers at the end of the case.

Actor Clients

Actor Action Response

1.Clients give feedback to 3. Supervisor is allotted to students with no

their clients supervisors.

2.Lawyers can review it at

any time.

Pre-Condition No feedback is given before.

Post-Condition Feedbak submitted.

Exception The Clients can’t use abusive language.

Alternate Path Try agian.

Table Error! No text of specified style in document.-4 Use Case of Submit Feedback
 Review Feedback
Use Case Title

Use Case ID UC- Reviewfeedback -10

Description
The Lawyers and admins can review the feedback.

Actor Lawyers, Admins

Actor Action Response

1.Lawyers can review the 2. Admin can edit and delete this review at any
feedback. time.

Pre-Condition No feedback submitted before.

Post-Condition Reviewed successfully.

Exception Time delay.

Alternate Path Try again.

Table Error! No text of specified style in document.-10 Use Case of Feedback Review
 ApproveRegistration
Use Case Title

Use Case ID UC- Approveregistration -11

Description
The Admin have to approve the registrations of the clients and the Laywers both.

Actor Admin

Actor Action Response

1.Admin opens the 5. Client get confirmations message .

request.
3.Lawyers get confirmation message.
4.Admin accepts the
request.

2.Admin rejects the

request.

Pre-Condition No registered before.

Post-Condition Registration is successful.

Exception No request sent to Admin.

Alternate Path Select other.

Table Error! No text of specified style in document.-11 Use Case of Approve Registration
3.1. USE CASE

3.1.1Usecase Diagram

Figure 3.1.1 Use Case Diagram

3.2. CLASS DIAGRAM

3.2.1Class Diagram

Figure 3.2.1 Class Diagram

3.3. ENTITY RELATIONSHIP DIAGRAM

3.3.1ER Diagram

Figure 3.3.1 ER Diagram

3.4. SEQUENCE DIAGRAM

3.4.1Registration Sequence Diagram

:ApplicationPanel :RegisteredUser :DBConnection

: User

1: RequestForRegistration()

2: DisplayForm()

3: FillsRegistrationForm()

4: GetData()

5: ValidateData()

6: EnterValidData()

7: SaveRecord()

8: CreateAccount()

9: Response

10: Response

11: LoginForm

12: UserId&Password()

13: LoginDetails()

14: LoginQuery()

15: Validation

16: QuerySuccessfull

17: ValidMember

18: LoginSuccessfully

Figure 3.4.1 Registration Sequence Diagram

 3.4.2Search Lawyer Sequence Diagram

Figure 3.4.2 Search Lawyer Sequence Diagram

 3.4.3Select Lawyer Sequence Diagram

Figure 3.4.3 Select Lawyer Sequence Diagram

 3.4.4Start Conversation Sequence Diagram

Figure 3.4.4 Start Converstation Sequence Diagram

 3.4.5Case Updates Sequence Diagram

Figure 3.4.5 Case Updates Sequence Diagram

 3.4.6Edit Profile Sequence Diagram

Figure 3.4.6 Edit Profile Sequence Diagram

 3.4.7Location Based Sequence Diagram

Figure 3.4.7 Location Based Sequence Diagram

 3.4.8Submit Feedback Sequence Diagram

Figure 3.4.8 Submit Feedback Sequence Diagram

3.5. COLLABORATION DIAGRAM

3.5.1Registration Diagram

1: RequestForRegistration()
3: FillsRegistrationForm()
12: UserId&Password()
:Application
Panel
2: DisplayForm()
: User 11: LoginForm
18: LoginSuccessfully
4: GetData()
10: Response 13: LoginDetails()
17: ValidMember
15: Validation
6: EnterValidData()

16: QuerySuccessfull
9: Response
:DBConnection :RegisteredUser

7: SaveRecord()
8: CreateAccount()
14: LoginQuery() 5: ValidateData()

Figure 3.5.1 Registration Diagram

 3.5.2 Search Lawyer Diagram

Figure 3.5.2 Search Lawyer Diagram

 3.5.3 Start Conversation Diagram

Figure 3.5.3 Start Conversation Diagram

 3.5.4 Case Updates Diagram

Figure 3.5.4 Case Updates Diagram

3.5.5 Edit Profile Diagram

Figure 3.5.5 Edit Profile

 3.5.6 Location Based Diagram

Figure 3.5.6 Location Based Diagram

3.5.7 Submit Feedback Diagram

Figure 3.5.7 Submit Feedback

3.6. ACTIVITY DIAGRAM

3.6.1 Login Diagram

Figure 3.6.1 Login Diagram

 3.6.2 Registration Diagram

Figure 3.6.2 Registration Diagram

 3.6.3 Search Lawyer Diagram

Figure 3.6.3 Search Lawyer Diagram

 3.6.4 Select Lawyer Diagram

Figure 3.6.4 Select Lawyer Diagram

 3.6.5 Start Conversation Diagram

Figure 3.6.5 Start Conversation Diagram

3.6.6 Edit Profile Diagram

3.6.6 Edit Profile Diagram

3.6.7 Client Feedback Profile Diagram

3.6.7 Client Feedback Profile Diagram

3.7. DEPLOYMENT DIAGRAM

Figure 3.7 Deployment Diagram

3.8. COMPONENT DIAGRAM

Figure 3.8 Component Diagram