Task Management System

(Web Based)

university_logo.png

Submitted By:

Saqib Mehmood 2019-UET-NFC-BSC-CS-15

Shaheryar Babar 2019-UET-NFC-BSC-CS-25
Muhammad Awais 2019-UET-NFC-BSC-CS-34

Supervised by: Mr. Fiaz Waheed

Department of Computer Science

NFC Institute of Engineering and Fertilizer Research
Faisalabad, Pakistan
 Task Management System
(Web Based)

Submitted to the faculty of Computer Science Department of the NFC

Institute of Engineering and Fertilizer Research Faisalabad Pakistan in the
partial fulfillment of the requirements for the Degree of

Bachelor of Science

in

Computer Science

Director Undergraduate
Internal Examiner External Examiner
studies

NFC Institute of Engineering and Fertilizer Research

Faisalabad, Pakistan
 Declaration

I hereby declare that this report entitled ”Task Management System (Web
Based)” represents my own work and has not been submitted in any form by me
or any other person for any degree or diploma in any university or institution.
All sources of information have been duly cited and referenced.

Signature:
Date:

Signature:
Date:

Signature:
Date:
 Acknowledgments

With the kind assistance and support of many people, our initiative is made
possible. We want to express our sincere gratitude to each and every one of
them. First and foremost, we want to thank our ALLAH ALMIGHTY for the
knowledge he gave us, the strength, the calmness of our minds, and the excellent
health that allowed us to complete this undertaking. We would like to show our
appreciation to our family for their support, which enabled us to finish this
project. Our cherished and helpful group members, who were always there for
one another when we needed them most and greatly assisted one another in
creating this project. We owe a great deal to NFC Institute of Engineering and
Fertilizers Research for their direction, continual oversight, and provision of the
data required for this research, as well as for their assistance in seeing this
project through to completion. We would especially want to thank Mr. Fiaz
Waheed, our adviser, for sharing his knowledge and skills with us on this project.
Contents

1 Chapter 2
1.1 Introduction . . . . . . . . . . . . . . . . 2
1.2 Problem Statement . . . . . . . . . . . . 3
1.3 Purpose . . . . . . . . . . . . . . . . . . . 4
1.4 Scope . . . . . . . . . . . . . . . . . . . . 4
1.4.1 Admin Panel . . . . . . . . . . . . 4
1.4.2 Company Admin Panel . . . . . . 5
1.4.3 Employee panel . . . . . . . . . . . 5
1.5 Definition,Acronyms and Abbreviations . . 6
1.5.1 Visual Studio . . . . . . . . . . . . 6
1.5.2 SQL . . . . . . . . . . . . . . . . . 7
1.6 Server Used: . . . . . . . . . . . . . . . . 8
1.6.1 SQL Server: . . . . . . . . . . . . 8
1.7 Web Service: . . . . . . . . . . . . . . . . 10
1.8 Usage Scenarios: . . . . . . . . . . . . . . 11
1.9 Functional Non-Functional Requirements: . 11
1.9.1 Functional Requirements: . . . . . 11
1.9.2 Authentication: . . . . . . . . . . . 11
1.9.3 Authorization: . . . . . . . . . . . 12
1.9.4 Process Data: . . . . . . . . . . . . 12
1
 1.9.5 Recruitment: . . . . . . . . . . . . 13
1.9.6 Attendance: . . . . . . . . . . . . 13
1.9.7 Company Admin Profile Manage-
ment: . . . . . . . . . . . . . . . . 13
1.9.8 Admin Panel: . . . . . . . . . . . . 14
1.10 Non-Functional Requirements: . . . . . . . 14
1.10.1 Hardware Requirements: . . . . . . 14
1.10.2 Software requirements: . . . . . . . 14
1.10.3 Performance Requirements: . . . . 15
1.10.4 Response Time: . . . . . . . . . . 15
1.10.5 Workload: . . . . . . . . . . . . . 15

2 Chapter 17
2.1 Purpose: . . . . . . . . . . . . . . . . . . 17
2.1.1 Available Methodology: . . . . . . 18
2.1.2 Chosen Methodology and Reason: . 18
2.2 Project Plan: . . . . . . . . . . . . . . . . 19
2.3 Project Planning Includes: . . . . . . . . . 20
2.3.1 Risk Planning: . . . . . . . . . . . 20
2.3.2 Project Scheduling: . . . . . . . . . 22
2.4 Project Structure: . . . . . . . . . . . . . 23

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

