Mobile Service Management System

A
Project
Submitted for the partial fulfilment to Award of Degree of

BCA(HONS)
In

The Department of Mathematical Sciences & Computer

Applications

Bundelkhand University Jhansi

2021-2022

Supervision of: Submitted by:

Dr.Kamlesh K. Verma Sunaina Sahu
Dr.Saurabh Shrivastav (191341133082)

1
 Content
S.No Title Page No.
Acknowledgement 1
o
Project Description
1. 1.1 Existing System 3
1.2 Proposed System
2. Objective 5

3. Technologies used
3.1 Front-End 7
3.2 Back-End
4. Modules
4.1 Mobile Management Service
Modules 9
4.1.1 Authentication
4.1.2 Maintenance
5. Feasibility Study
5.1 Technical Feasibility
5.2 Operational Feasibility 11
5.3 Economic Feasibilty
5.4 Social Feasibility
6. Overall Descriptions
6.1 Product Perspective
6.2 User Interface 12-14
6.3 Software Interface
6.4 Hardware Interface
7. Product Functions
7.1 User Characterstics 15-21
7.2 Assumptions and Dependencies
7.3 Specific Requirements
2
 7.4 External Interfaces
8. Database Design 21-24
8.1 Database Description

9. User Interface Design 25-38

o Conclusion 39

3
 CERTIFICATE

This is to certify that this project entitled MOBILE SERVICE MANAGEMENT

SYSTEM is a bonafide work carried out by Sunaina Sahu Submitted to
Bundelkhand University in partial fulfillment of the requirements for the award
of Bachelor of Computer Applications.

Guide External Examiner HOD

DR. Kamlesh Verma DR. Saurabh Srivastava Prof R.K Saini

4
 CANDIDATE'S DECLERATION

I hereby declared that the work being presented in this project ended "MOBILE
SERVICE MANAGEMENT SYSTEM", for partial fulfilment of the requirement to
award a degree of “BCA(HONS)” is an authentic record of my own work camed
out under the supervision of Dr. Kamlesh Verma & Dr. Saurabh Shrivastav
The matter embodied in this project has not been submitted by me for the
award of any other degree diploma elsewhere.

SUNAINA SAHU
(191341133082)

5
 ACKNOWLEGEMENT

In carving of this thesis. I owe my deepest gratitude to my supervisor, Dr.

Kamlesh K. Verma & Dr. Saurabh Shrivastav, Department of
Mathematical Sciences and Computer Applications Bundelkhand University,
Jhansi without whose willing cooperation and encouragement, the work have
been a fruitless venture.

I express my deep thanks to the serviceman members Dr. RK. Saini,HOD of the
department for his cooperation and support. I also express my thanks to Dr
Saurabh Srivastava, Dr. Kamlesh K. Verma and Dr. Dharamdas Prajapati for
their valuable suggestions.

I would like to thanks my serviceman Kamal Gupta, Sharad Dubey and Sachin
Upadhayay.

I found no words to express my hearty feeling towards my parents Mr. Kishan

Dutt and Mrs. Neelu Sahu providing me all kind of help which gave me
encouragement and to complete this project.

I also thanks to colleagues' friends Shreya Gupta, Susheel Verma and Mohit
Kumar for their immense support and help

SUNAINA SAHU
(191341133082)

6
 Project
Description

7
 1. Project Description

1.1 Existing System

In the existing Mobile Service Management System the data is stored in the excel, to
maintain the data in the excel there are a huge amount of time is required. The
maintenance of data in the excel sheet is not an easy process as one need to remember the
name of the excel sheet. While if a person remembers the name then also it takes the time
to search the file. The present Mobile Service Management System requires high amount
work to maintain an excel sheet which requires a lot of men to do the work, and hence the
overall cost required to work is large whereas the accuracy of the system is not that good.

1.2 Proposed system

In the mobile service provider operation portal is an internet based system so it provides all
the functions without installing the software into the system. As the system is internet
based it allow to access many numbers of the person at the same time. It has a graphical
interface so the use of the product is easy and anyone can use it without learning anything
new. The Mobile Service Provider system can be accessed from the organization or by
outside the organization means by the customer if they provide a valid Id. As the Mobile
Service Provider system automate most of the task, it speeds up the operation in the
industries and provides better user experience than the existing system.

8
Objective

9
 2. Objective

The main objective of this Mobile Service Management System project is to build an online
system through which a telecom company and customers can connect to each other. This
Mobile Service Management System will automate the operation of the telecom service
company and make the system simpler. Our project will help the customer to get the
mobile service easy at a reduced price rate. The project will aim to help an organization to
make their service excellent, time efficient at the low cost.

10
Technologies
Used

11
 3. Technologies used

 PHP 5.6
 MYSQL
 JAVASRIPT
 HTML
 CSS
 WAMP 2.0

3.1 Front-End
 HTML
 CSS
 JAVASCRIPT

