Online Roster System: Project Report on System Requirements and Design
VerifiedAdded on 2023/01/10
|25
|3558
|97
Report
AI Summary
This report provides a comprehensive overview of an Online Roster System project. It begins with an abstract summarizing the system's purpose: to facilitate employee attendance tracking and leave management for HR and management. The introduction highlights the system's cloud-based implementation and its role in managing employee rosters efficiently. The report outlines the project's aim, which is to develop a system for admin control and data management. It includes a detailed project management plan, encompassing a project charter, work breakdown structure (WBS), project schedule, and risk management analysis. The requirements document details user requirements for HR, management, and employees, alongside system and domain requirements, functional, and non-functional requirements. Use case diagrams illustrate user interactions with the system, followed by a conclusion summarizing the project's scope and findings. Appendices include use case details and a system prototype, providing a complete view of the project's design and implementation.

Running head: ONLINE ROSTER SYSTEM
Online Roster System
Name of the Student
Name of the University
Author’s Note:
Online Roster System
Name of the Student
Name of the University
Author’s Note:
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

1ONLINE ROSTER SYSTEM
Table of Contents
Introduction:....................................................................................................................................3
Aim:.................................................................................................................................................3
Project Management Plan:...............................................................................................................4
Project Charter:............................................................................................................................4
WBS:............................................................................................................................................7
Project Schedule:.........................................................................................................................7
Risk Management:...........................................................................................................................9
Requirements Document:..............................................................................................................11
User Requirements:...................................................................................................................11
System Requirement:.................................................................................................................12
Domain Requirements:..............................................................................................................14
Functional and Non-Functional Requirements:.........................................................................14
Use case Diagrams:....................................................................................................................16
Conclusion:....................................................................................................................................18
Bibliography:.................................................................................................................................19
Appendices:...................................................................................................................................22
Appendix 1: Use Case...............................................................................................................22
Appendix 2: Online Roster System...........................................................................................23
Table of Contents
Introduction:....................................................................................................................................3
Aim:.................................................................................................................................................3
Project Management Plan:...............................................................................................................4
Project Charter:............................................................................................................................4
WBS:............................................................................................................................................7
Project Schedule:.........................................................................................................................7
Risk Management:...........................................................................................................................9
Requirements Document:..............................................................................................................11
User Requirements:...................................................................................................................11
System Requirement:.................................................................................................................12
Domain Requirements:..............................................................................................................14
Functional and Non-Functional Requirements:.........................................................................14
Use case Diagrams:....................................................................................................................16
Conclusion:....................................................................................................................................18
Bibliography:.................................................................................................................................19
Appendices:...................................................................................................................................22
Appendix 1: Use Case...............................................................................................................22
Appendix 2: Online Roster System...........................................................................................23

2ONLINE ROSTER SYSTEM
Abstract
The report reflects the project overview and system requirement specification of the Online
Roster System. This system will be developed so that HR and management can easily track and
control the employee attendance. The employee can request for leave through this system. Each
user will have different actions to complete in this system. The report shares three use case
diagrams for three users. These use case diagrams clearly represented the interaction between the
user and system.
Abstract
The report reflects the project overview and system requirement specification of the Online
Roster System. This system will be developed so that HR and management can easily track and
control the employee attendance. The employee can request for leave through this system. Each
user will have different actions to complete in this system. The report shares three use case
diagrams for three users. These use case diagrams clearly represented the interaction between the
user and system.
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

