A Project Report on

“Desktop Support”
At

“Bhagwan Mahavir College of Computer Application”,

Bharthana-Vesu, Surat
As A Partial Fulfilment for The Degree Of

Bachelor of Science in Information Technology

Infrastructure Management Services

2022-25
Guided By: Submitted By:
Dr. Hetal Modi YashKumar Variya

Bhagwan Mahavir College of Computer Application

Bharthana-Vesu, Surat
Constituent College of

Bhagwan Mahavir University, Surat, Gujarat, India

1
 BHAGWAN MAHAVIR COLLEGE OF COMPUTER APPLICATION
Constituent College of Bhagwan Mahavir University
principal.bmcca@bmusurat.ac.in 0261-6770125/23, +91-7575803091
www.bmusurat.ac.in VIP Road, Surat, Gujarat–395007

PROJECT PROPOSAL
Desktop Support
PROJECT TITLE

YashKumar Variya
SUBMITTED BY SUBMITTED TO

PROGRAM Bsc – IT IMS Contact +91 8849175269

NAME Person Name
PROGRAMMING DATE
LANGUAGE SUBMITTED
FRONT-END BACK-END
TOOLS TOOLS
Are you doing this project for any Industry/Client? (Yes/No):
If Yes, Mention the Name and Address of the Industry or Client
Provide Name, Title, Phone, and Email Address for each stakeholder below.

Project Members Detail

MEMBER NAME ENROLLMENT NUMBER MEMBER CONTACT NO. MEMBER E-Mail

YashKumar Variya 2202020501051 +91 8849175269 Yashvariya1608@gmail.com

Program Coordinator: Is Project Title Approve : Allocated Project Supervisor:

Name & Sign

2
 BHAGWAN MAHAVIR COLLEGE OF COMPUTER APPLICATION
Constituent College of Bhagwan Mahavir University
principal.bmcca@bmusurat.ac.in 0261-6770125/23, +91-7575803091

www.bmusurat.ac.in VIP Road, Surat, Gujarat–395007

Certificate
This is to certify that the summer project entitled “Desktop Support” has been submitted by YashKumar Variya

Enrollment No. 2202020501051 at Bhagwan Mahavir College of Computer Application. As a partial fulfilment

of the requirement for the degree of Bachelor of Computer Application for the academic Year 2022-25.

Place: Surat

Date:

Dr. Hetal Modi Dr. Hetal Modi

(Project Guide, BMCCA) (Program Head)

3
 BHAGWAN MAHAVIR COLLEGE OF COMPUTER APPLICATION
Constituent College of Bhagwan Mahavir University
principal.bmcca@bmusurat.ac.in 0261-6770125/23, +91-7575803091
w www.bmusurat.ac.in VIP Road, Surat, Gujarat–395007

Date: - / /2025

PROJECT PROGRESS REPORT

Desktop Support
PROJECT TITLE

PROJECT GROUP SUPERVISOR

NO NAME
PROGRAMMING PROGRESS REPORT
LANGUAGE NO.
FRONT-END
BACK-END TOOLS
TOOLS
PROGRESS REPORT
From / /2025 to / /2025
DURATION:

Project Members Detail

Sr.
MEMBER NAME
No.
YashKumar Variya
1. .

Task Details

Sr. No. MEMBER NAME TASK COMPLETED

1. YashKumar Variya • Complete Project FrontEnd & BackEnd
• Complete Project Ui Ux Designer Documentation
• Complete Project Designer & Tester
Comment By Supervisor

Next Progress Report Date: / /2025

Is Progress of Project Approved?

Project Supervisor:
Name & Sign

4
 Acknowledgement

