Contents

1 Chapter 5
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1.2 Problem Statement . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.1 Customized Task Plans . . . . . . . . . . . . . . . . . . 6
1.3.2 User Privacy and Security . . . . . . . . . . . . . . . . 6
1.3.3 Resource Hub . . . . . . . . . . . . . . . . . . . . . . . 6
1.3.4 Collaboration with Task Professionals . . . . . . . . . . 7
1.3.5 Community Support . . . . . . . . . . . . . . . . . . . 7
1.4 Aims and Objectives . . . . . . . . . . . . . . . . . . . . . . . 7
1.4.1 Objectives . . . . . . . . . . . . . . . . . . . . . . . . . 7
1.5 Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
1.6 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.6.1 Admin Panel . . . . . . . . . . . . . . . . . . . . . . . 9
1.6.2 Company Admin Panel . . . . . . . . . . . . . . . . . 10
1.6.3 Employee panel . . . . . . . . . . . . . . . . . . . . . . 11
1.7 Definition,Acronyms and Abbreviations . . . . . . . . . . . . . 12
1.7.1 Visual Studio . . . . . . . . . . . . . . . . . . . . . . . 12
1.7.2 SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.8 Server Used: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.8.1 SQL Server: . . . . . . . . . . . . . . . . . . . . . . . . 13
1.9 Web Service: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.10 Usage Scenarios: . . . . . . . . . . . . . . . . . . . . . . . . . 15
1.11 Functional Non-Functional Requirements: . . . . . . . . . . . 15
1.11.1 Functional Requirements: . . . . . . . . . . . . . . . . 15
1.11.2 Authentication: . . . . . . . . . . . . . . . . . . . . . . 15
1.11.3 Authorization: . . . . . . . . . . . . . . . . . . . . . . . 15

1
 1.11.4 Process Data: . . . . . . . . . . . . . . . . . . . . . . . 16
1.11.5 Recruitment: . . . . . . . . . . . . . . . . . . . . . . . 16
1.11.6 Attendance: . . . . . . . . . . . . . . . . . . . . . . . . 16
1.11.7 Company Admin Profile Management: . . . . . . . . . 16
1.11.8 Admin Panel: . . . . . . . . . . . . . . . . . . . . . . . 17
1.12 Non-Functional Requirements: . . . . . . . . . . . . . . . . . . 18
1.12.1 Hardware Requirements: . . . . . . . . . . . . . . . . . 18
1.12.2 Software requirements: . . . . . . . . . . . . . . . . . . 18
1.12.3 Performance Requirements: . . . . . . . . . . . . . . . 18
1.12.4 Response Time: . . . . . . . . . . . . . . . . . . . . . . 18
1.12.5 Workload: . . . . . . . . . . . . . . . . . . . . . . . . . 19

2 Chapter 20
2.1 Literature Review . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.2 Purpose: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.2.1 Available Methodology: . . . . . . . . . . . . . . . . . 21
2.2.2 Chosen Methodology and Reason: . . . . . . . . . . . . 22
2.3 Project Plan: . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.4 Project Planning Includes: . . . . . . . . . . . . . . . . . . . . 23
2.4.1 Risk Planning: . . . . . . . . . . . . . . . . . . . . . . 23
2.4.2 Project Scheduling: . . . . . . . . . . . . . . . . . . . . 24
2.5 Project Structure: . . . . . . . . . . . . . . . . . . . . . . . . . 25

3 Chapter 26
3.1 Development Plan: . . . . . . . . . . . . . . . . . . . . . . . . 26
3.1.1 Project Managers: . . . . . . . . . . . . . . . . . . . . 26
3.1.2 Practitioners: . . . . . . . . . . . . . . . . . . . . . . . 26
3.1.3 End Users: . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.1.4 Product: . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2
4 Chapter 27
4.1 Introduction: . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.2 Purpose: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.3 Scope: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
4.3.1 Admin Panel: . . . . . . . . . . . . . . . . . . . . . . . 28
4.3.2 Company Admin Panel: . . . . . . . . . . . . . . . . . 28
4.3.3 Employee Panel: . . . . . . . . . . . . . . . . . . . . . 28
4.4 Use Cases: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.4.1 Admin: . . . . . . . . . . . . . . . . . . . . . . . . . . 29
4.4.2 Company Admin: . . . . . . . . . . . . . . . . . . . . . 30
4.4.3 Employee: . . . . . . . . . . . . . . . . . . . . . . . . . 31
4.5 Abbreviations, acronyms, and definitions: . . . . . . . . . . . . 32
4.5.1 Visual studio: . . . . . . . . . . . . . . . . . . . . . . . 32
4.5.2 SQL: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
4.6 Server Used: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
4.6.1 SQL Server: . . . . . . . . . . . . . . . . . . . . . . . . 33
4.7 Web Service: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
4.8 Data flow Diagram: . . . . . . . . . . . . . . . . . . . . . . . . 35
4.9 Dynamic Model: . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.9.1 ER Diagrams: . . . . . . . . . . . . . . . . . . . . . . . 36
4.10 Graphical User Interface: . . . . . . . . . . . . . . . . . . . . . 36
4.10.1 Login Page: . . . . . . . . . . . . . . . . . . . . . . . . 37
4.10.2 Dashboard: . . . . . . . . . . . . . . . . . . . . . . . . 38
4.10.3 Employee Role: . . . . . . . . . . . . . . . . . . . . . . 39
4.10.4 Manage Task: . . . . . . . . . . . . . . . . . . . . . . . 40
4.11 Company Admin: . . . . . . . . . . . . . . . . . . . . . . . . . 41
4.11.1 Dashboard: . . . . . . . . . . . . . . . . . . . . . . . . 41
4.11.2 Add New Company: . . . . . . . . . . . . . . . . . . . 42
4.11.3 Manage Branches: . . . . . . . . . . . . . . . . . . . . 43

3
 4.11.4 Mark Attendance: . . . . . . . . . . . . . . . . . . . . . 44
4.11.5 View Attendance: . . . . . . . . . . . . . . . . . . . . . 45
4.11.6 Manage company Admins: . . . . . . . . . . . . . . . . 46

5 Chapter 47
5.1 Conclusions: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.2 Future Work: . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.2.1 Chat Box: . . . . . . . . . . . . . . . . . . . . . . . . . 47
5.3 References: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

4
1 Chapter
1.1 Introduction
Everything is digitized in the ever-developing technological world of today.
The wide range of employment possibilities has led to an increase in the
human workforce. A system that can manage the data of so many personnel
and their roles inside a business is therefore needed. The user-friendliness of
this project makes keeping records easier task.
To overcome the issues that existed with the traditional manual approach,
we devised this system. These tools support teams and individuals in main-
taining organization, setting priorities, and meeting deadlines. As a result,
production rises since everyone is aware of what has to be done when. The
software makes it simple for the employer to maintain a record of every docu-
ment. The administrator can keep track of all the employees and departments
thanks to this program. Every employee in the database has a position that
may be added to or changed as needed.
The modules’ integration into a single application allows the creation
of the best framework for re-engineering and integrating business objectives
with human resource practices. The project’s goal is to develop an task man-
agement system that will fill existing gaps in the electronic administration of
employees’ activities.
In this Chapter we’ll see:

1. Introduction

2. Problem Statement

3. Purpose

4. Scope

5. Definitions, acronyms and abbreviations

6. Use cases and usage scenarios

7. Use case diagrams

8. Supplementary Requirements

9. Usability

10. Reliability

5
 11. Supportability