3ONLINE ROSTER SYSTEM
Introduction:
The information system can be referred as the integrated collection of technical
equipment that are used for gathering, recording and executing information and in order to
provide knowledge, information and digital products (Sanchez and Terlizzi 2017). Various
organizations depend on the information system for executing and managing business operations.
The Online Roster System is a type of information system that allows managing the roster of the
employee very easily. The proposed Online Roster System will be implemented in the cloud
which will increase availability.
The report is created based on the requirements of Online Roster System. The report
includes the base idea of the project for implementing the Online Roster System. Report also
concentrates on the Online Roster System’s requirements to highlight the technical aspects of the
system. The use case diagram is used for showing the interaction between the users and the
system. The prototype shows the font end of the system.
Aim:
The aim of the project is to develop a system that will allow the admin to manage the
employee roster. The system will be associated with a database system that can handle the data
processes. The purpose of the system will be easy storage, retrieval and modification of data. The
project will be capable of entertaining new requirements throughout the project life cycle.
Introduction:
The information system can be referred as the integrated collection of technical
equipment that are used for gathering, recording and executing information and in order to
provide knowledge, information and digital products (Sanchez and Terlizzi 2017). Various
organizations depend on the information system for executing and managing business operations.
The Online Roster System is a type of information system that allows managing the roster of the
employee very easily. The proposed Online Roster System will be implemented in the cloud
which will increase availability.
The report is created based on the requirements of Online Roster System. The report
includes the base idea of the project for implementing the Online Roster System. Report also
concentrates on the Online Roster System’s requirements to highlight the technical aspects of the
system. The use case diagram is used for showing the interaction between the users and the
system. The prototype shows the font end of the system.
Aim:
The aim of the project is to develop a system that will allow the admin to manage the
employee roster. The system will be associated with a database system that can handle the data
processes. The purpose of the system will be easy storage, retrieval and modification of data. The
project will be capable of entertaining new requirements throughout the project life cycle.
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

4ONLINE ROSTER SYSTEM
Project Management Plan:
Project Charter:
Project Name: Online Roster System Project Manager: Praquesh Tandukar
Background/ Rationale:
Stix Catering wants to improve their traditional roster system via web services.
Installation of a new online system.
Objective/s: Success criteria:
Transfer all the records of all staffs in the
database system.
Completion of project within the timeframe
and budget.
Completing the project within 10-12
weeks within the estimated budget
Improved reliability and efficiency of the
system.
Training all the staffs 2 weeks prior to
system implementation.
Create a feedback system.
Project Management Plan:
Project Charter:
Project Name: Online Roster System Project Manager: Praquesh Tandukar
Background/ Rationale:
Stix Catering wants to improve their traditional roster system via web services.
Installation of a new online system.
Objective/s: Success criteria:
Transfer all the records of all staffs in the
database system.
Completion of project within the timeframe
and budget.
Completing the project within 10-12
weeks within the estimated budget
Improved reliability and efficiency of the
system.
Training all the staffs 2 weeks prior to
system implementation.
Create a feedback system.

5ONLINE ROSTER SYSTEM
Deliverable: Exclusions:
Project Charter Timetable training not included.
Providing a complete software without any
bugs and transferring the data to the new
database without any loss.
Benefits Expected: (Inter) Dependencies / Interfaces:
Managing the roster efficiently, saving time
and costs.
Evaluation the efficiency of the system
implemented.
Better management control with improved
quality of service.
User-friendly system. Database must be created before records are
transferred.
Deliverable: Exclusions:
Project Charter Timetable training not included.
Providing a complete software without any
bugs and transferring the data to the new
database without any loss.
Benefits Expected: (Inter) Dependencies / Interfaces:
Managing the roster efficiently, saving time
and costs.
Evaluation the efficiency of the system
implemented.
Better management control with improved
quality of service.
User-friendly system. Database must be created before records are
transferred.
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

6ONLINE ROSTER SYSTEM
Increased company and employees satisfaction
Assumptions: Constraints:
Assume everything is organized. Budget Estimated might rise up.
Project was carried out within the estimated
budget. Time constraints for training the staffs.
Implementation carried out without any
complications.
Some staffs might find the new system
difficult.
Staffs are happy with the new system. Incompatibility of the proposed system.
No legal disagreements
Timeframe: 12 Weeks Cost Estimate / Budget: AUD $10,000 -
$15,000
Date Approvals/ sign-offs: Project Manager Sign-off & Date
Increased company and employees satisfaction
Assumptions: Constraints:
Assume everything is organized. Budget Estimated might rise up.
Project was carried out within the estimated
budget. Time constraints for training the staffs.
Implementation carried out without any
complications.
Some staffs might find the new system
difficult.
Staffs are happy with the new system. Incompatibility of the proposed system.
No legal disagreements
Timeframe: 12 Weeks Cost Estimate / Budget: AUD $10,000 -
$15,000
Date Approvals/ sign-offs: Project Manager Sign-off & Date
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

7ONLINE ROSTER SYSTEM
WBS:
WBS Task Name
0 Online Roster System
1 Developing the Project Charter
1.1 Write Business Case
1.2 Identify all the stakeholders
1.3 Submit and Sign-off Project Charter
2 Determine Project Scope
2.1 Work within the stated scope
3 Prepare WBS
4 Developing and Finalize PMP(Project Management Plan)
4.1 Identify all tasks
4.1.1 Allocate time and budget for each tasks
4.1.2 Divide them among team
4.2 Submit and Approve Project Plan
5 Identify the users’ requirements
5.1 research all the requirements and hardware & software required
6 Design the system and user interface
6.1 Check for any errors or changes required
6.2 Finalizing the design
7 Developing the system according to the design and requirements
7.1 Purchase the hardware and software required
7.2 Develop a prototype system
8 Test the prototype and evaluate
8.1 Test the fluency of the system
8.2 Gather staff feedbacks
9 Implement the system considering the feedbacks
9.1 Provide training about to whole staffs
9.2 Monitor all the risks that might occur
9.2.1 Provide measure to mitigate the risks
10 Carry out maintenance if required in future
11 Document the final report and present them
Project Schedule:
Task Name Duration Start Finish Predecessors
Online Roster System 47 days Mon 10/12/09 Tue 12/15/09
Developing the Project Charter 6 days Mon 10/12/09 Mon 10/19/09
Write Business Case 3 days Mon 10/12/09 Wed 10/14/09
WBS:
WBS Task Name
0 Online Roster System
1 Developing the Project Charter
1.1 Write Business Case
1.2 Identify all the stakeholders
1.3 Submit and Sign-off Project Charter
2 Determine Project Scope
2.1 Work within the stated scope
3 Prepare WBS
4 Developing and Finalize PMP(Project Management Plan)
4.1 Identify all tasks
4.1.1 Allocate time and budget for each tasks
4.1.2 Divide them among team
4.2 Submit and Approve Project Plan
5 Identify the users’ requirements
5.1 research all the requirements and hardware & software required
6 Design the system and user interface
6.1 Check for any errors or changes required
6.2 Finalizing the design
7 Developing the system according to the design and requirements
7.1 Purchase the hardware and software required
7.2 Develop a prototype system
8 Test the prototype and evaluate
8.1 Test the fluency of the system
8.2 Gather staff feedbacks
9 Implement the system considering the feedbacks
9.1 Provide training about to whole staffs
9.2 Monitor all the risks that might occur
9.2.1 Provide measure to mitigate the risks
10 Carry out maintenance if required in future
11 Document the final report and present them
Project Schedule:
Task Name Duration Start Finish Predecessors
Online Roster System 47 days Mon 10/12/09 Tue 12/15/09
Developing the Project Charter 6 days Mon 10/12/09 Mon 10/19/09
Write Business Case 3 days Mon 10/12/09 Wed 10/14/09

