Online Roster System: Project Overview and System Requirement Specification

This report provides an overview of the Online Roster System and its system requirement specification. It includes user requirements, system requirements, use case diagrams, and a prototype of the system. The system aims to improve employee roster management and attendance tracking.

Running head: ONLINE ROSTER SYSTEM
Online Roster System
Name of the Student
Name of the University
Author’s Note:

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

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.

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.

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.

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.

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

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

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

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

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

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

12ONLINE ROSTER SYSTEM
xiv. HR can schedule the paternity leave for the employee
The requirements of the manager are as following
i. Manager can create a report of all the employees who for a specific date or time
period
ii. Manager can add/delete/modify employee data
iii. Manager can create a report of employee attendance
iv. Manager can update the roster
v. Manager can decline approve/leave request
The requirements of the employee are as following
i. Employee can add their own data
ii. Employee can modify their own data
iii. Employee can request for leave
iv. Employee can view roster of their own attendance data
System Requirement:
The system requirements of the proposed Online Roster System are as following.
i. The system will be deployed in a server that can process all the user requests
ii. The system should have a database for managing the data
iii. The system must have an interface through which the user can access the
functions and information
iv. The system needs to establish a secure connection between the server and user

13ONLINE ROSTER SYSTEM
Figure 1: Login Page Wireframe
(Source: Created by Author)
Figure 2: Send Leave Request Page Wireframe
(Source: Created by Author)

14ONLINE ROSTER SYSTEM
Domain Requirements:
The domain requirements are as following.
i. The system will be able to access the list of the managers, HR and employee
ii. The system can fetch the data regarding the availability of employees for a
particular date
iii. The system can fetch the employee record based on the designation
iv. The system can validate the data entered into the system
Functional and Non-Functional Requirements:
Functional Requirement of this system are as following:
i. The system will authenticate every user that tries to access the system. The
system will have a login function that will check the user login id and password.
Each user will get a login id and password.
ii. The system will authorize the user request to access an information or functions.
The system will categorize the user in different categories. Each category will be
allowed to access different functions of the system.
iii. The system will have a data storage media that will handle the process of data
storing, retrieving and deleting from the database. The data storage will function
as storage media for employee roster and user data.
iv. The system allow the HR and Manager to manage roster for each employee. The
HR and manager can update the roster. They can also approve or reject the
request of the employee for leave.

15ONLINE ROSTER SYSTEM
v. The employee can request for leave through the system. The employee will
mention the type of leave and date for submitting the leave application.
The Non-Functional Requirement of this system are as following:
i. The security is one of the most required non-functional requirement of the
system. The system will hold the business related sensitive data that must be
protected from external entities. The system will protect the data from data theft
and corruption.
ii. Availability is another major requirement of the system. The users can access the
system anytime. The system can be down during night time so that system
upgrades can be done without hampering the system much.
iii. It is essential that users of the system can easily access the system functionality.
The usability of the system will ensure ease of use. The system will integrate easy
navigation.

16ONLINE ROSTER SYSTEM
Use case Diagrams:
Figure 3: Use Case Diagram of HR
(Source: Created by Author)

17ONLINE ROSTER SYSTEM
Figure 4: Use Case Diagram of Manager
(Source: Created by Author)

18ONLINE ROSTER SYSTEM
Figure 5: Use Case Diagram of Employee
(Source: Created by Author)
Conclusion:
From the above study it can be concluded that the roster system should allow different
functions for different user types. The system must record each data into the code database so
that easy retrieval of the data can be done. The project charter provides a good idea of the system
to be developed. The user case diagrams provide establishes clear understanding of how the
users will interact with the system.