4 Chapter 27
4.1 Introduction: . . . . . . . . . . . . . . . . 27
4.2 Purpose: . . . . . . . . . . . . . . . . . . 27
4.3 Scope: . . . . . . . . . . . . . . . . . . . 28
4.3.1 Admin Panel: . . . . . . . . . . . . 28
4.3.2 Company Admin Panel: . . . . . . 29
4.3.3 Employee Panel: . . . . . . . . . . 29
4.4 Use Cases: . . . . . . . . . . . . . . . . . 29
4.5 Abbreviations, acronyms, and definitions: . 33
4.5.1 Visual studio: . . . . . . . . . . . . 33
4.5.2 SQL: . . . . . . . . . . . . . . . . 34
4.6 Server Used: . . . . . . . . . . . . . . . . 35
4.6.1 SQL Server: . . . . . . . . . . . . 35
4.7 Web Service: . . . . . . . . . . . . . . . . 37
3
 4.8 Data flow Diagram: . . . . . . . . . . . . 39
4.9 Dynamic Model: . . . . . . . . . . . . . . 40
4.9.1 ER Diagrams: . . . . . . . . . . . 40
4.10 Graphical User Interface: . . . . . . . . . 40
4.10.1 Login Page: . . . . . . . . . . . . . 41
4.10.2 Dashboard: . . . . . . . . . . . . . 43
4.10.3 Employee Role: . . . . . . . . . . . 45
4.10.4 Manage Task: . . . . . . . . . . . 47
4.11 Company Admin: . . . . . . . . . . . . . 49
4.11.1 Dashboard: . . . . . . . . . . . . . 49
4.11.2 Add New Company: . . . . . . . . 51
4.11.3 Manage Branches: . . . . . . . . . 52
4.11.4 Mark Attendance: . . . . . . . . . 54
4.11.5 View Attendance: . . . . . . . . . 56
4.11.6 Manage company Admins: . . . . . 58

5 Chapter 60
5.1 Conclusions: . . . . . . . . . . . . . . . . 60
5.2 Future Work: . . . . . . . . . . . . . . . . 60
5.2.1 Chat Box: . . . . . . . . . . . . . 61
5.3 References: . . . . . . . . . . . . . . . . . 62

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 maintaining
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
document. 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
management system that will fill existing gaps in the
electronic administration of employees’ activities.
5
 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
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.
6
1.3 Purpose
For effectively managing duties and employee
information in the firms of industrialized nations, there
are several simple and outstanding approaches available
in the modern globe. We must master current
technologies since our nation is still in the
developmental stages. In order to do this, we must
bring technology to our nation and educate the
populace about its practices, which will raise awareness
of the current day. TMS is a step toward attaining this
achievement by providing a resource that is lacking in
the majority of businesses or institutions in our nation
[1]. At the moment, the project manager must
personally give duties to each employee based on their
areas of expertise, and every time, the manager must
speak with employees to update assignments. This is a
difficult circumstance for the leader.
1.4 Scope
Our Web Based interface is divided into three parts:

1. Admin Panel
2. Company Admin Panel
3. Employee Panel
1.4.1 Admin Panel

• Admin can add or delete the company.

7
 • Admin can add or delete the company admin.
• Admin manage the system and databases.
• Admin can update his profile.
1.4.2 Company Admin Panel

• Company Admin can add, remove and add employ-

ees.
• Company Admin can assign the task to the employee.
• Company Admin manages the Attendance of em-
ployees.
• Company Admin can view attendance reports of em-
ployees.
• Company Admin can view and update role of each
employee.
• Company admin can view the report of each task
given to the employee.
1.4.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

8
1.5 Definition,Acronyms and Abbreviations
The definitions, acronyms and abbreviations of each
tool we are going to use is as follows:
1.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.
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 break-

points, check variables, walk through code, and iden-
tify problems in your program.
• A sophisticated code editor with syntax highlighting,
code completion, and Intelligence.
• With the numerous customization possibilities of-
fered 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 man-
agement.

9
1.5.2 SQL

Structured query language is a special-purpose language