8ONLINE ROSTER SYSTEM
Identify all the stakeholders 2 days Thu 10/15/09 Fri 10/16/09 2
Submit and Sign-off Project
Charter 1 day Mon 10/19/09 Mon 10/19/09 3
Determine Project Scope 2 days Tue 10/20/09 Wed 10/21/09
Work within the stated scope 2 days Tue 10/20/09 Wed 10/21/09 4
Prepare WBS 1 day Thu 10/22/09 Thu 10/22/09 6
Developing and Finalize
PMP(Project Management Plan) 5 days Fri 10/23/09 Thu 10/29/09
Identify all tasks 4 days Fri 10/23/09 Wed 10/28/09
Allocate time and budget for
each tasks 2 days Fri 10/23/09 Mon 10/26/09 7
Divide them among team 2 days Tue 10/27/09 Wed 10/28/09 10
Submit and Approve Project
Plan 1 day Thu 10/29/09 Thu 10/29/09 11
Identify the users’ requirements 4 days Fri 10/30/09 Wed 11/4/09
research all the requirements and
hardware & software required 4 days Fri 10/30/09 Wed 11/4/09 12
Design the system and user
interface 5 days Thu 11/5/09 Wed 11/11/09
Check for any errors or changes
required 3 days Thu 11/5/09 Mon 11/9/09 14
Finalizing the design 2 days Tue 11/10/09 Wed 11/11/09 16
Developing the system according
to the design and requirements 9 days Thu 11/12/09 Tue 11/24/09
Purchase the hardware and
software required 2 days Thu 11/12/09 Fri 11/13/09 17
Develop a prototype system 7 days Mon 11/16/09 Tue 11/24/09 19
Test the prototype and evaluate 5 days Wed 11/25/09 Tue 12/1/09
Test the fluency of the system 2 days Wed 11/25/09 Thu 11/26/09 20
Gather staff feedbacks 3 days Fri 11/27/09 Tue 12/1/09 22
Implement the system
considering the feedbacks 5 days Wed 12/2/09 Tue 12/8/09
Provide training about to whole
staffs 2 days Wed 12/2/09 Thu 12/3/09 23
Monitor all the risks that
might occur 3 days Fri 12/4/09 Tue 12/8/09
Provide measure to mitigate
the risks 3 days Fri 12/4/09 Tue 12/8/09 25
Carry out maintenance if required
in future 2 days Wed 12/9/09 Thu 12/10/09 27
Document the final report and
present them 3 days Fri 12/11/09 Tue 12/15/09 28
Identify all the stakeholders 2 days Thu 10/15/09 Fri 10/16/09 2
Submit and Sign-off Project
Charter 1 day Mon 10/19/09 Mon 10/19/09 3
Determine Project Scope 2 days Tue 10/20/09 Wed 10/21/09
Work within the stated scope 2 days Tue 10/20/09 Wed 10/21/09 4
Prepare WBS 1 day Thu 10/22/09 Thu 10/22/09 6
Developing and Finalize
PMP(Project Management Plan) 5 days Fri 10/23/09 Thu 10/29/09
Identify all tasks 4 days Fri 10/23/09 Wed 10/28/09
Allocate time and budget for
each tasks 2 days Fri 10/23/09 Mon 10/26/09 7
Divide them among team 2 days Tue 10/27/09 Wed 10/28/09 10
Submit and Approve Project
Plan 1 day Thu 10/29/09 Thu 10/29/09 11
Identify the users’ requirements 4 days Fri 10/30/09 Wed 11/4/09
research all the requirements and
hardware & software required 4 days Fri 10/30/09 Wed 11/4/09 12
Design the system and user
interface 5 days Thu 11/5/09 Wed 11/11/09
Check for any errors or changes
required 3 days Thu 11/5/09 Mon 11/9/09 14
Finalizing the design 2 days Tue 11/10/09 Wed 11/11/09 16
Developing the system according
to the design and requirements 9 days Thu 11/12/09 Tue 11/24/09
Purchase the hardware and
software required 2 days Thu 11/12/09 Fri 11/13/09 17
Develop a prototype system 7 days Mon 11/16/09 Tue 11/24/09 19
Test the prototype and evaluate 5 days Wed 11/25/09 Tue 12/1/09
Test the fluency of the system 2 days Wed 11/25/09 Thu 11/26/09 20
Gather staff feedbacks 3 days Fri 11/27/09 Tue 12/1/09 22
Implement the system
considering the feedbacks 5 days Wed 12/2/09 Tue 12/8/09
Provide training about to whole
staffs 2 days Wed 12/2/09 Thu 12/3/09 23
Monitor all the risks that
might occur 3 days Fri 12/4/09 Tue 12/8/09
Provide measure to mitigate
the risks 3 days Fri 12/4/09 Tue 12/8/09 25
Carry out maintenance if required
in future 2 days Wed 12/9/09 Thu 12/10/09 27
Document the final report and
present them 3 days Fri 12/11/09 Tue 12/15/09 28
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide

9ONLINE ROSTER SYSTEM
Risk Management:
I
D
Curr
ent
Statu
s
Risk
Categor
y
Risk
Descript
ion
Risk
Impa
ct
Probabi
lity of
Occurr
ence
Risk
Ratin
g
Risk
Respo
nse
Strate
gy
Response
Strategy
Assigned
To
1 Open Technic
al
The
project
uses low
quality
technolo
gical
compone
nts. The
technical
compone
nts are
not
capable
of
fulfilling
the
factors
like
stability,
scalabilit
y,
availabili
ty,
extensibi
lity,
security
and
usability
(Bashash
in et al.
2016)
High Low High Mitigat
ion
The
responsib
le person
will be
making
sure that
technical
compone
nts are
free of
security
issues
System
Administ
rator
2 Open Stakehol
ders
If the
stakehol
ders have
negative
thought
about the
project
then it
Medi
um
Medium Medi
um
Mitigat
ion
The
stakehold
ers will
receive
continuou
s update
about the
project
Project
Manager
Risk Management:
I
D
Curr
ent
Statu
s
Risk
Categor
y
Risk
Descript
ion
Risk
Impa
ct
Probabi
lity of
Occurr
ence
Risk
Ratin
g
Risk
Respo
nse
Strate
gy
Response
Strategy
Assigned
To
1 Open Technic
al
The
project
uses low
quality
technolo
gical
compone
nts. The
technical
compone
nts are
not
capable
of
fulfilling
the
factors
like
stability,
scalabilit
y,
availabili
ty,
extensibi
lity,
security
and
usability
(Bashash
in et al.
2016)
High Low High Mitigat
ion
The
responsib
le person
will be
making
sure that
technical
compone
nts are
free of
security
issues
System
Administ
rator
2 Open Stakehol
ders
If the
stakehol
ders have
negative
thought
about the
project
then it
Medi
um
Medium Medi
um
Mitigat
ion
The
stakehold
ers will
receive
continuou
s update
about the
project
Project
Manager
Paraphrase This Document
Need a fresh take? Get an instant paraphrase of this document with our AI Paraphraser

