SSE4300: SOFTWARE PROJECT

MANAGEMENT

AUTOMATED STAFF ATTENDANCE SYSTEM

USING A FACIAL RECOGNITION APPROACH

TASK 5 (Configuration MANAGEMENT)

(GROUP 1: COUGARYAHOO)

DR. NORHAYATI BINTI MOHD ALI

GROUP MEMBERS:

1. MUHAMMAD AFIF MIRZA BIN MOHD FARID 192128

2. NUR AIDA FARAHANIE BINTI AHMAD 192494
3. ANIS NUR HAJAR BINTI AHMAD RIZAL 192560
4. AMIR KHAIDIR BIN ADZEMAN 192212
5. OSAMAH EBRAHIM ZAID ABKAR 191592
 TABLE OF CONTENT

1.0 INTRODUCTION ………………………………………………………………………………

1.1 BACKGROUND ………………………………………………………………………

1.2 SCOPE …………………………………………………………………………………

1.3 PURPOSE ……………………………………………………………………………..

2. Change management
2.1 About
2.2 Change request

3.0 SOFTWARE TOOL USED ……………………………………………………………………

3.1 ABOUT TOOL …………………………………………………………………………

4.0 REFERENCES …………………………………………………………………………………

5.0 APPENDIX ……………………………………………………………………………………...

1.0 INTRODUCTION
1.1 BACKGROUND

Software Configuration Management is defined as a process to systematically manage,

organize, and control the changes in the documents, codes, and other task during the
Software Development Life Cycle. It is abbreviated as the SCM process in software
engineering. The primary purpose is to increase productivity with minimal mistakes.

1.2 SCOPE

The scope for this configuration management plan are:

● To identify the suitable configuration management tool for this project
● To define the changes needed for this system
● To implement the chosen tool to manage the change requests systematically

1.3 PURPOSE
The configuration management plan provides details of how the team will manage the
control of configuration items being developed under each phase. It defines the policies and
procedures for configuration management and the necessary infrastructure to implement
them throughout the project.

2. Change Management:
2.1 About

Change management encompasses in managing the request of changes by the

stakeholders to achieve the required business goals. The working out of the costs and
impact of changes also is taken into account of the change management.
2.2 Change request :

Change request

Project: Automated staff attendance system using facial Date: 17/11/19

recognition

Change Requester: Hajar Anis Change No: 001

Change Type: Major

Change Priority: High

Title: Size of database

Describe the change being requested:

The size of current database is full/ limited

Describe the reason for the change request:

The database size need to upgrade into a larger one, because there are several
new staffs that need to be registered

Schedule start: 19/11/19 -22/11/19

Change owner: Afif Mirza

Change Approver: Osamah

Change reviewer: Amir Khaidir

Statue:
Approved

Justification of Approval, Rejection or deferral:

This should be fixed as it effect the stakeholder
 Change request

Project: Automated staff attendance system using facial Date: 17/11/19

recognition

Change Requester: Muhammad Afif Mirza Change No: 002

Change Type: Major

Change Priority: High

Title: Cost of the software system

Describe the change being requested:

The cost of attendance system should be reduced

Describe the reason for the change request:

The cost attendance system should be reduced. This is because, if its malfunctions the
cost needed to maintain the system should be lower. Cost for maintenance is crucial as
improper maintenance can jeopardize the system thus causing delay for the staff and
lower the system’s performance.

Schedule start: 23/11/19 -2/12/19

Change owner: Hajar Anis

Change Approver: Osamah

Change reviewer: Amir Khaidir

Statue : rejected

Justification of Approval, Rejection or deferral:

after gathering requirements and making the cost estimation plan we decided
the cost of the system so, we can not reduce the cost as it will affect the project
and the developing team.
 Change request

Project: Automated staff attendance system using facial Date: 17/11/19

recognition

Change Requester: Muhammad Afif Mirza Change No: 003

Change Type: Major

Change Priority: High

Title: Privacy of the attendance system

Describe the change being requested:

The privacy of the attendance system should be tightened and be secured

Describe the reason for the change request:

The privacy of the system help in providing detection if any unauthorized faces try to
access the system as well as keeping it safe from any other threats. Only authorized
persons like the manager and the user can use the system.

Schedule start: 2/12/19 -10/12/19

Change owner: Aida Farahanie

Change Approver: Osamah

Change reviewer: Amir Khaidir

Statue:
Approved

Justification of Approval, Rejection or deferral:

This should be fixed as it affects the security risk of the attendance system
 Change request

Project: Attendance system using facial recognition Date: 17/11/19

Change Requester: Nur Aida Farahanie binti Ahmad Change No: 004