The reason of completing the project work successfully is not just our efforts but efforts of many people. The
people, who trusted us, guided us and encouraged us with every means. Guide is a person who provides you the
direction towards success, so I feel great pleasure to express our gratitude to our guides, our faculty members as
well as every person who helped us directly or indirectly with our project.
We are also indebted to our Professor Asst. Prof. Dr. Hetal Modi who provided constant encouragement, support
& valuable guidance before and during our project. It was her effort who led us to this place for project work. Her
guidance and suggestions were valuable.
We are also thankful to our all Faculties Members and specially to Our Principal Dr. Vikram Kaushik , to give us
opportunity to make us this project.
Thank you very much,

Enrollment No. : 2202020501051

Name : YashKumar Variya

5
 Preface

Before Tasking the Project Work for Foundation, It Is Quite Necessary To Have An Exact Idea The Work “Project”.
The Project Consist of Seven Letters Each Letter Has Its Own Significance As Follow.

‘P’ For Planning

‘R’ For Resources
‘O’ For Operation
‘J’ For Joints Efforts
‘E’ For Engineering Function
‘C’ Communication
‘T’ Task Of Working

We Happy to Hand Over This Project To The Bhagwan Mahavir College Of Computer
Application. This project is based on “Desktop Support” .
In a Computer Application studies, the partial training is very important. We can improve theoretical knowledge
by reading and attempting class but it is imperfect without getting partial knowledge.

Being an IT student, we should see every side of technical unit. It performs vital role in developing software and
situation opportunities and problem.

6
 INDEX
Sr.no Topic Page.no

01. Introduction 9

1.1 college profile 9

1.2 project profile 11

02 Literature Review / Background Study 13

2.1 Existing Systems / Technologies 13

2.2 Recent Trends in IT 15
03 System Analysis 16

3.1 scope of project 16

3.2 Problem Defination 18

04 System Design 19

4.1 Architecture Diagram 19

4.2 Data Flow Diagrams (DFD) 21
4.3 Database Design 24

05 Results and Discussion 26

5.1 Output Screens 26

5.2 Performance Evaluation 26
5.3 Limitations of the System 27
06 Conclusion and Future Work 30

7
6.1 Summary 30
6.2 Future Enhancements 30

8
 INTRODUCTION

1.1 College Profile

❖ Bhagwan Mahavir College of Computer Application (BMCCA), Surat

Established: 2008
Affiliation: Bhagwan Mahavir University
Location: New City Light Road, Bharthana-Vesu, Surat, Gujarat
Accreditation: AICTE approved; UGC affiliated; NAAC accreditation in progress
Website: bmusurat.ac.in

❖ Overview

Bhagwan Mahavir College of Computer Application (BMCCA) is a distinguished

private institution in South Gujarat, committed to delivering quality education in
Information Technology and Computer Applications. Since its inception in 2008,
BMCCA has been managed by the Bhagwan Mahavir College Foundation and is
affiliated with Bhagwan Mahavir University. The college boasts a lush green campus
equipped with modern infrastructure, including spacious classrooms, a
comprehensive library, multipurpose halls, and state-of-the-art computer
laboratories. Currently, the college serves approximately 850 students.

❖ Vision
To emerge as a diversified and preferred institution of national and global repute,
fostering holistic development in the domain of Information Technology and
Computer Science.

9
❖ Mission

Emphasize holistic development of students' careers.

Evolve into a diversified and multidisciplinary institution in Computer Applications
and Science.
Cultivate a lifelong learning community.
Maintain a dynamic, agile, and industry-responsive curriculum and teaching
methodology.

❖ Academic Programs

i. Bachelor of Computer Applications (BCA)

ii. M.Sc. in Cyber Security
iii. Integrated Information Technology Programs
iv. Infrastructure & Facilities

10
1.2 Project profile

Technical support analyst/desktop support

Project Title analyst

YashKumar Variya
Submitted by

2202020501051
Enrollment Number

BSC-IT IMS
Course

Bhagwan Mahavir College of Computer

College Name Application, Surat

Bhagwan Mahavir University

University

Dr. Hetal Modi

Guide / Mentor

:-
Project Duration

Programming :-
Languages

Visual Studio Code, MySQL, XAMPP, GitHub

Tools & Technologies

MySQL
Database Used