12. System Requirements

1.2 Problem Statement

Our organization’s existing task management procedures rely on manual
techniques [3]. It’s important to note that this takes time, and that using
paperwork to manage some of these procedures might result in human errors
if the paperwork ends up in the wrong hands. A few of the present systems
also don’t have employee self-service, which prevents workers from accessing
and controlling their personal data.

1.3 Purpose
The Task Management System’s mission is to revolutionize how individ-
uals organize and oversee their tasks while raising awareness of effective task
management techniques and promoting proactive productivity. Users of this
advanced digital platform can utilize it as a comprehensive tool to gain bet-
ter control over their tasks, identify trends in their work patterns, and make
informed decisions that enhance their efficiency and overall quality of work.
1.3.1 Customized Task Plans
The Task Management System generates personalized task management
plans based on the data it collects and analyzes. These plans incorporate
research-backed strategies and activities tailored to each user’s specific needs
and work preferences. To support professional well-being, these strategies
include task prioritization techniques, time management methods, and work-
flow optimization approaches.
1.3.2 User Privacy and Security
The system employs state-of-the-art encryption and strictly adheres to
privacy regulations to ensure maximum data protection and confidentiality.
Users can trust that their personal information is safeguarded, fostering a
secure environment that encourages open and honest task reporting.
1.3.3 Resource Hub
The platform functions as a comprehensive resource center, providing ac-
cess to a wealth of informative articles, books, and resources on various task
management-related subjects. The system aims to reduce the stigma associ-
ated with poor task management and enhance task management literacy by
offering reliable information.

6
1.3.4 Collaboration with Task Professionals
Through the system, task management experts can interact with their
clients and access vital information that enables more personalized and in-
formed task management strategies. This collaboration between users and
experts promotes a holistic approach to task management and increased pro-
ductivity.
1.3.5 Community Support
The platform facilitates connections among users who are facing similar
task management challenges. Through secure and monitored forums, users
can share their experiences, seek advice, and find support in their quest for
improved productivity and effective task management.

1.4 Aims and Objectives

To develop an effective and user-friendly task management system that
empowers individuals to streamline their work processes, enhance productiv-
ity, and promote a balanced work-life dynamic.
1.4.1 Objectives
• Conduct Needs Analysis Perform a comprehensive needs analysis to
identify the specific challenges individuals face in managing their tasks.
This analysis will consider factors such as work environments, individ-
ual preferences, and unique requirements for different professions.

• Experts Partner with task management experts, productivity coaches,

and workplace professionals to ensure that the system’s features and
content adhere to best practices and address the identified needs effec-
tively.

• Create an intuitive and aesthetically pleasing user interface. Take into

account factors like ease of use, adaptability to different work contexts,
and readability, ensuring the system caters to a broad range of users.

• Interactive Resources Develop a variety of interactive resources, in-

cluding task prioritization tools, time management techniques, and
workflow optimization guides. These resources should support users
in enhancing their work efficiency and productivity.

• Implement robust security measures to safeguard users’ sensitive task-

related information. Ensure that the system provides a secure and
reliable online environment for managing tasks and sensitive work data.

7
 • Conduct usability testing with users from various professional back-
grounds to gather their feedback on the system’s design, functionality,
and the relevance of its content to their work requirements.

• Use data analysis and feedback from users to assess the system’s ef-
fectiveness in improving work efficiency, task management skills, and
overall work performance. Regularly measure and track outcomes.

• Continuously update and expand the system’s features and content

based on emerging trends and best practices in the field of task man-
agement and workplace productivity. Ensure that the system remains
relevant and effective in addressing evolving needs.

1.5 Scope
• Users can create tasks, assign them to themselves or other team mem-
bers. Tasks may include deadlines, priorities, and descriptions.

• Users can categorize and group tasks by projects, teams, or due dates.

• Ability to set task dependencies to show relationships between tasks.

• Notifications and reminders for upcoming or overdue tasks.

• Visual progress indicators, such as task completion percentages.

• Team members can comment, discuss, and collaborate on tasks.

• Integration with communication tools (e.g., chat or email) for task-

related discussions.

• Ability to attach files, documents, or links to tasks for reference.

• Centralized storage for project-related documents.

• Synchronization with calendars for task due dates and appointments.

• The ability to view tasks on a shared team calendar.

• Generate reports on task progress, completion rates, and team per-

formance. Analyze historical task data for performance improvement.
User Access and Permissions:

• Role-based access control to define who can create, edit, or delete tasks.

• Privacy settings for tasks that need to remain confidential.

8
 • Mobile applications or responsive web design for on-the-go task man-
agement.

• Integration with other software and platforms (e.g., email, project man-
agement, CRM, or document sharing tools).

• Secure storage and encryption of task data. Compliance with data

protection laws and regulations.

• Training resources and user support for system adoption.

• Assistance with technical issues and questions.

• Ability to scale the system to accommodate growing teams and projects.

Customization options to adapt the system to specific workflow require-
ments.

• Mechanisms for users to provide feedback and suggest improvements.

• Regular updates and enhancements based on user needs. Ethical Con-

siderations:

• Adherence to ethical standards regarding data privacy and user con-

sent.

1.6 Module
Our Web Based interface is divided into three parts:

1. Admin Panel

2. Company Admin Panel

3. Employee Panel

1.6.1 Admin Panel

• Admin can add or delete the company.

• Admin can add or delete the company admin.

• Admin manage the system and databases.

• Admin can update his profile.

9
 An administrator, often referred to as ”admin,” holds a pivotal role in
the management of a system, particularly when it comes to a company’s
operations and databases. This role encompasses several critical responsibil-
ities. Firstly, admins have the authority to add or delete companies within
the system, which is essential for maintaining an up-to-date and organized
database of companies that the system serves. Additionally, admins can also
add or remove company administrators, allowing them to control access and
permissions for various stakeholders within each company.
One of the core functions of an admin is to manage the system and its
databases efficiently. This involves overseeing the performance, security, and
functionality of the system, ensuring that it operates smoothly and securely.
Admins are responsible for regular system maintenance, troubleshooting is-
sues, and implementing necessary updates to keep the system up to date
with the latest features and security measures.
Furthermore, admins have the privilege to update their own profiles,
which is essential for keeping their contact information, credentials, and ac-
cess privileges accurate and current. This not only helps in maintaining the
integrity and security of the system but also allows them to communicate
effectively within the organization.
In summary, an admin plays a crucial role in the administration and
maintenance of a system, with the authority to manage companies, company
admins, and the system’s databases, while also ensuring their own profile
information is up-to-date. This combination of responsibilities is vital for
the smooth and efficient operation of the system, as well as for maintaining
the security and integrity of the data it manages.
1.6.2 Company Admin Panel
• Company Admin can add, remove and add employees.

• Company Admin can assign the task to the employee.

• Company Admin manages the Attendance of employees.

• Company Admin can view attendance reports of employees.

• Company Admin can view and update role of each employee.

• Company admin can view the report of each task given to the employee.

In a company, the role of the Company Admin is crucial for oversee-

ing various administrative tasks and ensuring the efficient operation of the