10ONLINE ROSTER SYSTEM
can be a
very bad
sign for
the
project.
If the
project
goes
through
few
challeng
es and
failure
then
whole
project
can be
shut
down
(Grover
and
Froese
2016)
progress.
They
must be
informed
about
what
issues are
occurring
the
project
and how
well the
team is
handling
the.
Consideri
ng the
stakehold
ers as
crucial
part of
the
project
will make
them feel
like
responsib
le for
success
for the
project.
3 Open Authorit
y
Often the
project
team
does not
have the
authority
to
complete
a task of
the
project.
If the
project
crosses
the
Low Low Low Transf
er
The
project
manager
transfer
the risk to
the
project
owner
whenever
the
organizati
onal
boundary
is crossed
(Laudon
Project
Owner
can be a
very bad
sign for
the
project.
If the
project
goes
through
few
challeng
es and
failure
then
whole
project
can be
shut
down
(Grover
and
Froese
2016)
progress.
They
must be
informed
about
what
issues are
occurring
the
project
and how
well the
team is
handling
the.
Consideri
ng the
stakehold
ers as
crucial
part of
the
project
will make
them feel
like
responsib
le for
success
for the
project.
3 Open Authorit
y
Often the
project
team
does not
have the
authority
to
complete
a task of
the
project.
If the
project
crosses
the
Low Low Low Transf
er
The
project
manager
transfer
the risk to
the
project
owner
whenever
the
organizati
onal
boundary
is crossed
(Laudon
Project
Owner

11ONLINE ROSTER SYSTEM
boundary
of the
organizat
ion the
situation
will
invite
this risk
and
Laudon
2016).
Requirements Document:
User Requirements:
The user of the system are HR, management and employee. The requirements of HR are
as following.
i. HR can create yearly roster from the system
ii. HR can update the details available in the roster like changing week off or leave
iii. The HR can approve the leave that employee has requested for
iv. HR can record shift swap
v. HR can create a schedule regarding the employee training
vi. HR can update the information regarding the qualification of the employee
vii. HR can create schedule of sick leave for the employee
viii. HR can create a schedule of sabbatical leave for the employee
ix. HR can record the overtime employees are doing
x. HR can add employee data
xi. HR can modify the employee data
xii. HR can delete employee data
xiii. HR can schedule the meetings along with storing the participants of the meetings
boundary
of the
organizat
ion the
situation
will
invite
this risk
and
Laudon
2016).
Requirements Document:
User Requirements:
The user of the system are HR, management and employee. The requirements of HR are
as following.
i. HR can create yearly roster from the system
ii. HR can update the details available in the roster like changing week off or leave
iii. The HR can approve the leave that employee has requested for
iv. HR can record shift swap
v. HR can create a schedule regarding the employee training
vi. HR can update the information regarding the qualification of the employee
vii. HR can create schedule of sick leave for the employee
viii. HR can create a schedule of sabbatical leave for the employee
ix. HR can record the overtime employees are doing
x. HR can add employee data
xi. HR can modify the employee data
xii. HR can delete employee data
xiii. HR can schedule the meetings along with storing the participants of the meetings
⊘ This is a preview!⊘
Do you want full access?
Subscribe today to unlock all pages.

Trusted by 1+ million students worldwide
1 out of 25
Related Documents

Your All-in-One AI-Powered Toolkit for Academic Success.
+13062052269
info@desklib.com
Available 24*7 on WhatsApp / Email
Unlock your academic potential
Copyright © 2020–2025 A2Z Services. All Rights Reserved. Developed and managed by ZUCOL.