Windows 10 / Linux
Operating System

To develop a system to manage and streamline

Objective student academic data.

11
12
 Literature review/ Background Study

2.1 Existing Systems / Technologies

In the current digital landscape, various systems and technologies are used
across the IT sector to handle tasks such as data management,
communication, automation, and security. These existing solutions
provide a foundation for innovation but also have limitations that leave
room for improvement.

Examples of Existing Systems:

System Description

Manual Record- Traditional paper-based systems still used in some

Keeping institutions; prone to errors and data loss.

Legacy Software Older desktop-based applications with limited

Applications flexibility, poor UI, and lack of integration.

Spreadsheets Commonly used for small-scale data storage and

(e.g., Excel) processing; lacks automation and security.

ERP Systems

13
Technology Purpose / Usage

MySQL / Oracle For managing relational databases.

PHP / Java / Python For developing web or backend applications.

HTML, CSS, JS For designing and developing user interfaces.

Cloud Platforms (AWS, For scalable hosting, storage, and deployment

Azure) of apps.

Git / GitHub For version control and collaborative software

development.

14
2.2 Recent Trend in Information Technology

Artificial Intelligence (AI) & Widely used in automation, predictive analytics,

Machine Learning (ML) natural language processing, and smart applications.
Enables flexible, scalable, and cost-effective
Cloud Computing infrastructure using platforms like AWS, Microsoft
Azure, and Google Cloud.

Growing focus on data protection, ethical hacking, and

Cybersecurity
secure software development due to rising cyber
Enhancements
threats.

Connects physical devices to the internet, allowing

Internet of Things (IoT) real-time data sharing and automation in homes, cities,
and industries.

Reduces latency by processing data near the source,

Edge Computing improving performance in IoT and real-time
applications.

Combines development and operations for faster

DevOps & Automation deployment, continuous integration (CI/CD), and
better collaboration.

Used for secure, transparent, and decentralized record-

Blockchain Technology keeping, especially in finance and supply chain
management.

15
 System Analysis

3.1 Scope of the Project

➢ The scope of this project defines the boundaries, functionalities, and

objectives of the system to be developed. This project aims to design and
implement a [project title – e.g., Student Management System], which will
streamline and automate tasks that are currently handled manually or
inefficiently.

➢ Key Areas Covered in the Scope:

• Development of a user-friendly interface for users such as administrators, faculty,

and students.
• Implementation of secure login and role-based access control.
• Ability to store, retrieve, and manage data efficiently through a centralized
database.
• Real-time updates and notifications (optional, if applicable).
• Generation of automated reports (e.g., attendance, performance, transactions).
• Support for future scalability and integration with other systems.

➢ Out of Scope (Optional):

• Mobile app development (if not included in this version).
• Integration with third-party APIs (unless specifically part of the current build).
• Multilingual or cross-platform support beyond initial deployment.

16
DIAGRAM :

17
3.2 Problem Definition

➢ In many organizations and institutions, traditional methods of managing

data and processes are still prevalent. These manual systems are often
time-consuming, prone to human error, difficult to manage at scale, and
lack proper security or data integrity. As the volume of data increases,
these limitations become more prominent, leading to inefficiencies,
delays, and inconsistencies in operations.

➢ The core problem addressed by this project is the lack of a centralized,

automated, and user-friendly system that streamlines [insert specific
function, e.g., student records management, inventory tracking,
appointment scheduling, etc.]. The absence of automation and digital
tools leads to redundant work, poor accessibility, and difficulty in
generating meaningful reports or analytics.

➢ Key Issues Identified:

• Manual data entry and tracking, leading to errors and duplication.

• Lack of real-time access to information.
• Inefficient communication between stakeholders (e.g., admin, users,
management).
• No proper data backup, version control, or security measures
• Difficulty in analyzing and reporting information for decision-making

18
 System Design

4.1 Architecture Diagram: Infrastructure Management System

