database design document firefly dashboard

Provides database tables and the relationship between them.Description designing a database DB, a collection of data related to storage on a computer through database management system a

Group Project

CMU-CS 445 BIS

Database Design

Version 1.0 Date: 12/3/2024

Firefly Dashboard

Submitted by

Nguyen Thi Yen Nhi Dinh Viet Nhat Tan Tang Ngoc Tuan Ngo Le Hoang Approved by Huy Nguyen Dang Quang M.Sc.

Proposal Review Panel Representative:

Capstone Project 2-Mentor:

PROJECT INFORMATION Project

Lead

Project Mentor

Huy Nguyen Dang Quang

Email: huyndq@duytan.edu.vn

Tel: 0935525354

Project Leader

& contact

details

Tan Dinh Viet Nhat

Email:dinhvietnhattan@gmail.com

Tel: 0349920513

Partner

Organization

Project Web

URL

27211200906 Tan Dinh Viet

Nhat

dinhvietnhattan@gmail.com 0349920513

27201200414 Nhi Nguyen

27211223958 Tuan Tang

PROJECT PLAN DOCUMENT

Reporting

Period

March 2024

Author(s) &

project

Tan Dinh Viet Nhat , Project

Leader

Nhi Nguyen Thi Yen Member

Tuan Tang Ngoc Member

C2SE.08-DatabaseDesignDocument- OSM.docx

URL

DOCUMENT HISTORY

1 Introduction 1

1.1 Purpose 1

1.2 Document Objectives 1

1.3 Intended Audience 1

1.4 Scope 1

1.5 System Overview 2

1.6 Acronyms And Abbreviations 2

2 System Overview 2

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

4.1 Responsibility 3

4.2 Applications/Systems Using the Database 3

4.3 Physical Design 4

4.3.1 Detail table 4

5 Entity Mapping 13

6 References 15

LIST OF TABLES

Table 1: System Overview 2

Table 2: Acronyms And Abbreviations 2

Table 3: Database Software 3

Table 4: Support Software 3

Table 5: Responsibility 3

Table 6: Systems Using the Database 3

Table 7: Personal 4

Table 8: Job History 5

Table 9: Emergency Contacts 6

Table 10: Employment 7

Table 11: Benefit plans 8

Table 12: Migration History 8

Table 13: Employee 9

Table 14: Pay Rates 10

TABLE OF FIGURES

Figure 1 Entity Mapping 14

CMU 1

1 Introduction

1.1 Purpose

Setting up an overview about the database of Firefly web application

Provides database tables and the relationship between them

Description designing a database (DB), a collection of data related to storage on

a computer through database management system as a basis for data query related software

Provide the entire needed database for OSM web application

1.2 Document Objectives

The Database Design Document has the following objectives

To describe the design of a database, that is, a collection of related data stored

in one or more computerized files that can be accessed by users or developers via a DBMS

To serve as a basis for implementing the database and related software units It provides the acquirer visibility into the design and provides information necessary for software development

1.3 Intended Audience

This document is intended for the following audiences

Technical developers, who must evaluate the quality of this document Developer including:

o Architects, whose overall architecture design must meet the requirements specified in this document

o Designers, whose design must meet the requirements specified in this document

o Developers, whose software must implement the requirements specified in this document Quality Assurance personnel, whose test cases must validate the requirements specified in this document

1.4 Scope

This Database Design Document provides the basic database design of OSM web application

CMU 2

It describes both logical and physical definition, non-functional, database interfaces, tables, code create tables

It includes the tables and performance considerations and requirements The following topics are covered in this document:

o Assumptions and decisions on database design

o Entity – mapping

o Table, column definitions

o Column and row level validation rules (check constraints)

o Interfaces and dependencies with other components

This Database Design Document of Online Service Market web application is composed of definitions for database objects derived by mapping entities to tables, attributes to columns, unique identifiers to unique keys and relationship

to foreign keys

1.5 System Overview

Table 1: System Overview

1.6 Acronyms And Abbreviations

Table 2: Acronyms And Abbreviations

2 System Overview

2.1 Database Management System Configuration

- System: MS Windows

