CASE MANAGEMENT SYSTEM

INTRODUCTION OF CASE INFORMATION MANAGEMENT SYSTEM:

Are you looking for Case information management system for your final year project? We are here to help you. You can contact us

Case Information Management System is cloud based software. This software is meant to be used by Lawyers or Advocates. This is very powerful software.

Any client(Lawyer) who is using this software does not need to worry about maintaining any paperwork. This software would maintain everything which an advocate needs to do.

This software will store the data about advocate’s client, opponents, Case no., case details, Previous hearing date, next hearing date, court name, employee details, case related document. This software is secure to store data.

Every sensitive information is encrypted using cryptography. This software makes easy to search about the case or case details using the search option. You can search by case no., next hearing date, client, or employee (junior advocate).

The software would also manage the day to day meetings, appointments. This system will notify the user for appointments, meeting. The client can search about advocate, view their profiles, and book their slot if available. If an advocate is ready to take the case.

An advocate can verify it. Then client pays the advance fee using online payment portal. Finally, Software would help the advocates/lawyers in maintaining their offices.

MODULES OF CASE INFORMATION MANAGEMENT SYSTEM:

There are several modules required to complete this system. Here we are discussing the main modules or core modules of the system.

ADMIN PROFILE:

Admin is a super user of our system. Admin can view all data in the system. Admin must log in to the system then there is authentication process. Admin is basically senior advocate. Admin can add case details, verify employee, details, accept case etc.

CLIENT PROFILE:

The client is the end user of this system. The client can search the advocates in the system. The client can view advocate’s profile, their winning percentage, experience, age etc. Clients can hire the advocate for their cases. They can pay the fee using a payment gateway.

EMPLOYEE PROFILE:

In any advocate office, there are a lot of employees. Senior advocate finds it difficult to manage them. This system would help him/her to manage employee works, pay the salary etc. An employee can see the task assigned to him/her. They can arrange a meeting, update hearing details, case details, contact to client etc.

CASE:

Every case information needs to be entered in the system. Once a case is entered into the system. It is assigned to an advocate with case id. After a case is being created, the employee can update the information like case hearing date, the status of the case, client information, document etc.

NOTIFICATION AND MESSAGES:

This system has a fully automated process of notification. The advocate would be notified about next hearing with case details. The employee would receive notification about case assignment, meeting etc. Admin would get a notification whenever a new client or case is registered to the system.

FACILITIES:

PRINTOUTS:

Details of the case can be printed and a hard copy can be used to distribute.

PDF FILE:

Pdf can be used as soft copy.

EMAIL:

Every information in the system can send via email.

SORTING:

Information can be sorted on the basis of many information.

BACKUP:

Backup is being taken every day.

RECOVERY:

Any failure then backup can be restored.

SYSTEM DESIGN OF CASE INFORMATION MANAGEMENT SYSTEM:

The system basically needs very simple architecture. This is system is their main three users i.e. Admin(Advocate), Client, Employee.

USE CASES FOR ADMIN OF CASE INFORMATION MANAGEMENT SYSTEM:

Admin is a most important person of this system. Admin is a super user of this Case Management System. Admin is a senior advocate of offices. Admin must have a login and complete authentication process.
Now, the admin has complete access to the system. Admin can add cases, edit, update cases. Admin can manage the employee details, their salary, work assignment. Admin has the power to assign a case to any lawyer in the office. Admin also manages the client details.

USE CASES FOR EMPLOYEE OF CASE INFORMATION MANAGEMENT SYSTEM:

Employees are man power in offices. An employee can register to the system. Admin would get a notification.

When admin would verify the employee identity only then the employee would able to access the system. After successful registration, the employee needs to log in and authentication process does occur. An employee can view those cases assigned to them.

They can update the case information like hearing a date, case updates. They can contact the client and provide the case status as well as ask the case related information. They can contact to them using phone or email.

USE CASES FOR CLIENTS OF CASE INFORMATION MANAGEMENT SYSTEM:

The client is the end user of the system. Before doing anything, the user needs to register with the system. Admin would verify the client details. Once the client is verified. Clients can log in to the system.

Clients can search the advocate using the name, case win percentage, or case type etc. when they find the best one. They can register one case with that advocate. Admin would verify the case and assign to the employee(Advocate).

Clients can then pay the advocate fee using the online gateway.The client is the end user of the system. Before doing anything, the user needs to register with the system. Admin would verify the client details. Once the client is verified.

Clients can log in to the system. Clients can search the advocate using the name, case win percentage, or case type etc. when they find the best one. They can register one case with that advocate.