19ONLINE ROSTER SYSTEM
Bibliography:
Bahill, A.T. and Madni, A.M., 2017. Discovering system requirements. In Tradeoff Decisions in
System Design (pp. 373-457). Springer, Cham.
Bashashin, M.V., Kekelidze, D.V., Kostromin, S.A., Korenkov, V.V., Kuniaev, S.V., Morozov,
V.V., Potrebenikov, Y.K., Trubnikov, G.V. and Philippov, A.V., 2016. NICA project
management information system. Physics of Particles and Nuclei Letters, 13(5), pp.618-620.
de Sousa, T.C., Kelvin, L., Neto, C.D. and de Carvalho, C.G.N., 2017. A Formal Semantics for
Use Case Diagram Via Event-B. JSW, 12(3), pp.189-200.
Eroshkin, S.Y., Koryagin, N.D., Kovkov, D.V., Panov, D.V. and Sukhorukov, A.I., 2017. The
paradigm of the integration of different types of management information systems in investment
and construction company implementing the project approach. Procedia Computer Science, 103,
pp.605-608.
Grover, R. and Froese, T.M., 2016. Knowledge management in construction using a SocioBIM
platform: A case study of AYO smart home project. Procedia Engineering, 145, pp.1283-1290.
Jacobson, I., Spence, I. and Kerr, B., 2016. Use-Case 2.0. Commun. ACM, 59(5), pp.61-69.
Joosten, D., Basten, D. and Mellis, W., 2016. Measurement of information system project
success in German organizations. In Project Management: Concepts, Methodologies, Tools, and
Applications (pp. 1175-1196). IGI Global.
Kostalova, J., Tetrevova, L. and Svedik, J., 2015. Support of project management methods by
project management information system. Procedia-Social and Behavioral Sciences, 210, pp.96-
104.

20ONLINE ROSTER SYSTEM
Laudon, K.C. and Laudon, J.P., 2016. Management information system. Pearson Education
India.
Marnewick, C., 2016. Benefits of information system projects: The tale of two
countries. International Journal of Project Management, 34(4), pp.748-760.
Nassif, A.B., Capretz, L.F. and Ho, D., 2016. Enhancing use case points estimation method using
soft computing techniques. arXiv preprint arXiv:1612.01078.
Noe, R.A., Hollenbeck, J.R., Gerhart, B. and Wright, P.M., 2017. Human resource management:
Gaining a competitive advantage. New York, NY: McGraw-Hill Education.
Permana, P.A.G., 2015. Scrum method implementation in a software development project
management. International Journal of Advanced Computer Science and Applications, 6(9),
pp.198-204.
Rhode, J. and Miller, T., 2017. Essentials for Preparing to Teach an Existing Online Course on
Short Notice.
Sanchez, O.P. and Terlizzi, M.A., 2017. Cost and time project management success factors for
information systems development projects. International Journal of Project Management, 35(8),
pp.1608-1626.
Schwalbe, K., 2015. Information technology project management. Cengage Learning.
Subiyakto, A.A., Ahlan, A.R., Putra, S.J. and Kartiwi, M., 2015. Validation of information
system project success model: a focus group study. SAGE Open, 5(2), p.2158244015581650.
Tischler, M.B., 2018. System identification methods for aircraft flight control development and
validation. In Advances in aircraft flight control (pp. 35-69). Routledge.

21ONLINE ROSTER SYSTEM
Wautelet, Y., Heng, S., Hintea, D., Kolp, M. and Poelmans, S., 2016, November. Bridging user
story sets with the use case model. In International Conference on Conceptual Modeling(pp.
127-138). Springer, Cham.
Weiss, J., Newell, S. and Swan, J., 2017, January. Introduction to IT and project management
minitrack. In Proceedings of the 50th Hawaii International Conference on System Sciences.
Zhang, C., Duan, Z., Yu, B., Tian, C. and Ding, M., 2016. A test case generation approach based
on sequence diagram and automata models. Chinese Journal of Electronics, 25(2), pp.234-240.
Zwikael, O., 2016. International journal of project management special issue on “project benefit
management”.

22ONLINE ROSTER SYSTEM
Appendices:
Appendix 1: Use Case
A use case is a software and system engineering term that describes how a user uses a
system to accomplish a particular goal. A use case acts as a software modeling technique that
defines the features to be implemented and the resolution of any errors that may be encountered.
Use cases define interactions between external actors and the system to attain particular
goals. There are three basic elements that make up a use case:
 Actors: Actors are the type of users that interact with the system.
 System: Use cases capture functional requirements that specify the intended behavior of
the system.
 Goals: Use cases are typically initiated by a user to fulfill goals describing the activities
and variants involved in attaining the goal.
Use cases are modeled using unified modeling language and are represented by ovals
containing the names of the use case. Actors are represented using lines with the name of the
actor written below the line. To represent an actor's participation in a system, a line is drawn
between the actor and the use case. Boxes around the use case represent the system boundary.

23ONLINE ROSTER SYSTEM
Appendix 2: Online Roster System

24ONLINE ROSTER SYSTEM