+-------------------------------------------------------+
| **User Interface Layer** |
|-------------------------------------------------------|
| - Admin Portal - IT Staff Dashboard - Clients |
+----------------------------+--------------------------+
|
v
+-------------------------------------------------------+
| **Application Layer** |
|-------------------------------------------------------|
| - Infrastructure Management Platform |
| - Notification/Alert Service |
| - API Integrations (3rd party/cloud tools) |
+----------------------------+--------------------------+
|
v
+-------------------------------------------------------+
| **Data Layer** |
|-------------------------------------------------------|
| - Asset Database - User Information DB |
| - System Logs DB - Configuration Repositories |
+----------------------------+--------------------------+

19
 |
v
+-------------------------------------------------------+
| **Infrastructure Layer** |
|-------------------------------------------------------|
| - Physical Servers - Network Equipment |
| - Storage Systems - Cloud Infrastructure (AWS, Azure) |
+-------------------------------------------------------+

Layer Descriptions:
User Interface Layer:
•

Interfaces for users (admin, IT staff, and clients) to access system features like
monitoring, reporting, or request handling.
Application Layer:
•

Core business logic, infrastructure control, automation scripts, alerting systems, and
APIs that enable third-party integrations.
Data Layer:
•

Centralized repositories for storing assets, user data, logs, and infrastructure
configurations.
Infrastructure Layer:
•

The actual hardware and virtual resources being managed, including servers, storage,
networking devices, and cloud services.

20
4.2 Data Flow Diagrams (DFD) :

21
22
23
4.3 Database Design

➢ The database for the Infrastructure Management System is designed using

a relational model, ensuring efficient data organization, integrity, and
scalability. It contains several core tables that handle essential information
related to users, assets, maintenance activities, and incident reports.

➢ The Users table stores details of all individuals who interact with the
system, including administrators, IT staff, and clients. Each user has a
unique ID, along with attributes such as name, email, role, and an
encrypted password for secure access.

➢ The Assets table maintains records of all infrastructure components like

servers, routers, switches, and other IT equipment. Each asset is identified
by a unique asset ID and includes details such as the asset name, category,
status (e.g., active, under repair), location, and purchase date.

➢ To track system upkeep, the Maintenance table logs all maintenance

activities performed on assets. This table links to both the Assets and Users
tables using foreign keys and stores the date of maintenance, the user
responsible, and remarks regarding the work done.

➢ The Incidents table captures all issues reported related to assets, including
problems such as hardware failure or performance issues. Each incident
includes a unique ID, the related asset and user, a description of the issue,

24
 the status (open, in progress, or closed), and a timestamp of when it was
reported.

➢ These tables are connected through proper relationships to ensure

normalized and consistent data. One user can report or perform multiple
maintenance tasks or incident entries, and each asset can be associated
with many incidents or maintenance logs. This structure provides a robust
foundation for managing IT infrastructure efficiently and reliably.

25
 Results and discussion

5.1 Output Screens

➢ The output screens of the Infrastructure Management System provide a

user-friendly and interactive interface for all user roles—admin, IT staff,
and clients. These screens are designed with clarity and functionality in
mind, ensuring smooth navigation and task execution.

➢ The Login Screen serves as the entry point, where users securely access
the system using their credentials. Based on role-based access, users are
directed to their respective dashboards. The Admin Dashboard provides
an overview of system activity, such as the number of assets, pending
incidents, and recent maintenance logs. It also features quick access
buttons for user management, asset registration, and reports.

➢ The Asset Management Screen allows users to view, add, update, or

deactivate infrastructure assets. It displays information such as asset ID,
name, type, status, and location in a tabular format with search and filter
options.

➢ The Incident Reporting Screen enables users to report issues related to

any asset. It includes fields for selecting the affected asset, describing the
issue, and assigning a priority level.

5.2 Performance evaluation

➢ The performance of the Infrastructure Management System was

evaluated based on several critical parameters such as response time,
system accuracy, resource usage, and user satisfaction. The goal of this
26
 evaluation was to ensure that the system meets operational expectations