Admin would verify the case and assign to the employee(Advocate). Clients can the pay then advocate fee using the online gateway.

USER INTERFACE(UI) OF CASE INFORMATION MANAGEMENT SYSTEM:

The user interface is very important part of the system. A good and user-friendly interface attracts the user toward it. Whereas a bad one makes the user experience bad and they never return to the system. As we have shown several use cases in this system. We have developed these interfaces to interact with the system.

LOGIN PAGE:

Admin, client and employee need to log in using login id and password. The system authenticates every user. The only valid user can access the data.

ADMIN PAGE:

This page is dedicated to a senior advocate of offices. This page contains the link to cases, link to employees, link to client’s details. This page also shows to highlighted cases.

CLIENT PAGE:

This page shows the client details. Clients can access recommended advocates. Clients can view the case update using this interface.

CASE PAGE:

This page is common to admin, employee, clients with a different access level. Only admin has the super power to change the data.

EMPLOYEE PAGE:

This interface helps the employee to view their work, notification, manage cases, update cases etc.

ER-DIAGRAM OF CASE INFORMATION MANAGEMENT SYSTEM

ERD of case information management system:

There are mainly Six Entities Admin, Employee, client, log in, case, Payment. These five entities would manage the whole system.

ADMIN:

Admin is a super user of the system. Admin has all right to view and modify the data in the system. Admin is a senior advocate of office. Admin has followings attributes.

ADVOCATEID:

This is numeric 14 digits number which is unique to every admin. AdvocateID is the primary key to admin table in the database.

NAME:

This attribute would hold the name of admin. The name is varchar type variable which holds the data length up to 250 characters.

EMAIL:

This is an essential attribute of the table. Every admin must have a working email id to keep in contact with employees. This field has validation only email formatted values will be stored.

CONTACT.:

This is multi valued attributes which mean every admin can have more the one mobile number in database.

ADDRESS:

This attribute would hold the address of admin. Each employee must provide the address.

AGE:

This would help the client to better understand the advocate.

WORK PROFILE:

work profile would able to describe the advocate professional background.Advocate type would help them to hire the lawyer for the specific case. Experience would also give the client better understanding of advocate. Case win percentage can easily be related to success chance of winning.

LOGIN:

This system contains a lot of sensitive information which needs to be secure. unwanted, unauthenticated, access should not be permitted to achieve this goal. we have a user id and password for every user. Login entity has followings attributes.

USER ID:

This is an alpha numeric 10-50 character. This is unique to every user in this system. Two users can’t have the same username.

PASSWORD:

This attribute holds the encrypted value of password chosen by the user. The password is 8-25 characters alpha numeric with case sensitive.

EMPLOYEE:

The employee is another user of the system. An employee can view cases, manage the case details. The employee has followings attributes.

EMPID:

This is numeric 14 digits number which is unique to every Employee. EmpID is the primary key to Employee table in the database.

NAME:

This attribute would hold the name of Employee. The name is varchar type variable which holds the data length up to 50 characters.

EMAIL:

This is an essential attribute of the table. Every employee must have a working email id to keep in contact with employees. This field has validation only email formatted values will be stored.

CONTACT.:

This is multi valued attributes which mean every employee can have more the one mobile number in database.

ADDRESS:

This attribute would hold the address of the employee. Each employee must provide the address.

EMPLOYEE TYPE:

This field stores the information about employee whether the employee is an advocate or junior staff or helper. On the basis of this, they would assign to the user profile.

ASSIGN CASE:

An employee can see the information about the case assigned to them using this attribute.

CLIENT:

The client is the basic end user of our system most of the business is done through them. Clients would give the case to advocate. The client would provide the feedback. The client has following attributes.

CLIENTID:

This is numeric 14 digits number which is unique to every Client. ClientID is the primary key to client table in the database.

NAME:

This attribute would hold the name of clients. The name is varchar type variable which holds the data length up to 50 characters.

EMAIL.:

This is an essential attribute of the table. Every client must have a working email id. This field has validation only email formatted values will be stored.

ADDRESS:

This attribute would hold the address of clients. Address of clients would help us to connect with them and visit the location. This would provide better services.

CASE:

Every case registered with the system has the information in this entity. Cases are the main concern of system.

CASEID:

This is numeric 14 digits number which is unique to every case. CaseID is the primary key to case table in the database. Each case is uniquely identified using this id.

CASE TYPE:

There are several types of criminal and non-criminal case. Every case should be assigned to a type so that we can classify them into the group. Which would help us to manage the case efficiently?

CASE DETAILS:

Case detail would periodically update. As the case goes on case details would also be updated.

COURT NAME.:

Every case has been heard in specific court. This attribute holds the court name with address.

ADVOCATEID:

Every case is assigned to an advocate. This attribute is a foreign key to Admin table or employee. Advocate details can be fetched using this.

LAST HEARING DATE:

This field store the data about last hearing of the case.

NEXT HEARING DATE:

This field store the data about next hearing of the case.

PAYMENT:

Payment Entity store the data about payment. Every payment data is here. Any conflict can be resolved by looking to this.

PAYMENTID:

This is numeric 14 digits number which is unique to every Payment. PaymentID is the primary key to case table in the database. Each Payment is uniquely identified using this id.

CASEID:

This is a reference to a case. This would help the admin to find this payment is in this case.

DATE:

This would hold the date of the transaction.

TRANSACTIONNO.:

The transaction number is reference no given by the bank.

STATUS:

Status of every transaction either it would be pending or confirm is being updated in this field.

FUNCTIONAL AND NON-FUNCTIONAL REQUIREMENTS OF CASE INFORMATION MANAGEMENT SYSTEM:

There are two types of requirement of the system in any system, these are:

FUNCTIONAL REQUIREMENT OF CASE INFORMATION MANAGEMENT SYSTEM:

REGISTRATION:

Users can register their self in the system. Admin will verify their profile to work properly. Once a user is registered with system User

VALIDATION:

Validation is very important in the system. Invalid data can corrupt the valid data. So, we need to apply validation in each module. Validation would ensure the safety and security of data.

EMPLOYEE RECORD:

Employee data should be secure. We should take care of employees’ data privacy in our mind. Employee performance excels the performance of company too.

CLIENT RECORD:

Client profile would record the information about client and client details would help the client to choose the case and assign the case.

CASE RECORD:

Case records are the record which needs to update periodically and secured.

NON-FUNCTIONAL REQUIREMENT OF CASE INFORMATION MANAGEMENT SYSTEM:

IMPROVE SECURITY:

This system has multilevel profiles. The lower profile should not view upper profiles. System security should be ensured in this system.

SUPPORT MULTI USER:

Nowadays, every system work in an environment of multi users. As per requirement of system our, the system is developed in multi user’s environment.

FAST:

Every module should to compatible with other modules. There should not be any lag or delay in processing the data.

AVAILABLE(24X7):

Case Management System should be available to clients 24X7. The user can access the system whenever they need to access, wherever they want to access provided having an internet connection and device to access.

DESIGN DATA DICTIONARY FOR ER-DIAGRAM OF CASE INFORMATION MANAGEMENT SYSTEM:

The data dictionary is useful in case of development.

Table Name: AdminMaster

Primary Key: AdvocateID

Description: To store the details of admin

Serial No.	Fields	Datatype	Description
1.	AdvocateID	Integer	Primary key
2.	Name	Varchar
3.	EmailID	Varchar
4.	Contact.	Integer	Multiple contacts can exist for single admin
5.	Address	Varchar
6.	Age	Number
7.	Work Profile	Varchar

Table Name: LoginMaster

Primary Key: UserID

Description: To store the details of Login table

Serial No.	Fields	Datatype	Description
1.	UserID	varchar	Primary key
2.	Password	varchar

Table Name: CaseMaster

Primary Key: CaseID

Description: To store the details of case

Serial No.	Fields	Datatype	Description
1.	CaseID	Integer	Primary key
2.	Case Type	varchar
3.	Case Details	varchar
4.	Court Name	Varchar
5.	AdvocateID	Integer	Foreign key to admin table(Advocate)
6.	Last Hearing date	Date
7.	Next Hearing date	Date

Table Name: EmployeeMaster

Primary Key: EmpID

Description: To store the details of Employee Details

Serial No.	Fields	Datatype	Description
1.	EmpID	Integer	Primary key
2.	Name	varchar
3.	Email	varchar
4.	Contact.	Integer	Multiple contacts can exist for single admin
5.	Address	varchar
6.	Employee Type	varchar
7.	Assig case	Integer

Table Name: ClientMaster

Primary Key: ClientID

Description: To store the details of Clients

Serial No.	Fields	Datatype	Description
1.	ClientID	Integer	Primary key
2.	Name	varchar
3.	Contact	integer	Multiple contacts can exist for single client
4.	Address	varchar

Table Name: PaymentMaster

Primary Key: PaymentID

Description: To store the details of Payment

Serial No.	Fields	Datatype	Description
1.	PaymentID	Integer	Primary key
2.	CaseID	Integer	Foreign key to CaseMaster
3.	Date	date
4.	Transaction No.	varchar
5.	Status	varchar