Jamaica Constabulary Force Human Resource Management System

Jameilia Jones 2100759, Shyhiem Barnes

School of Computing and Information Technology , University of Technology Jamaica

Software Engineering – CMP2019

Mr.Arnett Campbell

December 3, 2022
Date Version Description Author

30/11/2022 Version 1 Design Diagram Jameilia Jones

Shyiem Barnes

30/11/2022 Version 1 Database Design Brianna James

3NF

28/11/2022 Version 1 Architectural Brianna James

Diagrams

28/11/2022 Version 1 User Interface Jameilia Jones

Brianna James

1/12/2022 Version 1 Communication Brianna James

Interaction Diagram

1/12/2022 Version 1 Sequence Diagram Brianna James

27/11/2022 Version 1 System Quality Brianna James

Requirements
 Table of Contact

4. Data Requirements.........................................................................................................

DESIGN CLASS DIAGRAM...................................................................

DATABASE DESIGN(3NF)......................................................................

ARCHITECTURAL DIAGRAMS...............................................................

Technological Architecture Diagram .........................................................

Application Architecture (Three Layer) .....................................................

USER INTERFACE...............................................................................

Figure 1...............................................................................................

Figure 2...............................................................................................

Figure 3...............................................................................................

Figure 4...............................................................................................

Figure 5...............................................................................................

Figure 6...............................................................................................

5. System Quality Requirements..................................................................

5.1 ACCESSIBILITY..............................................................................

5.2 AUDITABILITY................................................................................

5.3 BRANDING.....................................................................................

5.4 CONFIGURABILITY..........................................................................

5.5 CORRECTNESS...............................................................................

5.6 EFFICIENCY...................................................................................

5.7 EXTENSIBILITY...............................................................................

5.8 INSTALLATION...............................................................................

5.9 INTEROPERABILITY.........................................................................

5.10 MAINTAINABILITY........................................................................
5.11 OPERATIONAL AVAILABILITY..........................................................

5.12 PERFORMANCE.............................................................................

5.13 PORTABILITY................................................................................

5.14 RELIABILITY.................................................................................

5.15 REUSABILITY................................................................................

5.16 ROBUSTNESS................................................................................

5.17 SAFETY........................................................................................

5.18 SCALABILITY................................................................................

5.19 SECURITY REQUIREMENTS.............................................................

5.2 Appendices.......................................................................................
4.1 Design Class Diagram
4.2 Database Design (3NF)

Table Attributes

Employee Badge_number ,trainingCourseCode, fName, lName, gender,

email,

HrPersonnel Hr_ID, address, dep.name, role_HR, phone_no, position_HR

Supervisor SupervisorID, supervisorRole

Accountant Act_ID, Act_name, ACDepName, Address, ACposition, role_num

Training trainingCourseCode, empID,

trainingCourseName,trainingTime,trainingDate, trainingDuration

Leave leaveID,leaveType, leaveDate, leaveDuration,remainingLeaveDay

LeaveRequest leaveID, empID, requestDate

Report Report#, date, employee_name

Payroll payslipNo, payAmount, payDate

WorkSchedule scheduleNo, empID, workDate, workTime

AttendanceRepor attendanceCode,empID, date, clockInTime, clockOutTime,

t totalHours
4.3 Architectural Diagrams

4.3.1 Technological Architectural Diagram

4.3.2 Application Architecture (Three Layer)s
4.4 User Interface

Figure 1: System Login Page

Figure 2: System Homepage
Figure 3: System Services being displayed

Figure 4: HR Manager clicks “Track Employee Attendance.

Figure 5: System retrieves and displays the attendance report for all employees
over that time period.

Figure 6: HR Manager clicks on an employee name.

4.5
Communication Interaction Diagram
4.5.1
Sequence Diagram
5. System Quality Requirements

5.1 Accessibility

The degree to which the system must be accessible to people with disabilities are specified in

this subsection:

● ACC-1) Persons with color blindness must be able to use JCF graphical

user interfaces.

● ACC-2) JCF graphical user interfaces must have a sufficient font size to be

usable for people with low vision.

● ACC-3) JCF graphical user interface can be used by people with impaired hearing

5.2 Auditability

This subsection outlines the following conditions for the system's ability to facilitate

independent

audits of its transactions and finances:

● AUD-1) The GPM must keep a record of each payroll for one year.

● AUD-2) The GPM must keep a record of each payslip for one year.

5.3 Branding

The following requirements for the degree to which the system must support the JCF

brands are specified in this subsection.

● Consistent theme across the system’s website.

5.4 Configurability

This subsection specifies the following requirements related to the system's ability to exist in
multiple concurrent configurations or variants:

5.4.1 Variant Capabilities

There are no requirements for multiple JCF HRM System variants.

5.4.2 Internationalization

There are no requirements for internationalization envisioned because the initial releases of

the JCF HRM System will be restricted to users within Jamaica.

5.4.3 Personalization

The degree of personalization remains to be determined.

5.5 Correctness

This subsection specifies the following requirements concerning the degree to which the

system

can contain defects and still be acceptable to the customer.

5.5.1 Latent Defects

This area specifies the requirements that concern the maximum number of allowable latent

defects in released work products.

● COR-1) The maximum number of latent bugs per unit of software shall not exceed TBD

for any release.

● COR-2) The maximum number of latent bugs by category should not exceed:

-Minor-TBD

-Significant=TBD

-Critical=TBD

● COR-3) The maximum number of tests that can fail when the system is shipped shall not

exceed TBD.

5.5.2 Accuracy
Below are the requirements that concern the degree of correctness of the system’s outputs:

● COR-4) Values of money should be correct to the nearest dollar.

● COR-5) Values of time should be correct to the nearest second

5.5.3 Precision

Below concerns the resolution of the JCF System numerical outputs

● COR-6) Values of money should be correct to the nearest dollar.

● COR-7) COR-5) Values of time should be correct to the nearest second

5.5.4 Timeliness

This subsection specifies the following requirements concerning the degree to which the

system

must ensure that its persistent information is current (i.e., up-to-date):

● COR-8) When one user updates some data, the system shall ensure that other users shall

automatically see the update within 3 seconds.

● COR-9) JCF HRM System will not return requested information to an external that is more

than one second obsolete.

● COR-10) The system shall automatically transfer “old” information from on-line storage

to off-line archives after TBD days.

● COR-11) The system shall permanently delete10 “obsolete” information from all storage

after TBD days.

5.6 Efficiency

This subsection specifies the following requirements associated with the degree to which

JCF System’s system effectively uses its resources:

● EFF-1) JCF System will require users to permanently download the required software to

their

computers.
5.7 Extensibility

This subsection specifies the following requirements associated with the degree to which the

system can be modified to meet changing requirements or goals.

● EXT-1) JCF System should be easily extendable to new employees for recruitment,

onboarding, and training.

● EXT-2) JCF System should be easily extensible to accommodate any amount of employees

without malfunction of the system.

5.8 Installation

This subsection specifies the following usability requirements associated with the ease with

which the system can be installed.

● INS-1) The average employee should not average more than 6 minutes to install or

upgrade any of JCF System’s software on his /her personal computer.

● INS-2) The user will be notified and informed about the requirements to download

JCF System’s software(e.g. operating system, memory).

● INS-3) It shall not average over 10 minutes to install or upgrade the software on

JCF System’s servers.

5.9 Interoperability

This subsection specifies the following requirements associated with the ease with which the

system can be integrated with other systems (e.g browser and required databases).

● JCF System will interoperate with the browsers listed below

-IOP-1) Microsoft Edge

-IOP-2) Google Chrome

-IOP-3) Safari

5.10 Maintainability

This subsection specifies the following requirements associated with the ease with which the
system can be maintained:

· M-1) JCF System will allow software upgrades without downtime.

· M-2) The Mean Time to Fix (MTTF) shall not exceed two persons per day.

5.11 Operational Availability

This subsection specifies the following requirements associated with the percent of time that

the

system must function correctly.

● OA-1) By release 0, JCF System shall provide the actors with a minimum operational

availability of 98%

● OA-1) By release 1, JCF System shall provide the actors with a minimum operational

availability of 99.9%

5.12 Performance

Here we will specify the requirements associated with the speed with which the system shall

function.

5.12.1 Capacity

● PER-1) The system shall support a minimum of 20,000 employees.

● PER-2) he system shall support a minimum of 10,000 employees for training.

5.12.2 Latency

This subsection specifies the following requirements concerning the maximum time that is

permitted for the system to execute specific tasks (i.e., system operations) or use case paths

end

to end:

● PER-3) The actors should be able to login to the system within two minutes

5.12.3 Response Time

This subsection specifies the following requirements concerning the maximum time that is
permitted for the system to respond to requests:

● PER-4) All system responses shall occur within 35 seconds

5. 12.4 Throughput

This subsection specifies the following requirements concerning how many executions of a

given

system operation or use case path must the system be able execute in a unit of time:

● To be determined (TBD)

5.13 Portability

This subsection specifies the following requirements associated with the ease with which the

system can be moved from one environment (e.g., hardware, operating system) to another.

JCF System will allow users to use the environments mentioned below to interact with the

system:

- Personal Computer:

-POR-1) PC with a minimum of 16 gb ram, SSD or hybrid storage and a 28.8K modem

-Operating Systems:

-POR-2) Windows 10

-POR-2) Windows 11

-POR-3) MAC OS

5.14 Reliability

This subsection specifies the following requirements associated with the reliability (e.g.,

mean

time between failures, number of failures per unit time) of the system.

● REL-1) The mean time between failures (MTBF) shall exceed 4 months.

5.15 Reusability

This subsection specifies the following requirements associated with the degree to which the
system can be used for purposes other than originally intended (e.g., as part of other

applications).

● REU-1) JCF System shall incorporate a database continuous availability layer.

● REU-3) The GPM shall reuse software for sending emails.

5.16 Robustness

This subsection specifies the following requirements associated with the degree to which the

system continues to properly function under abnormal circumstances.

● ROB-1) JCF System will handle all hardware failures and notify the system operator

of the issue instead of crashing.

● ROB-2) JCF System will verify inputs and detect all invalid inputs along with

requesting

valid inputs without the software crashing:

-human actors

-The Authorization Processor Gateway

5.17 Safety

This subsection specifies the following requirements associated with the degree to which the

system does not directly or indirectly (e.g., via inactivity) cause accidental harm to life or

property (e.g., loss of money or data).

● SAF-1 JCF System will store user data so that it is not lost

● SAF- 2 JCF System will notify user if there are any potential data threats or risk to

them

● SAF-3 The JCF System shall accurately calculate user fees.

5.18 Scalability

This subsection specifies the following requirements associated with the degree to which the
system can scale (e.g., can handle more simultaneous users or clients, can store more

information

in its databases).

● SCA-1) JCF System shall be able to scale as follows:

Release Total Employees

0 5000

1 10,000

2 20,000

5.19 Security Requirements

This subsection documents the security requirements that specify the extent to which the

Jamtive

Special shall protect itself and its sensitive data and communications from accidental,

malicious,

or unauthorized access, use, modification, destruction, or disclosure.

5.19.1 Identification Requirements

This subsection documents the identification requirements that specify the extent to which the

Jamtive shall identify its externals (e.g., human users and external applications) before

interacting with them:

Accountant – A minimum of 99.999% of the time, JCF System shall identify the accountant

before permitting him or her to perform the following accountant use cases:

● View Timesheet

● View Work Schedules

● Produce payroll

Employee – A minimum of 99.999% of the time, JCF System shall identify the employee
before permitting him or her to perform the following employee use cases:

● View/Update Personal Information

● Request Training

● Apply for leave from work

● Write/ Submit Report

● Clocks in/out

● View Payroll

Supervisor- A minimum of 99.999% of the time, JCF System shall identify the supervisor

before permitting him or her to perform the following supervisor use cases:

● Create Assessments

● Approve/Deny absence request

● Approve/Deny Training request

● Generate attendance report

● Generate training progress report

HR Manager- A minimum of 99.999% of the time, the JCF System shall identify the HR

manager before permitting him or her to perform the following HR manager use cases:

● Add employee personal information

● Retrieve/Update employee information

● Track employee attendance

● Track employee training progress

5.19.3 Authorization Requirements

This subsection documents the authorization requirements that specify the access and usage

privileges of authenticated users and client applications:

Accountant – A minimum of 99.999% of the time, JCF System shall restrict the
performance of all accountant use cases to persons who do not login with the proper

accountant

credentials.

Employee – A minimum of 99.99% of the time, JCF System shall restrict the performance of

the following employee use cases to persons who have successfully registered with the

appropriate employee credentials.

● View/Update Personal Information

● Request Training

● Apply for leave from work

● Write/Submit Report

● Clocks in/out

● View Payroll

Supervisor- A minimum of 99.99% of the time, JCF System shall restrict the performance of

the following supervisor use cases to persons who have successfully registered with the

appropriate supervisor credentials.

● Create Assessments

● Approve/Deny absence request

● Approve/Deny Training request

● Generate attendance report

● Generate training progress report

HR Manager- A minimum of 99.99% of the time, JCF System shall restrict the performance

of the following HR manager use cases to persons who have successfully registered with the

appropriate HR manager credentials.

● Add employee personal information

● Retrieve/Update employee information

● Track employee attendance

● Track employee training progress

5.19.4 Immunity Requirements

This subsection documents the immunity requirements that specify the extent to which the

JCF System shall protect itself from infection by unauthorized harmful programs or persons

(e.g.,hackers, computer viruses etc.):

● JCF System shall keep all platforms or scripts installed up-to-date

● JCF System will require strong passwords of least ten characters long and at least one

number and a special symbol.

● JCF System shall use SSL encryption on web pages.

● JCF System shall back up websites hourly

● Scanning – JCF System shall scan all entered or downloaded data and software

against the published definitions of known computer viruses, worms, Trojan horses, and

other similar harmful programs.

● Disinfection – If possible, JCF System shall disinfect any data or software found to

contain such a harmful program.

● Prevention – JCF System shall delete the infected file if it cannot disinfect the

infected data or software.

5.19.5 Integrity Requirements

This subsection documents the integrity requirements that specify the extent to which the

JCF System shall protect its data and communications from intentional corruption via

unauthorized creation, modification, or deletion:

● Communications – JCF System shall protect a minimum of 99.999% of its

communications from unauthorized intentional corruption during transit including

communications with the:

■ Regular Employees

■ Accountants

■ Supervisors

■ HR manager

5.19.6 Intrusion Detection Requirements

This subsection documents the intrusion-detection requirements that specify the extent to

which

JCF System shall detect attempted access or modification by unauthorized individuals or

programs:

● Repeated Authentication Failure – A minimum of 99.99% of the time, JCF System

shall block login within thirty seconds if it cannot successfully verify the identity of any

actor after five login attempts.

5.19.7 Non Repudiation Requirements

This subsection documents the nonrepudiation requirements that specify the extent to which

the

JCF System shall prevent a party to one of its interactions from denying having participated

in all or part of the interaction:

Accountant:

Generate Payroll – A minimum of 99.999% of the time that an accountant generates payroll,

JCF System shall make and store a tamper-proof record including the following information:

● Accountant name

● Accountant ID

● Date
● time

5.19.8 Privacy Requirements

The privacy goal of JCF System is to ensure the confidentiality of all information entrusted

to it, whether stored or communicated, except for such information that an operational

requirement explicitly makes public.

The following privacy requirements specify the extent to which JCF System shall support

anonymity and keep its confidential data and communications private from unauthorized

individuals and programs.

User Privacy – A minimum of 99.999% of the time, the JCF System shall restrict access as

indicated to the following confidential user information, whether communicated or stored:

● Financial Information (restricted to the user and accountants):

○ Payslip

● Password Information (restricted to the user):

○ Password

○ Password Confirmation

● Postal Address (restricted to the user and HR manager):

○ Street Number

○ Street Name

○ Parish

● Telephone Number (restricted to the user and HR manager)

5.19.9 Security Auditing Requirements

This subsection specifies the following privacy requirements:

TBD

5.19.10 Survivability Requirements

This subsection specifies the following privacy requirements:

TBD

5.19.11 Physical Protection Requirements

This subsection specifies the following privacy requirements:

TBD

5.19.12 System Maintenance Security Requirements

This subsection specifies the following system-maintenance requirements:

● JCF System shall ensure that authorized modifications during maintenance will not

inadvertently allow unauthorized individuals access to the system.

5.2 Appendices
This section documents the following appendix:
● Envisioned Future Enhancements
● Elicitation tools

Envisioned Future Enhancements

TBD

Elicitation tools

● ● Interviews: The interview predictor discusses the requirement of the product and

gets an exclusive view of the entire system. The purpose of the interview is to

investigate and understand how the expert selects the requirement engineering

process.

Questions:

Which processes of a human resource department would require automation? Based

on a human resource management system you are aware of, what are some

improvements that could be made to increase productivity?

 What are some of the functionalities that are necessary in a payroll system? When

calculating payroll, what are some of the necessary components and why?

● ● Brainstorming: In Brainstorming, each team member can express his own idea

about the product. It is very effective and commonly used to arrive at the most

important verdict regarding the product.