under various conditions and workloads.

➢ During testing, the system demonstrated fast response times for typical
operations such as logging in, retrieving asset records, and submitting
incident reports, even when handling a moderate number of concurrent
users. Queries were optimized to ensure that database interactions did
not result in noticeable delays, keeping the average page load time under
2 seconds.

➢ The system also maintained high accuracy in data processing. All form
submissions, updates, and data retrievals were validated both on the
frontend and backend, reducing the risk of data inconsistencies or input
errors. Role-based access control was thoroughly tested to confirm that
users could only access functions relevant to their permissions.

➢ From a resource efficiency standpoint, the system operated within

acceptable CPU and memory usage limits on standard hosting
environments. No significant memory leaks or performance bottlenecks
were identified during stress testing.

5.3 Limitations of the system

➢ While the Infrastructure Management System fulfills its core objectives of

asset tracking, incident management, and maintenance scheduling, it
27
 does have certain limitations that may impact scalability and usability in
larger or more complex environments.

1. Limited Real-Time Monitoring:

The current version does not support real-time infrastructure monitoring
(e.g., live device health checks or usage metrics). It relies on manual
updates or periodic logs, which may delay issue detection.

2. No Mobile Application:
The system is optimized for desktop browsers and lacks a dedicated
mobile application, which limits accessibility for on-the-go users such as
field technicians.

3. Scalability Constraints:
While suitable for small to medium-sized organizations, the system may
require database and backend optimizations to handle larger datasets or
high user traffic efficiently.

4. Lack of Automation:
Routine tasks such as asset deprecation alerts or automated maintenance
reminders are not fully automated and must be manually triggered by
users.

5. Third-Party Integration Limitations:

Integration with third-party tools (e.g., ticketing systems, cloud platforms,
or inventory APIs) is limited or non-existent in the current build.

28
6. Basic Role Management:
The role-based access control is functional but basic. It lacks advanced
permission granularity and audit trails for sensitive operations.

29
 Conclusion and futurework

6.1 Summary

➢ The Infrastructure Management System project was developed to

streamline and digitize the management of IT infrastructure assets,
incidents, and maintenance activities. The system addresses common
challenges faced by organizations, such as manual tracking, inefficient
reporting, and lack of centralized visibility over IT resources.

➢ Through careful analysis, design, and implementation, the system

provides essential features like asset registration, incident reporting,
maintenance logs, and role-based access control. A well-structured
database ensures efficient data handling, while a user-friendly interface
makes the system accessible to administrators, IT staff, and clients.

➢ Performance evaluation confirmed that the system operates effectively

under typical workloads, with fast response times and accurate data
handling. However, some limitations were identified, including the lack of
real-time monitoring, mobile access, and advanced integrations.

6.2 Future Enhancements

➢ While the current version of the Infrastructure Management System

meets its basic requirements, several enhancements can be implemented
in future versions to increase its functionality, efficiency, and scalability.

30
1. Real-Time Monitoring Integration:
Incorporating real-time monitoring tools for network devices and servers
would allow the system to detect failures or performance issues instantly,
enabling faster response times.

2. Mobile Application Support:

Developing a cross-platform mobile application would improve
accessibility for field technicians and staff who require on-the-go access to
system features.

3. Automated Alerts & Notifications:

Implementing automated email or SMS alerts for asset

4. Advanced Analytics & Reporting:

Adding dashboards and visual analytics for performance metrics, asset
usage trends, and incident frequency would help management make data-
driven decisions.

5. Integration with External Systems:

Future versions could support integration with help desk tools, cloud
service providers, and inventory management systems for a more cohesive
IT ecosystem.

31
6. Improved Security Features:
Enhancing user authentication methods with multi-factor authentication
(MFA) and audit trails for user activities would provide greater system
security.

7. Scalability for Large Enterprises:

Optimizing the system architecture to handle large data volumes and
concurrent users would make it suitable for enterprise-level deployments.

32