used for managing 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 manipulation, 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 Standardization (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

10
 order to work correctly across different database
systems.
1.6 Server Used:
1.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 updates to XML data, is also introduced.
SQL Server 2005 also makes it possible 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

11
 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 optimistic 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
cluster is considerably easier. SQL CLR was initially
made available with SQL Server 2005 in order to
facilitate integration with [Link] 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

12
 concurrent users. We utilized a few more tools for
graphic design that weren’t included in the online
interface.
1.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 independent 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 applications 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.

13
1.8 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.9 Functional Non-Functional Requirements:
1.9.1 Functional Requirements:
1.9.2 Authentication:

• Login: The user’s username and password are re-

quired 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.

14
1.9.3 Authorization:

• User role check: After logging in, the database will

be queried to determine the user’s role, and the user
interface will then be shown appropriately.
1.9.4 Process Data:

• Display: Users with particular responsibilities can

access database content. To be more exact, the em-
ployee can only look at his or her personal informa-
tion. All employees’ personal and professional data
are accessible to the admin.
• Edit: Users who have the employee position are un-
able to change their personal data. Employees’ per-
sonal and professional information can only be edited
by admins. All employee-related information, includ-
ing 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 searchable 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 peo-
15
 ple that have the admin role type. The administrator
can modify the role type associated with a certain
user. An employee who receives a promotion, for in-
stance, will see a change in his position type from
assistant professor to associate professor. The ad-
ministrator may make changes to this employee job.
1.9.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.9.6 Attendance:

Mark attendance:A worker may log his attendance. The

employee’s attendance report is accessible to company
administrators.
1.9.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 responsibilities as its
parent, but it cannot change or remove its parent or
another admin. Only its child admins are editable or
erasable.
• Edit Profile: Its own email address is editable by
admin. Its password can also be modified. Only once
16
 admin has entered their password and authenticated
themselves will these two modifications take effect.
1.9.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.

1.10 Non-Functional Requirements:

1.10.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.10.2 Software requirements:

A web connection must be created because the TMS

application is web-based. The SQL environment will be
17
supported by TMS software’s personal database model
(DBMS).
1.10.3 Performance Requirements:

In order to assess the performance of a system the

following must be clearly specified:
1.10.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 expects 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.
1.10.5 Workload:

The performance of the system is influenced by how the

load is allocated to it. For instance, it is easier to

18
 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 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 maintaining
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
document. 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
20
 management system.
2.1.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
computer-assisted management (CAM). A
computer-based management system’s primary
components in its early phases were computerization
and little tracking assistance. The capacity to effectively
implement a management system for controlling and
integrating organizational management enhanced the
system’s overall functionality with advances in software
infrastructure.
2.1.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

21
 adaptable enough to accept an appropriate mix of
specification-oriented, prototype-oriented,
simulation-oriented, automated transformation-oriented,
or other software development [Link] essence,
the spiral is a series of gradual phases that resemble a
cascade, in which all project operations follow a single
spiral pattern.
2.2 Project Plan:
Project planning is the cornerstone of what all project
managers do, regardless 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
accountable 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?

22
 • How will we meet the timeline and those deliverables?
• Which members of the project team will be respon-
sible for which deliverables?
• Who is on the project team and what role will they
play in those deliverables?
• When will the team reach its milestones, and when
will the other team members help produce those de-
liverables 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 undertaking. 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 con-
tinue reading. You may take a few actions to make
sure that your project plan is remembered for being
well-written and on course.
2.3 Project Planning Includes:
1. Risk Planning
2. Project Scheduling
2.3.1 Risk Planning:

Risk management is a crucial aspect of project

management. Even though they are frequently ignored,
23
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, qual-
ity problems, and redos.
• 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.

24
2.3.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 assignment, 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)

25
 • Employ additional resources (increased cost)
• Reduce the project’s scope (provide fewer services)
• Used the project schedule to justify pursuing one of
these options.
2.4 Project Structure:
A graphical depiction known as an organization chart,
which creates authority, 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 output 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.

26
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

27
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 any-
where
• Employees can access his information anywhere they
want.

28
3.1.5 Process:

[Link]

Figure 1: Process step

29
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 hypoth-
esis
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
30
 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 inform 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
• 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.
31
4.3.2 Company Admin Panel:

• Company Admin can add, remove and add employ-

ees.
• Company Admin can assign the task to the employee.
• Company Admin manages the Attendance of em-
ployees.
• Company Admin can view attendance reports of em-
ployees.
• 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

4.4 Use Cases:

• Login
• Handle system and database

32
[Link]

Figure 2: Admin Use Case Diagram

• 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.

33
The functions that a company admin can perform are as
follows:

company [Link]

Figure 3: Company Admin Use Case Diagram

• Login
• View Profile
• View Employee
• View employee attendance
• Assign task
• View task Report

34
 • Add or Delete Employee
• Logout

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 interacting
with our project.

[Link]

Figure 4: Employee Use case Diagram

• Login
• View Profile
• View Attendance
35
 • View assign task
• View task status
• Logout
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 environ-