3.2 Back-End
 PHP
 MYSQL

12
Modules

13
 4. modules

4.1 Mobile Service Management System Modules

The system has two modules in it, they are authentication and maintenance.

4.1.1 Authentication
This module contains option by use of which anyone can access the system they
just need a valid ID and password. At first login they will provide with the
system generated ID and password, but after the first login, they can change
their password while Id can’t be changed.

4.1.2 Maintenance
This module provides various options by use of which a customer can use the
service provided by the operator. The user won’t need to go anywhere to get
the service they will need to access the system and then they can get all the
service. The service will be like pin change, sound problem etc.

14
Feasibility
Study

15
 5. feasibility study

Depending on the results of initial investigation, the survey is expanded to a more detailed
feasibility study. Feasibility study is a test of system proposal according to its work ability,
impact on the organization ability to meet user needs, and effective use of resources. The
three major areas under the feasibility study of project.
 Technical Feasibility
 Operational Feasibility
 Economic Feasibility
 Social Feasibility

5.1. Technical Feasibility

It is a measure of the practically of a specific technical solution and the availability of the
technical expertise and resources.

5.2. Operational Feasibility

The system will be used if it is developed well then be resistance for users that
undetermined.

5.3. Economical Feasibility

It looks at the financial aspects of the project; it determines whether the management has
resources and budget to invest in the proposed system and the estimate time for de cost to
be incurred.

5.4. Social Feasibility

The assessment of social feasibility will be done alongside technical feasibility. Each of the
alternative technical solutions that emerge must be evaluated for its social implication.

16
 Overall
Descriptions

17
 6. overall descriptions
The Mobile Service Management System is to be designed for users dicuss the various
mobile related problems on their desktop online. With the help of this the user, admin and
serviceman can connect with each other through the online mode.
Various features can be used by viewing the project are:

6.1. Product Perspective

The Mobile Service Management System is a PHP based service system that resides on the
servers as well as the client machines that has an Windows operating system. The database
used to store the data will be Microsoft SQL server 2019.

6.2. User Interface

The Primary interface via which user will interact with the system is a Web Browser and for
the system is should be Google Chrome. And definitely an Intranet connection is required.
Format of main screen shall be standard and flexible. The System shall be user friendly
designed. Pages shall be connected each other in consistent way.

6.3 Software Interfaces

 Client
Operating System: Window 10/11, MacOS
Web Server: Apache HTTP Server

 Server
Operating System: Window 10/11
Web Server: XAMPP Server , WAMP Server ,
Database Server: MYSQL,MariaDB

18
6.4. Hardware Interfaces

 Client
Any machine that has Intranet connection.

For PC (Windows)
Processor: Core i3 and Core i5
RAM: 2 GB to 16 GB

 Server
Processor: Core i3 and Core i5
RAM: 2 GB to 16 GB

19
 Product
Functions

20
 7. product functions
The system will have the following provision:

 The user, admin and serviceman are provided with the specific ID and password.
 They will login to the system by using the login ID and password.
 All the registered users should be available to the admin and serviceman at any point
of time.
 Three roles are identified for this system:
User
Admin
Serviceman
 According to the roles system functions have been divided amongst three
modules/components with each of them specific to the User role. They are started as
under:

Module 1 :

As an user of the system:

 Should be able to login into the system.

 Should be able to fill the request form.
 Should be able to check the status of the request.
 Should be able to create an otp.

Module 2:

As an admin of the system:

 Should be able to login into the system.

 Should be able to check the request form submitted by the user.
 Should be able to accept, reject and close request.
 Should be able to retrieve any user information or details.

21
 Module 3:

As a serviceman of the system:

 Should be able to login into the system.

 Should be able to check the request form submitted by the user.
 Should be able to process the request form.
 Provide authenticity by asking user for otp.
 Status of the form will be closed after processing.

22
 7.1 User characterstics:
The user of this system must possess the following characterstics:

1. The user should have Samsung phone.

2. Educational level: User should be comfortable with the English Language.
3. Technical Expertise: Should be comfortable using general purpose applications.

 Constraints:
The following constraints applied to this system:
1. The system is for the use of Samsung users only.
2. To fill the request form or check for the status the user must have a valid login ID and
password.
3. For creating token number the user will be provided with the otp.

7.2 Assumpstions and Dependencies

1. The user must be connected to the intranet to use the system.
2. The problem mentioned in the request form should not be changed by the user.
3. The user’s computer must be Windows 10 or later version platforms.
4. The accuracy of the information of users is the responsibility of all users.

7.3 Specific Requirements

This section contains all the software requirements at a level of detail, sufficient to enable
designers to design a system to satisfy those requirements. 6.4. External Interfaces

7.4 External Interfaces

The external interface requirements refer to the user interfaces that have been designed
for the user to interact with the system and perform the required tasks as mentioned in the
product functions. The system shall provide the following interfaces to the user for
accessing the system:

23
The system shall have same interface(s) for all the users entering to the system a user
specifies his/her role-of-login

Such interfaces are:

Home: This interface shall provide to user some information about the system he/she is
going to use, as well as shall provide to user an option to fill request form, check the status
and provide login/logout option.
Login: This interface shell provides a way to authenticating the accessing user.
Admin Login Page: This interface shell provides Admin a way to itself for accessing its
MSMS modules.
MSMS Serviceman Login Page: This interface shell provides serviceman a way to
authenticate itself for accessing its MSMS modules.
MSMS User Login Page: This interface shell provides user a way to authenticate itself for
accessing its MSMS modules.
Specify the Role: This interface shall ask to the user for the role, amongst his/her assigned
role, he/she wants to access the system with .
Contact US: This interface shell provides contact information about the admin and the
serviceman.

* Depending on the role chosen, the user will have different interfaces as stated below:

User: This interface shall give way to the following interfaces:

Generate Token: The user will generate its specific token number by clicking on the New
Request tag.
To generate token user has to provide some information:
 The user should provide with its name.
 The user should be the Samsung user only.
 The user should provide the bill number which was given to them while buying
the phone.
 The user should provide with the brand name and model name.
 In the description box the user can explain their problem which they are facing
in the phone.
24
  After providing all the information click on the submit button.
 After submitting a token with specific number will be created by providing the
otp send.
 The form will get forwarded to the admin.
History: The user can check for the previous token information.
Search: The user can search for any information by providing valid service ID number.
Logout: The user can get logged out from the page by clicking on the logout tag.

Admin: This interface shall give way to the following interfaces:

Token requests:
 Total Request: On the admin dashboard all the request will be shown with their
information.
 Pending Request: The requests that did not get confirm from the admin will remain
on pending.
 Confirm Request: The requests that get the confirm status by the admin are showm
in the confirm request option.
 Processing Request: The request which are still processing.
 Closed Request: The admin set the status as closed when the process of the request
is completed.
 Rejected Request: The request that cannot be processed by them gets rets rejected
by the admin.

Search: The admin can search for any information by providing valid service ID number.
Logout: The admin can get logged out from the page by clicking on the logout tag.

Serviceman: This interface shall give way to the following interfaces:

Token Request:
 New Request: The request sent sent by the user.
 Processing Request: The request which are still processing.
 Closed Request: The serviceman set the status as closed when the process of the
request is completed.
Search: The admin can search for any information by providing valid service ID number.
Logout: The admin can get logged out from the page by clicking on the logout tag.
25
Website
Workflow
Diagram

26
27
Database
Design

28
 8. database design

8.1 Database Description

In this we include, maintain & format Databases and its tables.
The tables corresponding to each of the entity, holding the information about them are
designed.
The tables have the fields, their description, and their data type as well as integrity
constraints.

Xyz_crm

 login

Column Type Null Default Comments

sno(Primary) int(100) No
ac_type varchar(11) No
Pass varchar(30) No
Email varchar(100) No
Name varchar(100) No
Phone varchar(100) No
Photo varchar(100) No

 Indexes

Keyname Type Unique Packed Column Cardinality Collation Null Comment

PRIMARY BTREE YES No sno 6 A No

email BTREE YES No email 6 A NO

29
  Otp

Column Type Null Default Comments

sno(Primary) int(100) No
Tokenno varchar(100) No
Otp varchar(100) No
Date varchar(100) No

 Indexes

Keyname Type Unique Packed Column Cardinality Collation Null Comment

PRIMARY BTREE YES No sno 0 A No

Email BTREE YES No sno 0 A NO

 request_table

Column Type Null Default Comments

Tokenno(Primary) int(100) No
Name varchar(100) No
Phone varchar(100) No
Alt_phone varchar(100) No
Email varchar(100) No
Billno varchar(100) No
Brand varchar(100) No
Model varchar(100) No
Address varchar(500) No

30
description varchar(1000) No
Photo varchar(100) No
Status varchar(100) No
Date varchar(100) No
Time varchar(100) No
Sermenid varchar(100) No

 Indexes

Keyname Type Unique Packed Column Cardinality Collation Null Comment

PRIMARY BTREE YES No tokenno 12 A No

Email BTREE YES No tokenno 12 A NO

31
 User
Interface
Design

32
 9. User interface design
 Login Page

 Token form

33
34
 User History

35
 Search

 Get Information

36
 Admin Homepage

37
 Token Details

38
 Pending Request

 Allocation

39
40
 Serviceman Homepage

 Confirm Request

41
 Sending OTP

 OTP Confirmation

42
43
44
Conclusion

45
 Conclusion
The application works satisfactory. Using it the users can perform the listed function
appropriately. The result of the application is pleasing.
The website gives accurate and desired results in various ways. Overall the performance of
the application is near to perfection. It works according to user's demand.

46
 Dedicated
To

My Beloved Parents
Friends/Colleagues
Teachers

47