Change Type: Minor

Change Priority: High

Title: Feature extraction

Describe the change being requested: Raise the number of features to be extracted

Describe the reason for the change request: To enhance the accuracy of the image
to be detected by the system so that the system still can detect the user’s face if the
head moves (example: yawning)

Schedule start: 10/12/19 - 20/12/19

Change owner: Amir Khaidir

Change Approver: Afif Mirza

Change reviewer: Osamah

Statue:
Approved

Justification of Approval, Rejection or deferral:

This should be fixed as it may cause the registered user’s face undetected with the vary
of head’s movement
 Change request

Project: Automated staff attendance system using facial Date: 17/11/19

recognition

Change Requester: Hajar Anis Change No: 001

Change Type: Major

Change Priority: High

Title: Size of database

Describe the change being requested:

The size of current database is full/ limited

Describe the reason for the change request:

The database size need to upgrade into a larger one, because there are several
new staffs that need to be registered

Schedule start: 19/11/19 -22/11/19

Change owner: Afif Mirza

Change Approver: Osamah

Change reviewer: Amir Khaidir

Disposition:
Approver

Justification of Approval, Rejection or deferral:

This should be fixed as it effect the stakeholder
 Change request

Project: Automated staff attendance system using facial Date: 13/11/19

recognition

Change Requester: Amir khaidir Change No: 005

Change Type: Major

Change Priority: High

Title: camera and sensor

Describe the change being requested: Change the camera to a new one with a
better quality image and provide a good sensor to detect the face quickly

Describe the reason for the change request: The camera and the sensor need to be
changed to a better one to make sure that the system can easily recognise people’s face
without stuttering.. It is also to make sure that the camera works efficiently.

Schedule start: 15/11/19 -18/11/19

Change owner: Osamah

Change Approver: Afif mirza

Change reviewer: Anis Nur Hajar

Statue:
Approved

Justification of Approval, Rejection or deferral:

This change has to be done immediately because it can affect the system to record the
staff’s attendance.
3.0 Software tool :
3.1 Service Desk Plus

Service Desk Plus is a web-based software tool which is a managing tool to

manage change requests. Service desk plus can be access via
(https://www.manageengine.com/products/service-desk/) . User must sign up for an
account to use the tool. Once account has been created, Service Desk Plus can be
use for 30 days of trial. After trials has ended, users must buy the software to
continue using it. It cost about $25/month for cloud server and $250/year for local
and private server.

Service Desk Plus helps to manage change request. It assign the change
owner, request approver. The admin can add team members and give them the
permeation to log in and make change requests as well as they can give the approval
if the request is assigned to them.

The tool has its own default workflow that show the change request
procedures. However, the admin can create their own workflow from the settings and
then they can apply it to change requests.

Figure 1: Default workflow

In addition the change request template is already existed in the tool however it can
be modified or the admin can create a new one.

Figure 2: Default change request template

3.3 How to use the tool:

After registration you will be redirected to the home page then you can start your
activities. Then choose the ‘change’ from the bar and press on the ‘new change’
button. The form in Figure 2 will be shown to you then fill up all the details. After
completion the details save it then the approver will keen on the acceptance of each
stage from the right side in the tool as shown in figure 4.
 Figure 4 Acceptance of each level
After finishing that part we can see the journey of the change request from the workflow
button which is on the right of the request title. See Figure 4.

Figure5 Example of the change request journey

To change or create new change request template or workflow, user should go to the setting
from the bar they will find (Template and forms ) then you can modify your own forms.
3.4 Apply the tool for the existing change requests:
After clicking on the change button the list of requested changes will be displayed as shown
in figure 6

Figure 6 list of changes requests

3.3.1 Change requests:
A. Database size:
B. Cost of the software system

C. Privacy of the attendance system

D. Camera & sensor

E. Feature extraction:
The report created by the tool:
A- Report by Priroty
B-Report by Change Type
C-Report by Urgency
4.0 References:

1. https://www.prosci.com/resources/articles/change-management-definition
2. https://www.guru99.com/software-configuration-management-tutorial.html

5.0 APPENDIX

Date Agenda Team members Attendance

11/15/19 -Online meeting 1. Afif Mirza All Attend

-Discussing about which 2. Anis Nur Hajar
tasks is assigned to each 3. Aida Farahanie
member. 4. Amir Khaidir
5. Osamah Ebrahim

11/17/19 -Online meeting 1. Afif Mirza All Attend

-Discussing the tool and 2. Anis Nur Hajar
the change requests 3. Aida Farahanie
4. Amir Khaidir
5. Osamah Ebrahim