- Vendor: Digital Ocean

CMU 3

- Services enabled: Linux Virtual Machine

2.2 Database Software Utilities

Table 3: Database Software

Oracle

Corporation

MySQL

This application enables the ability

to manage MySQL database using GUI

SQL Server

management

studio

SQL Server 19 This application enables the ability

to manage SQL server database using GUI

2.3 Support Software

Table 4: Support Software

MySQL

Workbench 8.0 Generate ERD diagram of MySQL database. SQL Server

19

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

We use common dimensional tables for all the fact tables for better performance

4 Database Administrative Functions

4.1 Responsibility

Table 5: Responsibility

Database

Administrator

Tan Dinh Viet Nhat

dinhvietnhattan@gmail.co m

CMU 4

System and

Security

Administrator

4.2 Applications/Systems Using the Database

Table 6: Systems Using the Database

CMU 5

4.3 Physical Design

4.3.1 Detail table

4.3.1.1 Personal

The id is the primary key for Employee record

the Employee

Last Name nvarchar(50) True The Last Name of theEmployee.

the Employee Address1 nvarchar(50) True The Address 1 of theEmployee. Address2 nvarchar(50) True The Address 2 of theEmployee.

Employee live

State nvarchar(50) True The State whereEmployee live.

Employee

Employee

CMU 6

Phone Number nvarchar(50) True The phone number ofthe Employee. Social

Security_Numb

er

The Social Security Number of the Employee Drivers_Licens

The Driver's License

of the Employee

status

Employee Shareholder

Provide Shareholder status

the Employee

Ethnicity nvarchar(50) True The Ethnicity of theEmployee.

4.3.1.2 Job History

Table 8: Job History

ID

Int, autoIncrement PK False

The id is the primary key for Job History record

User identification number Foreign key to Employee.ID Department nvarchar(50) True Department of Job History

Division nvarchar(50) True Division of Job History

Start Date datetime True Date and time the recordwas created.

was ended

Job Title nvarchar(50) True Job Title of Job History

CMU 7

Supervisor nvarchar(50) True Supervisor of Job History

Job Category nvarchar(50) True Job Category of Job

History

Location nvarchar(50) True Location of Job History Departmen_C

Departmen Code of Job History Salary Type nvarchar(50) True Salary Type of Job History

Pay-Period nvarchar(50) True Pay-Period of Job History

Hours_per_W

Hours per Week of Job History

Hazardous

Job History has Hazardous Training or not 4.3.1.3 Emergency Contacts

Table 9: Emergency_Contacts

Employee_I

The id is the primary key for Emergency Contacts record Emergency_

Contact

Name

nvarchar(50) False Name of EmergencyContacts.

Phone

Phone Number of Emergency Contacts

Emergency Contacts

Table 10: Employment 5.

CMU 8

Employee_I

D

Int,

The id is the primary key for Employment record

Employmen

Hire Date datetime True Date and time the recordwas created. Workers_Co

Workers Comp Code of Employment Termination

Date and time the record was ended

was created again Last Review

was last updated

CMU 9

5.1.1.1 Benefit plans

7.

Benefit

Plan_ID

Int,

The id is the primary key for Benefit plans record Plan Name nvarchar(50) True The name of theBenefit plans.

Deductible Percentage_

7.1.1.1 Migration History

8.

Migrationld nvarchar(150) PK False

The id is the primary key for Migration History record

ContextKey nvarchar(150) PK False

Context Key is the primary key for Migration History record

CMU 10

9.

Model varbinary(MA

Model of Migration History ProductVers

Product Version of Migration History 9.1.1.1 Employee

1.1.1.1

s t r a i n t Nullable Description

idEmployee

Int,

F The id is the primary key for Employee record

Last Name

varchar(45) False Last Name of Employee

First Name varchar (45) False First Name of Employee.

Pay Rates identification number Foreign key to Pay_Rates.id

Vacation

Vacation Days of Employee

Paid Last

Paid Last Year of Employee

11

Figure 1 Entity

12

CMU 15

6 References

- Database Design.docx (Huy Nguyen Dang Quang)

- Payroll DB

- Human Resource DB