A

PROJECT WORK

ON

“computer service management

system ”

Submitted by:
Nikumbh Chinmay Milind(21497)

FY MCA ( Semester: 1 )

Guided By
Prof. G M Badhe
Assistant Professor, MCA Department

P.E. Society's

Modern Institute of Business Studies,

Nigdi, Pune - 411044
2020 - 2021

1
 P.E. Society's

Modern Institute of Business Studies,

Nigdi, Pune - 411044
2020 - 2021

CERTIFICATE

This is to certify that,Mr./Miss Nikumbh Chinmay Milind. Has

satisfactory completed his/her/their project on Computer Service
Management System fulfillment in MCA Department for the academic
year 2020-2021.

Prof. Gajanan Badhe

(Project Guide )

Internal Examiner External Examiner

 Sr. No. Chapter Name Page No.
1 Chapter 1: Introduction
1.1 Project Objectives
1.2 Existing System and Need of System
1.3 Scope of work
1.4 Operating Environment-Hardware and Software
1.5 Technology Used
1.6 Module Specification
2 Chapter 2: Analysis & Design
2.1 Data Flow Diagram
2.2 Entity Relationship Diagram
2.3 Use Case Diagram
2.4 Activity Diagram
2.5 Sequence Diagram
2.6 Class Diagram
2.7 User Interface Screens
2.8 Table Structure
3 Drawbacks and Limitations
4 Proposed Enhancement
5 Conclusion
6 Bibliography
 1. Chapter 1: Introduction :-

➢ Computer Service Management System is a web application which provides an interactive

platform between users and computer services provider companies.

➢ This project provides best and reliable ac services. In proposed system we do not have to maintain

everything manually.

➢ Through this system if any enquiry occurs it is corresponding entries is done automatically

because database management system gives facility of having relationship between the tables.

➢ In proposed system we do not have to maintain record manually.

1.1 Project Objectives:-

➢ Easy to generate report booking and queries.

➢ Provide an interactive platform between clients and ac repairing companies.

➢ It is very much faster than manual system.

➢ Easy and fastest record finding technique.

➢ It is very much flexible to work.

➢ It is very user oriented.

➢ Data can be stored for a longer period.

1.2 Existing System and Need of System:-

 • Existing System

➢ In the existing system, most of the operations are done manually like register complaints, taking

action on complaints, view status, etc.

➢ Lots of paper work.

➢ Time consuming.

➢ Difficult to maintain records

• Need of System :-

➢ Proposed system provides user-friendly application so that victim can easily register
their orders and Admin can easily take action on those Orders.

➢ Using proposed system maintaining records become easy.

1.3 Scope of Work :-

➢ Scope of building this website was to have user register their Orders from anywhere
therefore user do not have to go the manual store for Repairing System.
➢ By having this system, admin could handle more Orders at a time.
➢ Maintaining records are faster and easier for admin.
➢ Reports in this system keep the records of all the ordered Services.

1.4 Operating Environment – Hardware and Software:

➢ Hardware:

• Processor: Intel Core i3 or equivalent

• RAM: 4GB DDR3

• Display: Monitor

• Mouse, Keyboard, LAN cable, router

➢ Software:
 • Any Operating System

• Xampp

• VS Code

• Any web browser

1.5 Technologies Being Used :-

➢ Front End - HTML, CSS and JAVASCRIPT

➢ Back End – PHP, MYSQL

1.6 Modules Specification :-

➢ User :-

➢ Dashboard: It is a welcome page for users.

➢ Invoices: In this section, user can view his/her own invoices which are generated by admin.

➢ Search Invoices: In this section, use can search his/her own invoices details with the help invoice

number

➢ Chatbot:- User can communicate with admin.

➢ User can also update his profile, change the password and recover the password.

➢ Admin:-
➢ Admin is the super user of the website who can manage everything on the website. Admin can

also update his profile, change the password and recover the password.

➢ Dashboard: In this section, admin can view all the detail in brief like total services, total users

and total invoices

➢ Services: In this section, admin can manage services(add/update/del).

➢ Pages: In this section, admin can manage about us and contact us pages.

➢ Customer List: In this section, admin can view registered users details and generate invoices.

➢ Chatbot:- Admin can communicate with user.

➢ Invoices: In this section, admin can view customer’s invoices which are generated by him/her.

➢ Reports: In this section, admin can generate between dates reports of invoices.

➢ Search Invoices: In this section, admin can search invoices details with the help invoice number.

➢ Report Management
1. Chapter 2: Analysis & Design :

1.1 Context Level DFD :

1.2 Entity Relationship Diagram (ERD) :
 1.3 Use Case Diagram :
➢ User:-
➢ Admin

1.4 Activity Diagrams :

1. User :
I User Is Registered

Start

”
ter User Login Credent I

Succes sful

yes

Dashboard I

Select Service

NO

Successful

yes

.Poceed To

FIO

Successful

yes

" Payment success

Logout
2. Admin:
 1.5 Sequence Diagrams :

1. Admin:

2.User:-
 COMSMS DATABASE
USER

Register Validate

Registered

Login Validate User

Login Suc c es sfull Verified

Select Service Service Details

< Service Selected Acknowledge

Pavment

< Payment Success Validate

Reoun st Invnir n Invoice Details

< View Invoice < Acknowledge

 1.6 Class Diagram :

1.7 User interface screens:

➢ Home Page:
Login page:
Sign Up page:

Forget Password:

User dashboard:
Invoice:

Search Invoice:
Chatbox:-
 ➢ Admin Side:

Login Page:

Forget Password:
Admin Dashboard:

Admin Side :

Admin Dashboard:
Add Service:

Manage Service:
Pages:-

Customer List:
Order List :-

Invoices:-
Search Invoice:-

Report:-
 2.8 Database Design

Admin table:
User Table:

Invoice Table:-
Order Table:-

Page Table:-
Services Table:-

2. Drawbacks and Limitations:

3.
➢ Drawbacks:
 This website does not generate a person reports therefore user cannot know who is out for
getting their System.

➢ Limitations:

This website does not covers any buying of product of System.

4. Proposed Enhancement:

➢ We enhance this project where User can see the area where the System is out for Repairing.

➢ Adding Required Time module where user will get to know The Estimated Time for the
Service.

5. CONCLUSION:

The Software developed is found to be working efficiently and effectively. It results in regular

and timely action against Order Updated. It can be observed that the information can be obtained

easily and accurately. The Software is made user friendly to the maximum so that any layman

can run the software provided he could access to the system via the login password. It believes

that partnership work is highly beneficial to the organization and that partnership work is the

way forward to reduce the time for Basic Services to handle and order.

The Application was designed in such a way that future changes can be done easily. The

following conclusions can be deduced from the development of the project.

• Automation of the entire system improves the productivity.

• It provides a friendly graphical user interface which proves to be better when compared to the

existing system.

• It gives appropriate access to the authorized users depending on their permissions.

• It effectively overcomes the delay in communications.

• Updating of information becomes so easier.

• The System has adequate scope for modification in future if it is necessary.

3. Bibliography:

For PHP
• https://www.w3schools.com/php/default.asp
• https://www.sitepoint.com/php/
• https://www.php.net/

For MySQL
• https://www.mysql.com/
• http://www.mysqltutorial.org

For XAMPP
• https://www.apachefriends.org/download.html

Annexure 1 : USER INTERFACE SCREENS :

User Side :

Sign Up page :
Sign In Page :

Admin Side :

Admin Dashboard:
Add Service:

Manage Service:
Pages:-

Customer List:
Order List :-

Invoices:-
Search Invoice:-

Report:-
Validation for Sign Up page: