database design hr and payroll system

Capstone Database Design v2.0 – OSM PROJECT PLAN DOCUMENTDocument Title Project Plan ReportingMarch 2023 Authors &project Lam Nguyen Truong, Scrum MasterSon Nguyen Ngoc Member Huy Tong P

Huy Tong Phuoc Lam Nguyen Truong

Son Nguyen Ngoc Huy Dang Ngoc

Quan Approved by

Huy Nguyen Dang Quang M.Sc.

Proposal Review Panel Representative:

Capstone Project 2-Mentor:

PROJECT INFORMATION Project Acronym PMS

Project Title KidsLand

Lead Institution The Faculty of Information Technology, Duy Tan University Project Mentor MSc Huy Nguyen Dang Quang

Product Owner &

Son Nguyen Ngoc captianson@gmail.com 0326298990 Huy Tong Phuoc tonghuy176@gmail.com 0327501094 Huy Dang Ngoc

huydang080602@gmail.co m

0898210504

Capstone Database Design v2.0 – OSM PROJECT PLAN DOCUMENT

Document Title Project Plan Reporting

March 2023 Author(s) &

project Lam Nguyen Truong, Scrum Master

Son Nguyen Ngoc Member Huy Tong Phuoc Member

DOCUMENT HISTORY

Capstone Database Design v2.0 – OSM

2.1 Database Management System Configuration 2

2.2 Database Software Utilities 3

2.3 Support Software 3

3 Database-Wide Design Decisions 3

3.1 Key Factors Influencing Design 3

3.2 Performance And Availability Decisions 3

4 Database Administrative Functions 3

LIST OF TABLES

Table 1: System Overview 2

Table 2: Acronyms And Abbreviations 2

Table 3: Database Software 3

Table 4: Support Software 3

Capstone Database Design v2.0 – OSM

TABLE OF FIGURES

Figure 1 Entity Mapping 14

C2SE.08 8 1 Introduction

1.1 Purpose

The database design document aims to provide a comprehensive overview of the database structures for the HR (Human Resources) and Payroll systems within the Online Service Market (OSM) web application It delineates the tables and their interrelationships, serving as the backbone for efficient data management and processing Furthermore, it elucidates the significance of databases in storing and organizing essential HR and payroll-related information, vital for effective workforce management and financial operations.

1.2 Document Objectives

This document seeks to achieve several objectives:

To outline the design of the HR and Payroll databases, elucidating their roles as repositories of employee-related data and financial information.

To serve as a reference guide for implementing and maintaining the databases, ensuring alignment with the requirements of the OSM web application.

To provide insight into the database design for technical developers, architects, designers, developers, and quality assurance personnel involved in software development and testing.

1.3 Intended Audience

The document caters to a diverse audience, including:

Technical developers responsible for evaluating, implementing, and maintaining the HR and Payroll databases.

Architects tasked with designing the overall architecture of the databases to meet the requirements specified in this document.

Designers involved in crafting the database schemas and data models based on the outlined specifications.

Developers responsible for implementing the database design and ensuring compliance with the document's requirements.

Quality assurance personnel tasked with validating the database design through test cases to ensure functionality and reliability.

1.4 Scope

The Database Design Document encompasses the following scope for the HR and Payroll databases:

Logical and physical definitions of the database structures, including tables, relationships, and data attributes.

Non-functional considerations such as performance, scalability, and security requirements.

Description of database interfaces and dependencies with other components of the OSM web application.

Capstone Database Design v2.0 – OSM

Assumptions and decisions guiding the database design process Entity-to-table mappings, column definitions, and validation rules.

Identification of unique keys and foreign keys to maintain data integrity and enforce referential integrity constraints.

1.5 System Overview

Table 1: System Overview

1.6 Acronyms And Abbreviations

Table 2: Acronyms And Abbreviations

RDMS Relational atabase anagement D M System

C2SE.08 10 - Services enabled: Linux Virtual Machine

2.2 Database Software Utilities

Table 3: Database Software

Oracle Corporation

This application enables the ability to manage MySQL database using GUI.

2.3 Support Software

Table 4: Support Software

Workbench 8.0 Generate ERD diagram of MySQL database. 3 Database-Wide Design Decisions

3.1 Key Factors Influencing Design

- The database should be designed independent when the frontend and backend are still being developed.

- The database should be designed to meet the data warehouse principles 3.2 Performance And Availability Decisions

We use common dimensional tables for all the fact tables for better performance 4 Database Administrative Functions

Huy Tong Phuoc

4.2 Applications/Systems Using the Database

Table 6: Systems Using the Database

Capstone Database Design v2.0 – OSM

each employee, of integer type.

An integer field serving as the primary key for employee identification.

name of the employee, with a maximum length of 45 characters.

first name of the employee, also with a maximum length of 45 characters.

representing the Social Security Number of the employee.

the pay rate of the employee This field is nullable, allowing for flexibility in recording pay rates.

Pay Rates_idPay

False An integer field serving as the primary key for pay

C2SE.08 12 rates.

the number of vacation days accrued by the employee This field is nullable.

representing the total amount paid to the employee in the current year, up to the current date.

representing the total amount paid to the employee in the previous year 4.3.1.2 Pay Rates

Table 8: Pay Rates

the primary key for each pay rate entry.

Pay Rate Name

VARCHAR(40)

A varchar field specifying the name or label of the pay rate, with a maximum length of 40 characters.

representing the base value of the pay rate.

the tax percentage applied to this pay rate.

Capstone Database Design v2.0 – OSM

the type of pay.

representing the total pay amount associated with this pay rate.

PT – Level C

indicating additional pay or adjustments for specific conditions This field is nullable.

Table 1: Employee

Unique identifier to an individual in the database

First name of the individual

Last name of the individual

Middle name or initial of the individual

Date of birth of the

Primary address of the individual

Secondary address line of the individual, if applicable.

City of the individual's

C2SE.08 14

ZIP or postal code of the individual's current address

CURRENT_GENDER nvarchar(20) Checked Gender identity of the individual.

Phone number of the individual.

Personal email address of the individual.

Marital status of the individual (e.g., single,

Indicates whether the individual is a shareholder in a company or organization.

Identifier for the benefit plan(s) the individual is enrolled in.

Table 2: Benefit plans

BENEFIT_PLANS_ID numeric(18, 0) PK Unchecked

Unique identifier or each benefit plan.

PLAN_NAME nchar(10) Checked Name or title of the benefit plan

The amount of money that an individual must pay out of pocket before their insurance coverage kicks in.

The percentage of costs for covered services that an individual is required to pay after meeting

Current status of the individual's employment.

Capstone Database Design v2.0 – OSM

Date when the individual was hired for employment.

Code indicating the type of workers' compensation coverage associated with the employment

Date when the individual's employment was terminated, if applicable

Date when the individual was rehired after termination, if applicable.

Date of the individual's last performance review or evaluation.

NUMBER_DAYS_REQUIREMENT_O F_

The number of days required for the individual to work per month as per their

Identifier linking the job history record to the corresponding employment record.

Department within the organization where the individual worked.

Division or subgroup within the organization where the individual worked.

JOB_TITLE nvarchar(250) Checked Title or designation of the job position SUPERVISOR nvarchar(250) Checked Name or identifier of the supervisor

C2SE.08 16 overseeing the individual in the job position.

Location or site where job position was based.

Description or categorization of the type of work performed in the job position.

Table 5: Employment working time

Unique identifier for each record related to

The year for which the working time information is recorded.

The month for which the working time information is recorded.

The actual number of days the individual worked during the specified month TOTAL_NUMBER_VACATION_

The total number of vacation days taken by the individual during the specified month.

5 Entity Mapping

Capstone Database Design v2.0 – OSM

C2SE.08 15 6 References

- [SDA] 006 Database Design.docx (Man, Nguyen Duc) - https://drawsql.app/teams/dac-1/diagrams/osm