ment (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 Stu-
dio’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 create breakpoints, analyze variables,
walk through code, and find problems.
• With the numerous customization possibilities of-
fered by Visual Studio, developers may add custom

36
 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 man-
agement.
4.5.2 SQL:

Structured query language is a special-purpose language

used for managing 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 manipulation, 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, it
became the most used database language.

37
 SQL was approved as a standard by the American
National Standards Institute (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 updates to XML data, is also introduced.
SQL Server 2005 also makes it possible to contact a

38
 database server using web services by using Tabular
Data Stream (TDS) packets encased in SOAP
(protocol) requests. The data retrieval 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 optimistic 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
cluster is considerably easier. SQL CLR was initially
made available with SQL Server 2005 in order to
facilitate integration with [Link] 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

39
 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
concurrent 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 independent 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 applications 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

40
 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.

41
4.8 Data flow Diagram:

[Link]

Figure 5: Data Flow Diagram

42
4.9 Dynamic Model:
4.9.1 ER Diagrams:

ER [Link]

Figure 6: 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

43
 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 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:

[Link]

Figure 7: 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,
company admins, and employees a unique experience.
Users are guided through the login process with clear
instructions and useful placeholders, enabling a quick
44
 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.

45
4.10.2 Dashboard:

[Link]

Figure 8: 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

46
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.

47
4.10.3 Employee Role:

image [Link]

Figure 9: 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.

48
 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.

49
4.10.4 Manage Task:

[Link]

Figure 10: 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, description, 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
50
 job delegation. By clicking on an intuitive ”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.

51
4.11 Company Admin:
4.11.1 Dashboard:

[Link]

Figure 11: 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, will be visible to the user once he has
successfully authenticated. If he has the position of

52
 company admins, he will be able to oversee the whole
branch and view the job descriptions of those who work
under him.

53
4.11.2 Add New Company:

[Link]

Figure 12: Add new Company Page

A well labeled header at the top of the page reads ”Add

New Company,” giving users simple instructions. Input
forms and dropdown menus are thoughtfully arranged
below the header to collect crucial data about the new
business.
The user is prompted to provide the firm name, contact
information, and address in the first set of input fields.
Effective identification and communication 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

54
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 administrative 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.
4.11.3 Manage Branches:

[Link]

Figure 13: 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
55
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 identification 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 Company 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.

56
4.11.4 Mark Attendance:

[Link]

Figure 14: 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.
Employees 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 experience. 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
57
moment the employee views the website, guaranteeing
accurate records.

58
4.11.5 View Attendance:

[Link]

Figure 15: View Attendance Page

We’ve included a thorough ”View Attendance” page to

our task management system to accommodate
Employee duties. 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 employee 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.
This makes it possible for the company administrator 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

59
certain personnel, to speed up analysis and concentrate
on the pertinent data.

60
4.11.6 Manage company Admins:

[Link]

Figure 16: 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, 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.
Additionally, the ”Manage Company Admins” tab
61
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.

62
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 between 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.

63
5.2.1 Chat Box:

The chat box feature will work as a dynamic

communication tool, facilitating interactions between
staff members and company admins, allowing them to
talk about task specifics, respond to inquiries, and give
fast response. Furthermore, administrators will be able
to use the chat box to manage and monitor ongoing
work efficiently, providing excellent communication 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 notifications, ensuring that users get
prompt alerts for new messages, task assignments, 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 potential 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

64
 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.
Signal R’s use also guarantees real-time updates and
notifications, ensuring 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.
Overall, the SignalR integration of the chat box feature
offers a potential 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 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.
5.3 References:
[1] Barker and Deane (2022) Web content management,
Google Books. Available at:

65
[Link] CwAAQBAJoi =
f ndpg = P R2dq =
[2] M, M. (2022) Web services tutorial, Tutorialspoint.
Available at:
[Link]
(Accessed: 23 January 2023).
[3] wolff, E. (2019) Fronteiras Eclesiais no Pontificado de
Francisco, Revistade Cultura Teológica. Availableat:
[Link]
/Fronteiraseclesiaisnopontif icadodeF rancisco(Accessed :
01F ebruary2023).
[4] Olajide, F.O. (2021) Best practices of promoting
adult and non-formal education via distance ...,
[Link]
/media/2022/08/Best-Practices-of-Promoting-Adult-
and-Non-Formal-Education-via-Distance-and-E-
[Link] at:
[Link]
Practices-of-Promoting-Adult-and-Non-Formal-
[Link]
(Accessed: 03 February 2023

66