10
organization. The Company Admin holds the authority to add, remove,
and manage employees within the company, thereby being responsible for
maintaining an up-to-date employee roster. This includes adding new hires,
removing employees who have left the company, and updating employee in-
formation as needed.
Additionally, the Company Admin is in charge of task management. They
have the ability to assign tasks to employees, which is essential for distribut-
ing responsibilities and ensuring that work is allocated effectively. The Ad-
min can also monitor the progress and completion of these tasks to maintain
productivity and accountability.
Attendance management is another crucial responsibility of the Company
Admin. They keep track of employees’ attendance, making sure that they
are punctual and adhere to the company’s attendance policies. This involves
recording employee arrivals, departures, and any leave requests.
Furthermore, the Company Admin can generate attendance reports for
employees. These reports provide insights into attendance patterns, helping
to identify and address attendance issues or trends within the company.
Role management is another significant aspect of the Company Admin’s
responsibilities. They have the authority to view and update the roles and
permissions of each employee within the organization. This ensures that em-
ployees have the appropriate access to company resources and responsibilities
based on their job functions and hierarchy.
Lastly, the Company Admin has access to task reports, allowing them
to evaluate the progress and status of tasks assigned to employees. This
feature enables the Admin to monitor the overall performance and efficiency
of the workforce, making data-driven decisions to improve productivity and
outcomes.
In summary, the Company Admin plays a vital role in managing employee
data, task distribution, attendance, role assignments, and task performance
within the organization, contributing to the smooth and effective functioning
of the company.
1.6.3 Employee panel
• Employee has access to and control over his personal data.

• Employee can update the report of the task.

• Employee can view his attendance report. Employee can update his
password

11
Ensuring that employees have access to and control over their personal data
is a fundamental aspect of data privacy and security within any organiza-
tion. This empowers individuals and safeguards their privacy rights. When
an employee has the ability to update the report of the tasks they’ve com-
pleted, it promotes transparency and accountability. They can reflect the
most accurate and up-to-date information regarding their work, fostering
better communication and trust within the company.
Furthermore, allowing employees to view their attendance reports grants
them insight into their own work patterns and attendance records, which can
be valuable for personal and professional development. It can also help in
addressing any attendance-related issues promptly.
Empowering employees to update their own passwords is crucial for data
security. This self-service approach reduces the risk of unauthorized access
to their accounts and sensitive information. Employees can regularly change
their passwords, enhancing the overall cybersecurity of the organization. It
also reduces the administrative burden on IT departments and helps main-
tain the integrity of the organization’s data. In sum, providing employees
with access to their personal data, the ability to update task reports, view
attendance records, and change their passwords not only promotes trans-
parency and accountability but also strengthens data privacy and security
while improving overall organizational efficiency.
1.7 Definition,Acronyms and Abbreviations
The definitions, acronyms and abbreviations of each tool we are going to
use is as follows:
1.7.1 Visual Studio
Visual Studio is an integrated development environment (IDE), while
Visual Studio Code is a rich text editor akin to Atom. The IDE and text
editor are only one example of how the apps differ from one another. An
IDE is a useful tool for writing, editing, debugging, and executing your code.
The features of Visual Studio can vary depending on the edition and
version, but some common features include:

• Strong debugging tools that help you create breakpoints, check vari-
ables, walk through code, and identify problems in your program.
• A sophisticated code editor with syntax highlighting, code completion,
and Intelligence.
• With the numerous customization possibilities offered by Visual Studio,

12
 developers may add custom plugins, themes, and extensions to their
development environment. preferences particular to a project

• Built-in support for version control systems like Git, enabling seamless
collaboration and source code management.

1.7.2 SQL
Structured query language is a special-purpose language used for manag-
ing data stored in relational database management systems (RDBMS) or for
stream processing in relational data stream management systems (RDSMS).
The three languages that make up SQL are data definition, data manip-
ulation, and data control. Relational algebra and tuple relational calculus
served as its foundation at first. The range of SQL includes data access
control, schema creation and modification, data entry, query, update, and
deletion. Despite being primarily a declarative language, as it is commonly
called, SQL also has procedural elements.
One of the earliest commercial languages for the relational model was
SQI, which was introduced by Edgar F. Codd in his seminal 1970 paper,
”A Relational Model of Data for Large Shared Data Banks.” Despite not
entirely adhering to Codd’s relational model, the most widely used database
language.
SQL was accepted as a standard by the American National Standards
Institute (ANSI) in 1986 and the International Organization for Standard-
ization (ISO) in 1987. Since then, the standard has expanded to provide a
greater variety of functions. Even though there are such standards, most SQL
code has to be modified in order to work correctly across different database
systems.

1.8 Server Used:

1.8.1 SQL Server:
The public release of SQL Server 2005 (formerly known as ”Yukon”) took
place in November 2005. It included native support for XML data in addition
to managing relational data. This is why it added an xml data type that
could be used in database columns or as a literal in queries. Any XML
data being stored is validated using the XSD schema, which may be coupled
to XML columns. XML is converted into an internal binary data format
before being saved in the database. Specialized indexing methods are now
available for XML data. In order to allow XQuery queries to be incorporated
in T-SQL, SQL Server 2005 made certain changes to the T-SQL language.

13
XQuery is used to query XML data.
The new XQuery extension XML DML, which enables query-based up-
dates to XML data, is also introduced. SQL Server 2005 also makes it pos-
sible to contact a database server using web services by using Tabular Data
Stream (TDS) packets encased in SOAP (protocol) requests. Online services
utilized to retrieve the data supplied their findings as XML.
Now that Common Language Runtime (CLR) integration is available,
SQL code that is controlled by the CLR may be written. T-SQL for relational
data now supports CTES (Common Table Expressions) for recursive queries
and try/catch error management. New indexing methods, better syntax, and
enhanced error recovery mechanisms are among improvements in SQL Server
2005.
Data pages are check-summed for increased error resistance, and opti-
mistic concurrency support has been added for better performance. The
query processor now efficiently controls concurrent query execution and has
implemented more precise access control and permissions. Because table and
index partitions are supported by default, scaling out a database onto a clus-
ter is considerably easier. SQL CLR was initially made available with SQL
Server 2005 in order to facilitate integration with the.NET Framework.
Microsoft created the relational database management system known as
Microsoft SQL Server. It is a piece of software known as a database server,
and its primary function is to store and retrieve data when other software
applications require it. These applications may run on a different computer
or on the same one. For different clienteles, Microsoft offers at least a dozen
different editions of SQL Server. These editions can handle workloads ranging
from small single-machine systems to massive Internet-facing programs with
many concurrent users. We utilized a few more tools for graphic design that
weren’t included in the online interface.
1.9 Web Service:
Any piece of software that uses a recognized XML message protocol and
makes itself available online is considered a web service. XML is used to
encrypt all conversations with a web service [2]. Since web services are inde-
pendent of any specific operating system or computer language, a client can,
for example, contact a web service by sending an XML message and then
waiting for an XML response. Windows programs can connect with UNIX
programs, and Java and Perl can converse.
Web services are self-contained, modular, distributed, dynamic applica-

14
tions that may be described, published, located, or accessed across a network
in supply chains and corporate activities. These programs may be broadcast,
local, or available online. On top of open standards like TCP/IP, HTTP,
Java, HTML, and XML, web services are constructed. Direct application-
to-application communication via the Internet is made possible through web
services, which are XML-based platforms for information sharing. These
systems might be composed of words, objects, communications, or software.

1.10 Usage Scenarios:

Employees must first authenticate themselves in the program by using the
correct login or authentication mechanism. After that, he or she will be able
to view all of the amenities that meet both our functional and non-functional
application requirements.
Numerous modules, including Branch management, role management,
user management, task and attendance, will be visible to the user once he
has successfully authenticated. If he holds the position of company admin,
he can oversee the entire branch, view the roles of the company’s employees
who work for him, manage their profile information, assign tasks based on
their areas of expertise, and control their attendance.
Following are some functional and non-functional requirements related to
our project.

1.11 Functional Non-Functional Requirements:

1.11.1 Functional Requirements:
1.11.2 Authentication:
• Login: The user’s username and password are required to access the
TMS system.

• The user has the option to log out of the TMS system.

• Failure to login can occur if the user is not found in the database or if
the user enters the incorrect username or password.

1.11.3 Authorization:
• User role check: After logging in, the database will be queried to de-
termine the user’s role, and the user interface will then be shown ap-
propriately.

15
1.11.4 Process Data:
• Display: Users with particular responsibilities can access database con-
tent. To be more exact, the employee can only look at his or her per-
sonal information. All employees’ personal and professional data are
accessible to the admin.

• Edit: Users who have the employee position are unable to change their
personal data. Employees’ personal and professional information can
only be edited by admins. All employee-related information, including
the user role type, is editable by the admin.

• Search: The database’s content may be searched for by the company

admin role. The database of all the employees’ information is search-
able by the company admin. For instance, HR is looking for staff with
”Team Work” skills or who are permanent. After precisely entering
the term in the search area, he or she will click the appropriate search
button. Next, he or she will get a list of all employees with the ”Team
Work” competency or who are permanent employees.

• Update Role: This capability is only available to people that have the
admin role type. The administrator can modify the role type associ-
ated with a certain user. An employee who receives a promotion, for
instance, will see a change in his position type from assistant professor
to associate professor. The administrator may make changes to this
employee job.

1.11.5 Recruitment:
New employee addition: The firm administrator has the option of adding
a new employee to the database. The new worker will have access to all the
required personal information about them. An ID will be supplied to a new
employee. The unique ID will be provided by the system.
1.11.6 Attendance:
Mark attendance:A worker may log his attendance. The employee’s at-
tendance report is accessible to company administrators.
1.11.7 Company Admin Profile Management:
• Add new company Admin: A new business admin may be added by
admin. A newly established admin will have the same rights and re-
sponsibilities as its parent, but it cannot change or remove its parent
or another admin. Only its child admins are editable or erasable.

16
 • Edit Profile: Its own email address is editable by admin. Its password
can also be modified. Only once admin has entered their password and
authenticated themselves will these two modifications take effect.

1.11.8 Admin Panel:

• Admin can add or delete the company.

• Admin can add or delete the company admin.

• Admin manage the system and databases.

• Admin can update his profile.

An admin, short for administrator, plays a critical role in managing
various aspects of a system or organization. In the context of your
description, it appears that the admin has several important responsi-
bilities.
Firstly, the admin has the authority to add or delete companies within
the system. This means that they have the power to onboard new com-
panies or remove existing ones, which can be pivotal for maintaining
an up-to-date and relevant database of companies.
Secondly, the admin also has the capability to add or delete company
admins. This implies that they can assign or revoke administrative
privileges to individuals associated with the companies. This control
is essential for ensuring that the right people have access to and can
make decisions about the company’s data and settings.
Furthermore, the admin is responsible for managing the overall system
and its databases. This involves tasks like ensuring the system’s func-
tionality, optimizing its performance, and safeguarding the integrity
and security of the databases. The admin may also handle routine
maintenance, backups, and troubleshooting issues to keep the system
running smoothly.
Lastly, the admin can update their own profile. This is important
for maintaining accurate and relevant information about the person
responsible for system administration. It helps in ensuring that contact
details and access credentials for the admin are up to date, which is
vital for communication and security.
In summary, an admin has a range of crucial responsibilities, including
overseeing companies and their administrators, managing the system
and databases, and maintaining their own profile information. These

17
 functions are essential for the effective and secure operation of the
system.

1.12 Non-Functional Requirements:

1.12.1 Hardware Requirements:
T MS should be able to operate on a machine with the bare minimum of
the following hardware.
Specifications:

• OS: Windows 10 pro

• CPU: Intel core i5 4th gen
• Memory: 16GB and above
• Capacity: 8GB of hard drive
• Others: Mouse, keyboard, network interface card, and monitor.

1.12.2 Software requirements:

A web connection must be created because the TMS application is web-
based. The SQL environment will be supported by TMS software’s personal
database model (DBMS).
1.12.3 Performance Requirements:
In order to assess the performance of a system the following must be
clearly specified:
1.12.4 Response Time:
If it takes less than 0.5 seconds, the user can identify the system as
reacting instantaneously; in this instance, just the result must be marked.
Although the user will be aware of the delay, their uninterrupted mental
process can only last for so long. When delays of more than 0.1 but less than
1.0 second occur, the user does lose the mark sling of directly acting on the
data, but frequently no special mark back is needed. About 10 seconds is
the best length of time to keep the user’s attention on the discussion.
Users should be given marks back that indicate when the computer ex-
pects being completed since they will want to accomplish other tasks while
they wait for the computer to finish lengthy delays. Marking back during the
wait is especially important if the response time is going to be very variable
because customers won’t know what to expect.

18
1.12.5 Workload:
The performance of the system is influenced by how the load is allocated
to it. For instance, it is easier to achieve faster reaction times for a system
that gets constant task arrivals throughout the day as opposed to one that
has spikes of traffic. Despite being able to handle 10,000 read transactions
per hour, this database system can only handle 3,000 update transactions.

19
2 Chapter
2.1 Literature Review
A literature review on task management systems provides an overview of
research, trends, and key findings related to this topic. Task management
systems are crucial in various domains, including project management, per-
sonal productivity, and team collaboration. Here is a summary of some key
points from the literature on task management systems:

1. Definition and Types of Task Management Systems:

Task management systems are software tools or platforms designed to
help individuals and teams plan, track, and execute tasks and projects
efficiently. They can range from simple to-do lists to complex project
management software. Common examples include Trello, Asana, Mi-
crosoft Project, and JIRA.

2. Benefits of Task Management Systems:

Improved organization and time management: Task management sys-
tems help users structure their work, set priorities, and meet dead-
lines. Enhanced collaboration: These systems often enable real-time
collaboration, making it easier for teams to work together on tasks and
projects. Visibility and accountability: They provide a clear overview
of tasks and their progress, increasing accountability among team mem-
bers.

3. Challenges and Issues:

User adoption: Some research highlights the challenges of getting users
to adopt task management systems consistently, as resistance to change
is common. Complexity: In some cases, the complexity of advanced
task management systems may lead to confusion rather than clarity. In-
tegration: Ensuring that these systems integrate seamlessly with other
tools used in an organization can be a challenge.

4. Task Management in Specific Domains:

Project management: Task management systems are often used in
project management to plan and track tasks, allocate resources, and
manage dependencies. Personal productivity: Individuals use these
systems to manage their daily tasks and improve personal productivity.
Team collaboration: In a team context, these systems help distribute
tasks, monitor progress, and facilitate communication.

20
 5. Emerging Trends:
Mobile accessibility: Many task management systems now offer mobile
apps, making it easier for users to manage tasks on the go. Integration
with AI and automation: Some systems incorporate AI and automation
features to assist users in task prioritization and scheduling. Data
analytics: Task management systems are increasingly incorporating
data analytics to provide insights into task completion patterns and
productivity.

6. Research Gaps:
Some areas that require further research include the impact of task
management systems on stress levels, the adoption of these systems in
specific industries, and the effectiveness of AI-driven task management.

2.2 Purpose:
Everything is digitized in the ever-developing technological world of today.
The wide range of employment possibilities has led to an increase in the
human workforce. A system that can manage the data of so many personnel
and their roles inside a business is therefore needed. The user-friendliness of
this project makes keeping records easier task.
To overcome the issues that existed with the traditional manual approach,
we devised this system. These tools support teams and individuals in main-
taining organization, setting priorities, and meeting deadlines. As a result,
production rises since everyone is aware of what has to be done when. The
software makes it simple for the employer to maintain a record of every docu-
ment. The administrator can keep track of all the employees and departments
thanks to this program. Each employee in the database has a role that may
be expanded upon or altered as necessary.
The integration of the modules into a single application guarantees the
ideal framework for re-engineering and coordinating corporate goals with
human resource procedures. In order to close current gaps in the electronic
administration of workers’ tasks, the project’s objective is to design and
construct an employee management system.
2.2.1 Available Methodology:
Although the creation of thorough management systems is relatively new,
the notion of using computers as a resource management system is not.
Early uses of individualized, electronic training were referred to by terms like
computer-based instruction (CBI), computer-assisted instruction (CAL), and

21
computer-assisted management (CAM). A computer-based management sys-
tem’s primary components in its early phases were computerization and little
tracking assistance. The capacity to effectively implement a management sys-
tem for controlling and integrating organizational management enhanced the
system’s overall functionality with advances in software infrastructure.
2.2.2 Chosen Methodology and Reason:
The spiral development model is being used in our project because of
its risk-driven methodology. We use the spiral model as model generators
for software projects to customize a team’s strategy based on the unique
risk patterns of each project. Integrating components from other process
models, such as incremental, waterfall, or evolutionary prototyping, may be
necessary to achieve this. Thanks to the risk-driven sub configuration of
its phases, the spiral model is adaptable enough to accept an appropriate
mix of specification-oriented, prototype-oriented, simulation-oriented, auto-
mated transformation-oriented, or other software development approaches.In
essence, the spiral is a series of gradual phases that resemble a cascade, in
which all project operations follow a single spiral pattern.
2.3 Project Plan:
Project planning is the cornerstone of what all project managers do, re-
gardless of the industry, the kind of project, or the project manager’s level
of expertise. The main goal of a project plan is to lay out your approach and
the process your team will use to manage the project in accordance with its
scope. Every project needs a strategy since it not only keeps teams account-
able for scope and timeframes but also communicates critical information
to all project stakeholders. It can and will be considered as crucial to the
success of your project if you approach it as more than just a dry document
and express that component of it differently to everyone involved. An actual
plan encompasses more than just dates. You don’t want it to seem like a
tall tale as it is the story of your project! There are elements that make this
narrative good, just like any well-written story.
What are the major deliverables?

• How will we meet the timeline and those deliverables?

• Which members of the project team will be responsible for which de-
liverables?

• Who is on the project team and what role will they play in those
deliverables?

22
 • When will the team reach its milestones, and when will the other team
members help produce those deliverables or give feedback on them?

• If your project logistics are explained in your strategy and your team
and clients are informed,

• You are developing a workable, strategic game plan for your undertak-
ing. It sounds as though you’ve created a piece of fiction. After you’ve
made your strategy, use those questions as a gut check and continue
reading. You may take a few actions to make sure that your project
plan is remembered for being well-written and on course.

2.4 Project Planning Includes:

1. Risk Planning

2. Project Scheduling

2.4.1 Risk Planning:

Risk management is a crucial aspect of project management. Even though
they are frequently ignored, project risks must be identified in order to plan
for the worst-case scenario.
Here are a few instances of typical project risks:

• Too optimistic a time and cost estimate

• Too long between customer reviews and mark backs

• Unexpected cutbacks to the budget

• Roles and duties are unclear

• No stakeholder feedback was gathered.

• Not adequately grasping the demands of stakeholders

• Stakeholders changing project specs after it has started Stakeholders

adding additional requirements after the project has started.

• Poor communication causes misunderstandings, quality problems, and

redos.

23
 • To record hazards, you can utilize a straightforward risk notebook. In
your risk record, note what you’ll do for each risk you’ve identified,
including what you’ll do to avoid it if it does.

• Happening. Regularly review your risk record and add new hazards
as they materialize during the course of the project. Remember that
hazards don’t go away if you ignore them.

2.4.2 Project Scheduling:

• Make a list of the duties that need to be fulfilled in order to complete
each designated deliverable.

• For each task determine the following:

• The time (in hours or days) required to complete the project

• The agent or object that will carry out the action

Once you have established how much effort is required for each assign-
ment, you may calculate the effort required for each deliverable and choose
a suitable delivery date. To your deliverables box, add the more precise
delivery dates.
At this point in the planning phase, you could choose to create your
project schedule using a tool like Microsoft Project. Alternately, pick one of
the many available free templates. Add each deliverable, task, due date, and
resource required to complete it.
[4] When the Sponsor enforces a delivery timeframe that is too tight based
on your forecasts, problems frequently occur at this stage. If you realize this
is the case, you must immediately contact the sponsor.
The options you have in this situation are:

• Renegotiate the deadline (project delay)

• Employ additional resources (increased cost)

• Reduce the project’s scope (provide fewer services)

• Used the project schedule to justify pursuing one of these options.

24
2.5 Project Structure:
A graphical depiction known as an organization chart, which creates au-
thority, defines the structure. Since it shows where each employee belongs
inside the project’s framework, a well-designed project organization chart is
essential for project success.
Because this step includes determining data sources and the kind and
type of accessible data, its importance becomes clear. Understanding the
data at hand and its sources makes it easier to develop the System while
taking into consideration all pertinent elements. The design of the system
also makes sure that it is user-friendly, accommodating their demands, and
comfortable for them.
Designing a system that functions well and produces the desired out-
put within the allotted time frames is another crucial aim. Data security
and dependability cannot be ignored. This is because the system’s security
mechanisms are effectively and efficiently addressed throughout the system
design process.

25
3 Chapter
3.1 Development Plan:
Development plan depends on following key features:
3.1.1 Project Managers:
The project manager is also the project’s supervisor. He is in charge of
providing us with the issue definition, the institution’s requirements, and all
other information required to finish our project.
3.1.2 Practitioners:
The team members produced this project by studying the requirements
provided by the institute and creating the System to satisfy those criteria.
3.1.3 End Users:
The people who will purchase or utilize the built program are referred to
as end users. As our online application is specifically designed for companies
with several employees performing a variety of duties and wanting to keep
track of them, the end users in our instance are the company admins, admins,
and employees.
3.1.4 Product:
The product created for end users is called Task Management System. It’s
a free online tool designed for admins, company admins, and staff members
from different organizations. Once this web-based system is put in place
within a corporation, company admins and staff may easily use it. They
must first authenticate themselves as administrators or staff members of the
company in order to use the program. No training is required because of its
simplicity. The objectives of our product include:

• Server client web solution for the company Admins and Employees

• Company Admins and Employees can use it remotely online

• Company Admin can manage the system from anywhere

• Employees can access his information anywhere they want.

26
4 Chapter
4.1 Introduction:
This research project plan page includes action items for the hypothesis,
specific objectives, and experiments at each stage of creating a successful
research project. You’ll get advice on how innovative your study should be,
how well-known policy issues will affect your application, and how to make
sure your project has enough funding. As you plan and refine your project
concept, take part in our iterative process several times.

1. Keeping to your area of expertise, suggest a project that:

2. Outline draft specific aims and one or more hypothesis

3. Find a study area and probable funding source that will likely support
your research.

4. Outline experiments

5. Assess feasibility

6. If you hit a roadblock, go back to the failure point and reverse your
plan

4.2 Purpose:
There are several simple and impressive techniques for handling employee
information in firms in industrialized nations in the modern world. Since our
nation is still developing, we need to become adept at using contemporary
technologies. To do this, we must bring technology to our nation and in-
form the populace about its practices, which will increase understanding of
the current day. TMS offers organizations a resource that is absent in the
majority of American businesses or institutions, which is a step toward this
accomplishment. It might be burdensome for staff members to approach team
leaders for work delegation and reporting, as well as to update their personal
information. But tools like TMS give staff members a platform where they
can easily get information from their homes, simplifying the process.
4.3 Scope:
Our Web Based interface is divided into three parts:

• Admin panel

27
 • Company Admin

• Employee Panel

4.3.1 Admin Panel:

• Admin can add or delete the company.

• Admin can add or delete the company admin.

• Admin manage the system and databases.

• Admin can update his profile.

4.3.2 Company Admin Panel:

• Company Admin can add, remove and add employees.

• Company Admin can assign the task to the employee.

• Company Admin manages the Attendance of employees.

• Company Admin can [ 10] view attendance reports of employees.

• Company Admin can view and update role of each employee.

• Company admin can view the report of each task given to the employee.

4.3.3 Employee Panel:

• Employee has access to and control over his personal data.

• Employee can update the report of the task.

• Employee can view his attendance report. Employee can update his
password

28
4.4 Use Cases:
4.4.1 Admin:

Figure 1: Admin Use Case Diagram

• Login
• Handle system and database
• Add company Admins
• Add, delete, modify company admins
• Admin profile management
• Add companies
• Logout

In this use case diagram, all the functionalities that an Admin can perform
are shown. With these functionalities a company Admin can interact with
our project.

29
4.4.2 Company Admin:
The functions that a company admin can perform are as follows:

Figure 2: Company Admin Use Case Diagram

• Login

• View Profile

• View Employee

• View employee attendance

• Assign task

• View task Report

• Add or Delete Employee

• Logout

30
This use case diagram shows that how an employee is related to each part
of website and which of a functionality an employee can perform while inter-
acting with our project.
4.4.3 Employee:

Figure 3: Employee Use case Diagram

• Login

• View Profile

• View Attendance

• View assign task

• View task status

• Logout

31
4.5 Abbreviations, acronyms, and definitions:
The following are the definitions, acronyms, and abbreviations for each
tool we’ll be using:
4.5.1 Visual studio:
• Visual Studio is an integrated development environment (IDE), while
Visual Studio Code is a rich text editor akin to Atom. The IDE and text
editor are only one example of how the apps differ from one another.
An IDE is a useful tool for writing, editing, debugging, and executing
your code.

• Depending on the edition and version, Visual Studio’s features might

change, although several features are always present:

• ” A powerful code editor with syntax highlighting, code completion,

and IntelliSense,

• ” Debug your program using powerful debugging tools that let you cre-
ate breakpoints, analyze variables, walk through code, and find prob-
lems.

• With the numerous customization possibilities offered by Visual Studio,

developers may add custom plugins, themes, and extensions to their
development environment. preferences particular to a project

• Built-in support for version control systems like Git, enabling seamless
collaboration and source code management.

4.5.2 SQL:
Structured query language is a special-purpose language used for manag-
ing data stored in relational database management systems (RDBMS) or for
stream processing in relational data stream management systems (RDSMS).
The three languages that make up SQL are data definition, data manip-
ulation, and data control. Relational algebra and tuple relational calculus
served as its foundation at first. The range of SQL includes data access
control, schema creation and modification, data entry, query, update, and
deletion. Despite being primarily a declarative language, as it is commonly
called, SQL also has procedural elements.
One of the earliest commercial languages for the relational model was
SQI, which was introduced by Edgar F. Codd in his seminal 1970 paper,

32
”A Relational Model of Data for Large Shared Data Banks.” Despite not en-
tirely adhering to Codd’s relational model, it became the most used database
language.
SQL was approved as a standard by the American National Standards In-
stitute (ANSI) and the International Organization for Standardization (ISO)
in 1986. Since then, the standard has expanded to provide a greater variety
of functions. Even though there are such standards, most SQL code has to
be modified in order to work correctly across different database systems.
4.6 Server Used:
4.6.1 SQL Server:
The public release of SQL Server 2005 (formerly known as ”Yukon”) took
place in November 2005. It included native support for XML data in addition
to managing relational data. This is why it added an xml data type that
could be used in database columns or as a literal in queries. Any XML
data being stored is validated using the XSD schema, which may be coupled
to XML columns. XML is converted into an internal binary data format
before being saved in the database. Specialized indexing methods are now
available for XML data. In order to allow XQuery queries to be incorporated
in T-SQL, SQL Server 2005 made certain changes to the T-SQL language.
XQuery is used to query XML data.
The new XQuery extension XML DML, which enables query-based up-
dates to XML data, is also introduced. SQL Server 2005 also makes it pos-
sible to contact a database server using web services by using Tabular Data
Stream (TDS) packets encased in SOAP (protocol) requests. The data re-
trieval internet services provide their findings as XML.
Now that Common Language Runtime (CLR) integration is available,
SQL code that is controlled by the CLR may be written. T-SQL for relational
data now supports CTES (Common Table Expressions) for recursive queries
and try/catch error management. New indexing methods, better syntax, and
enhanced error recovery mechanisms are among improvements in SQL Server
2005.
Data pages are check-summed for increased error resistance, and opti-
mistic concurrency support has been added for better performance. The
query processor now efficiently controls concurrent query execution and has
implemented more precise access control and permissions. Because table and
index partitions are supported by default, scaling out a database onto a clus-
ter is considerably easier. SQL CLR was initially made available with SQL

33
Server 2005 in order to facilitate integration with the.NET Framework.
The relational database management system known as Microsoft SQL
Server was developed by Microsoft. A database server is a piece of software
whose primary function is to store and retrieve data when other software
applications, which may run on the same computer or on a different machine
through a network, need it.
For different clienteles, Microsoft offers at least a dozen different editions
of SQL Server. These editions can handle workloads ranging from small
single-machine systems to massive Internet-facing programs with many con-
current users. We utilized a few more tools for graphic design that weren’t
included in the online interface. The following are these tools:
4.7 Web Service:
Any piece of software that uses a recognized XML message protocol and
makes itself available online is considered a web service. XML is used to
encrypt all conversations with a web service [2]. Since web services are inde-
pendent of any specific operating system or computer language, a client can,
for example, contact a web service by sending an XML message and then
waiting for an XML response. Windows programs can connect with UNIX
programs, and Java and Perl can converse.
Web services are self-contained, modular, distributed, dynamic applica-
tions that may be described, published, located, or accessed across a network
in supply chains and corporate activities. These programs may be broadcast,
local, or available online. Web services are built on top of open standards like
TCP/IP, HTTP, Java, HTML, and XML. Direct application-to-application
communication via the Internet is made possible through web services, which
are XML-based platforms for information sharing. These systems might be
composed of words, objects, communications, or software.

34
4.8 Data flow Diagram:

Figure 4: Data Flow Diagram

35
4.9 Dynamic Model:
4.9.1 ER Diagrams:

Figure 5: ER Diagram Diagram

4.10 Graphical User Interface:

It is often believed that something’s initial impression lasts a lifetime.
Our welcome is therefore designed to be as attractive and user-friendly as
possible in order to earn our visitors’ positive marks when they utilize our
web interface for the first time. The graphic that follows shows how well we
concentrated on our website’s user interface and how much we care about
our visitors being completely at ease. We have simplified the color choosing
easier and used our Panel views to make the website more eye-catching and

36
informative. The screenshot below gives you a little idea of how diligently
we have worked to discipline our website’s interface.
4.10.1 Login Page:

Figure 6: Login Page

When you first open this website, you’ll see this screen first. It asks you
to login. There is a single login of each module.
Users are prompted to provide their special username and password so
that their accounts may be accessed securely via the form. The login form for
each module is customized for the particular user type, giving admins, com-
pany admins, and employees a unique experience. Users are guided through
the login process with clear instructions and useful placeholders, enabling a
quick and easy interaction.
Overall, the project’s login page acts as a doorway to a strong and effective
work management system. This page establishes the tone for a smooth trip
across the project’s complete modules by placing a priority on user experience
and security, enabling users to organize their work and interact successfully.

37
4.10.2 Dashboard:

Figure 7: Dashboard

You will be sent to the Admin dashboard if you click Login as Admin, and
the Employee dashboard if you select Login as Employee. On the employee
login page, an admin cannot log in, and vice versa. Two buttons may be seen
in the sidebar here: the dashboard button and the company button. While
the admin may add new firms through the company button, the dashboard
button displays statistics.
We have created a thorough dashboard for our task management system
that caters to both the business admin and employee admin modules, giving
them the tools and information, they need to effectively manage tasks and
simplify operations. The dashboard has a simple, intuitive layout that is
intended to increase productivity and cooperation inside the organization
The employee admin dashboard, on the other hand, is customized to each
employee’s needs. Employees are welcomed with a personalized view of their
allocated assignments and due dates when they check in. The to-do list on
the dashboard is organized by projects, deadlines, and priority. The task
status may be simply updated by employees.

38
4.10.3 Employee Role:

Figure 8: Employee Page

when a manager selects the user button to view users. From the generated
list, the admin may view the time and date the user was added, along with
all of the workers’ roles, emails, phone numbers, and addresses. The user
from the button may also be edited and removed by the admin.
The administrators are welcomed with a thorough list of personnel, nicely
displayed in a tabular fashion, when they reach the website. Each row in
the table displays crucial characteristics on specific employees, such as their
names, roles, and sometimes other relevant information like contact details
or employment status. Quick decision-making and simple identification of
workers’ positions within the company are made possible by the ability to
quickly access this data.
Additionally, the ”View Employees” tab gives admin and business admin
users the option to carry out a number of critical tasks. They may start
the procedure for adding new staff to the system, which would speed up
the onboarding process. Additionally, they have the ability to examine and
modify the roles of current workers to make sure that each team member is
given tasks that are appropriate for their level of skill.

39
4.10.4 Manage Task:

Figure 9: Manage Task Page

The admins or company admins may also delegate a job to one or more
workers along with a description and deadline. According to the task report,
the admin can also update the task’s status. The task can be modified or
removed by the admin.
The Admin and Company Admin will find a user-friendly interface that
provides a list of all current tasks within the system when they open the
”View Task” page. Key details about each work, including its title, de-
scription, assigned employee(s), due date, and present status, are given in a
tabular fashion. The Admin and Company Admin may easily find specific
projects and monitor their progress thanks to this well-organized style.
The page enables the Admin and Company Admin to easily assign new
tasks to workers in order to streamline job delegation. By clicking on an in-
tuitive ”Assign Task” button, they can enter the necessary details, including
the task title, description, due date, and the specific employee(s) to whom
the task should be assigned. The job distribution procedure is made simpler
by this feature, which also guarantees that duties are allocated fairly across
the workforce.

40
4.11 Company Admin:
4.11.1 Dashboard:

Figure 10: Company Admin Dashboard Page

Employees must first authenticate themselves in the program by using the

correct login or authentication mechanism. After that, he or she will be able
to view all of the amenities that meet both our functional and non-functional
application requirements.
Numerous modules, including Branch administration, role management,
user management, task and attendance[9], will be visible to the user once he
has successfully authenticated. If he has the position of company admins,
he will be able to oversee the whole branch and view the job descriptions of
those who work under him.

41
4.11.2 Add New Company:

Figure 11: Add new Company Page

A well labeled header at the top of the page reads ”Add New Com-
pany,” giving users simple instructions. Input forms and dropdown menus
are thoughtfully arranged below the header to collect crucial data about the
new business.[11]
The user is prompted to provide the firm name, contact information, and
address in the first set of input fields. Effective identification and communi-
cation within the system depend on this information. Additionally, choosing
the company’s industry category from the dropdown menu allows for easier
task management system categorization of businesses.
The website then includes a section with the information for the Company
Admin. The name, email address, and phone number of the main contact
can all be entered here by the administrator. The company’s future admin-
istrative procedures will be simplified and direct contact will be made easier
with this information readily available.
In the future, the ”Add New Company” page will have a section where
you may provide the company’s admin rights. The system guarantees that
the designated person can efficiently handle company-related duties, such as
adding new workers, monitoring projects, and managing company-specific
data, by choosing a user from a dropdown list or entering their ID.

42
4.11.3 Manage Branches:

Figure 12: Manage Branches Page

We have a managed company button available in the company section

of the admin panel. When we click on it, we are sent to the company list
page, where we may view the whole list of companies. Along with the firm
name are an address list, email address, and phone and cellphone numbers.
Additionally, there are two options to update or remove the firm. The new
branch button, which allows admin to create new branches, is located at the
top.
The ”View Branches” tab provides the Company Admin with an interface
that makes it simple to add additional branches to the business’s network.
They can fill in crucial information like the branch name, address, phone
number, and any other pertinent information needed for accurate identifica-
tion and organization.
A full list of branches is provided on the same page, giving the Company
Admin the pleasure of managing the company’s active branches. The Com-
pany Admin may quickly get a short summary of the major characteristics
of each branch by seeing the critical information that each entry highlights,
such as the branch’s name, address, and contact information.

43
4.11.4 Mark Attendance:

Figure 13: Mark Attendance Page

There are various sections on the page. The employees may immediately
check and choose the correct day for noting their attendance thanks to the
top’s prominently displayed part that clearly indicates the current date. Em-
ployees can enter their individual check-in and check-out hours for the day
in the input sections that are located immediately below the date.
The website also has a few features that improve the overall user experi-
ence.[8] For instance, if the employee has already clocked in, the system may
automatically fill in the Check-In time with that information, eliminating
the need for human entry and minimizing the risk of mistakes. The system
may similarly offer a timestamp for the Check-Out time based on the actual
moment the employee views the website, guaranteeing accurate records.

44
4.11.5 View Attendance:

Figure 14: View Attendance Page

We’ve included a thorough ”View Attendance” page to our task manage-

ment system to accommodate Employee duties.[16] This website acts as a
focal point for tracking and evaluating employee attendance data and offers
helpful details about when they arrive and depart for each working day.
The page has a user-friendly interface and is intuitively built. The em-
ployee will be shown a neat table when they access the ”View Attendance”
page. The table has columns that provide relevant data, such as the date
and the times that each employee checked in and checked out.
The table gives the Company Admin a bird’s-eye perspective of all the
company’s attendance records.[15] This makes it possible for the company ad-
ministrator to see trends, analyze attendance patterns, and respond quickly
to any attendance-related issues. The Company Admin may also use filters,
such as date range or certain personnel, to speed up analysis and concentrate
on the pertinent data.

45
4.11.6 Manage company Admins:

Figure 15: Manage Company Admins Page

s The website has been built with an easy-to-use layout and includes a
form where users can enter the data required to create a new business admin.
These specifics may include the name, email, and contact information of the
new firm admin[6], as well as perhaps certain permissions or access levels.
The system processes the data once the admin completes the needed fields
and submits the form, at which point the new firm admin is added to the
appropriate sub-organization.
The page shows a list of previously appointed firm admins in addition to
appointing new admins. The names, emails, and designated sub-organization
of each firm administrator are provided on this list, along with other critical
information. The admin may simply manage and keep track of the tasks
assigned to each firm admin using this overview.[12]
Additionally, the ”Manage Company Admins” tab could offer choices
to modify current business admin information or, if required, remove them
from their duties. These features guarantee flexibility and effectiveness in
managing the sub-organizations well.

46
5 Chapter
5.1 Conclusions:
Organizations and businesses are also advancing technology day by day
in the current technological era. Our goal is to give the management and
staff a helpful platform for simple management. After creating this project,
we can say that it brings a new management style between the executive
team and the workforce of any firm. In handling data, regular activities like
attendance, and reporting, both software systems would be highly beneficial.
a simple web-based interface that the administration may utilize to control
all the divisions and staff members of any company.
5.2 Future Work:
Implementing a chat box feature that enables smooth communication be-
tween users, administrators, and corporate admins is a crucial and promising
addition to the task management system’s future development. The addition
of this interactive chat feature aims to improve user experience overall and
promote efficient system-wide cooperation. The chat box may be created
to offer instant messaging features by using Signal R, a potent library for
real-time web applications, allowing users to interact in real-time, exchange
updates, talk about tasks, and ask for help when necessary.
5.2.1 Chat Box:
The chat box feature will work as a dynamic communication tool, facil-
itating interactions between staff members and company admins, allowing
them to talk about task specifics, respond to inquiries, and give fast re-
sponse. Furthermore, administrators will be able to use the chat box to
manage and monitor ongoing work efficiently, providing excellent communi-
cation and smooth collaboration amongst all stakeholders.
Users may readily access their chat history by integrating the chat box
into the current task management system, making it easier to examine old
talks and recover crucial information. The chat box’s interactive features
also encourage collaboration, fostering teamwork and productivity.
Additionally, using Signal R guarantees real-time updates and notifica-
tions, ensuring that users get prompt alerts for new messages, task assign-
ments, and other pertinent system changes. Participants will be able to easily
explore and take part in conversations thanks to the chat box’s user-friendly,
intuitive design.
Overall, the Signal R integration of the chat box feature offers a poten-

47
tial path for improving the task management system’s usefulness and user
engagement. This innovation may greatly increase productivity, simplify
work management, and contribute to the platform’s overall success by en-
abling seamless communication and cooperation. With the addition of this
ground-breaking functionality, the task management system will continue to
develop and adjust to the changing communication requirements of modern
teams and enterprises.[7]
Signal R’s use also guarantees real-time updates and notifications, en-
suring that users get prompt notices of any pertinent system changes, new
communications, and task assignments. The user-friendly, intuitive design of
the chat box will make it easy for participants to explore and take part in
conversations.[14]
Overall, the SignalR integration of the chat box feature offers a potential
path for improving the task management system’s usefulness and user en-
gagement. This innovation may greatly increase productivity, simplify work
management, and contribute to the platform’s overall success by enabling
seamless communication and cooperation. With the addition of this ground-
breaking functionality, the task management system will continue to develop
and adjust to the changing communication requirements of modern teams
and enterprises.

48
5.3 References:
[1] Barker and Deane (2022) Web content management, Google Books.
Available at: https://books.google.com/books?hl=enlr=id=x6N CwAAQBAJoi =
f ndpg = P R2dq =
[2] M, M. (2022) Web services tutorial, Tutorialspoint. Available at:
https://www.tutorialspoint.com/webservices/index.htm (Accessed: 23 Jan-
uary 2023).
[3] wolff, E. (2019) Fronteiras Eclesiais no Pontificado de Francisco, Revis-
tade Cultura Teológica. Availableat: https://www.academia.edu/81840017
/Fronteirase clesiaisn op ontif icadod eF rancisco(Accessed : 01F ebruary2023).
[4] Olajide, F.O. (2021) Best practices of promoting adult and non-formal
education via distance ..., https://ibadanadulteducationjournals.com.ng
/media/2022/08/Best-Practices-of-Promoting-Adult-and-Non-Formal-Education-
via-Distance-and-E-Learning-in-Nigeria.pdf.Available at:
https://ibadanadulteducationjournals.com.ng/media/2022/08/Best-Practices-
of-Promoting-Adult-and-Non-Formal-Education-via-Distance-and-E-Learning-
in-Nigeria.pdf (Accessed: 03 February 2023)
[5] Kharoff, A. (2021) What is task management? 10 best tools and more,
Coursera. Available at: https://www.coursera.org/articles/task-management
(Accessed: 24 September 2023).
[6] Atlassian, J. (2019) Jira: Issue project tracking softwareJuares , Atlas-
sian. Available at: https://www.atlassian.com/software/jira?aceid=adposition=adgroup=151705
p77108085019dse = GOOGLEdse id = 700000001558501dse 1 = GOOGLEgclid =
Cj0KCQjwvL−oBhCxARIsAHkOiu1T B8JyF N SZT F rptwQ ekstv 7hRN znvKU P o0kpvT uZP
JkaApHhEALww cBgclsrc = aw.ds(Accessed : 24September2023).
[7] Asana, T. (2018) Task management software for Effective Teams •
Asana, Asana. Available at: https://asana.com/uses/task-management (Ac-
cessed: 24 September 2023).
[8] Andy, A. (2018) Employee management system - DIVA portal, https://lnu.diva-
portal.org/smash/get/diva2:204828/FULLTEXT01.pdf. Available at: https://lnu.diva-
portal.org/smash/get/diva2:204828/FULLTEXT01.pdf (Accessed: 24 Septem-
ber 2023).
[9] Behance, A. (2019a) Task+Management+Dashboard projects: Pho-
tos, videos, logos, illustrations and branding on Behance, Task+Management+Dashboard
Projects — Photos, videos, logos, illustrations and branding on Behance.
Available at: https://www.behance.net/search/projects?search=Task

49
 [10] wane, A. (2016) Task Management System, Task Management Sys-
tem designs, themes, templates and downloadable graphic elements on Dribb-
ble. Available at: https://dribbble.com/tags/task
[11] brick, A. (2016) Sql database, SQL tutorial. Available at: https://www.w3schools.com/sql
(Accessed: 24 September 2023).
[12] Deshpande, C. (2023) What is angular?: Simplilearn, Simplilearn.com.
Available at: https://www.simplilearn.com/tutorials/angular-tutorial/what-
is-angular (Accessed: 24 September 2023).
[13] brace, A. (2021) Top angular courses online - updated [September
2023] — udemy. Available at: https://www.udemy.com/topic/angular/ (Ac-
cessed: 24 September 2023).
[14] stathum, T. (2022) Bootstrap admin task management system web-
site templates, ThemeForest. Available at: https://themeforest.net/search/bootstrap[15]Andrew,
S. (2021) @angular/service-worker, npm. Available at: https://www.npmjs.com/package/@angula
worker (Accessed: 24 September 2023).
[16] Watson, J. (2020) A new way of working, monday.com. Available at:
https://monday.com/ (Accessed: 24 September 2023).

50