Mapua University

Bachelor of Science in Information Technology

Information Systems Laboratory

DATABASE MODEL PROPOSAL FOR

GLOBAL COMPUTER SOLUTIONS (GCS)

Andrea Melyn C. Catalan

April 2023
 I. An Introduction to Global Computer Solutions

- Global Computer Solutions (GCS) is a renowned IT consulting company in

the US with multiple locations that provides excellent client services. GCS

successfully matches its talented employees to projects in specific

regions. This enables them to use local knowledge to offer customized

solutions to clients. The GCS team consists of highly skilled technology

professionals with extensive knowledge and experience in the industry.

They focus on ensuring clients are satisfied with their services by

delivering quality work and putting the client's needs first. As a result,

many businesses looking for IT solutions choose GCS as their preferred

company.

II. Proposal of new Database and Entity Relationship Diagram

- A new database and ERD were recently requested and proposed by the

head of Global Computers Solutions to have a more updated and more

modern take on managing the flow of their work and the relationship

between the entities in the company’s database. Furthermore, they also

requested to design a new database and ERD to better manage their own

projects and keep track of the data of their customers, employees,

projects, project schedules, assignments, and invoices.

III. Importance of Databases and ERDs

- Databases and ERDs are essential based on the following concepts:

● Databases offer a way to store and organize a large amount of data

in a structured manner, enabling quick and efficient searching,

 sorting, and retrieval of information.(Ramakrishnan & Gehrke,

2003)

● By only allowing valid data to be entered into the system,

databases ensure that data consistency and integrity are

maintained, preventing errors and discrepancies (Elmasri &

Navathe, 2020) .

● Data security is a critical aspect of databases, with security features

that protect sensitive information from unauthorized access and

malicious attacks (Ozsu & Valduriez, 2011).

● Databases facilitate data sharing among multiple users, allowing for

collaboration and better communication among team

members(Silberschatz, Korth, & Sudarshan, 2010).

● By analyzing data, databases can provide valuable business

insights to inform decision-making and improve business

performance(Kimball & Ross, 2013).

● ERDs visually represent the relationships between entities in a

database, making it easier to understand and communicate the

database structure and streamlining the design process(Connolly &

Begg, 2015).

IV. Provided Tables from GCS

- The Skills Inventory table provides information about the skills possessed

by each employee in the organization. Each employee is associated with

multiple skills, and some skills are shared by multiple employees. The
 table includes a unique skill ID, a detailed description of each skill, and the

rate of pay associated with it. The following valid skills are included in the

table: data entry I, data entry II, systems analyst I, systems analyst II,

database designer I, database designer II, Cobol I, Cobol II, C++ I, C++ II,

VB I, VB II, ColdFusion I, ColdFusion II, ASP I, ASP II, Oracle DBA, MS

SQL Server DBA, network engineer I, network engineer II, web

administrator, technical writer, and project manager. An example of the

Skills Inventory table is provided in Table 1.

SKILL EMPLOYEE

Data Entry I Seaton Amy; Williams Josh; Underwood Trish

Data Entry II Williams Josh; Seaton Amy

Systems Analyst I Craig Brett; Sewell Beth; Robbins Erin; Bush Emily; Zebras
Steve

Systems Analyst II Chandler Joseph; Burklow Shane; Robbins Erin

DB Designer I Yarbrough Peter; Smith Mary

DB Designer II Yarbrough Peter; Pascoe Jonathan

Java I Kattan Chris; Epahnor Victor; Summers Anna; Ellis Maria

Java II Kattan Chris; Epahnor Victor, Batts Melissa

C++ I Smith Jose; Rogers Adam; Cope Leslie

C++ II Rogers Adam; Bible Hanah

Python I Zebras Steve; Ellis Maria

Python II Zebras Steve; Newton Christopher

ColdFusion I Duarte Miriam; Bush Emily

ColdFusion II Bush Emily; Newton Christopher

ASP I Duarte Miriam; Bush Emily

ASP II Duarte Miriam; Newton Christopher

Oracle DBA Smith Jose; Pascoe Jonathan

SQL Server DBA Yarbrough Peter; Smith Jose

Network Engineer I Bush Emily; Smith Mary

Network Engineer II Bush Emily; Smith Mary

Web Administrator Bush Emily; Smith Mary; Newton Christopher

Technical Writer Kilby Surgena; Bender Larry

Project Manager Paine Brad; Mudd Roger; Kenyon Tiffany; Connor Sean
Table 1.1 Skills Inventory

- To effectively manage a project, the project manager is responsible for

creating a project schedule that acts as a roadmap for the design and

development process. This schedule outlines the individual tasks required

to take the project from start to finish, including a task ID, a brief task

description, the task’s start and end date, the necessary skill set required

for each task, and the number of team members with the relevant skills

required to complete each task. Common tasks included in the project

schedule are initial interviews, database and system design,

implementation, coding, testing, and final evaluation and sign-off. For

instance, an example project schedule for GCS is illustrated in Table 2.

Project ID: 1 Description: Sales Management System

Company: SeeRocks Contract Date: 2/12/2006 Region: NW
Start Date: 3/1/2006 End Date: 7/1/2006 Budget: $15,500

START END TASK DESCRIPTION SKILL REQUIRED QTY.

DATE DATE REQUIRED

3/1/06 3/6/06 Initial Interview Project Manager 1

Systems Analyst II
DB Designer I
 3/11/06 3/15/06 Database Design DB Designer I 1

3/11/06 4/12/06 System Design Systems Analyst II 1

Systems Analyst I

3/18/06 3/22/06 Database Implementation Oracle DBA 1

3/25/06 5/20/06 System Coding & Testing Cobol I 1

Cobol II
Oracle DBA

3/25/06 6/7/06 System Documentation Technical Writer 1

6/10/05 6/14/05 Final Evaluation Project Manager 1

Systems Analyst II
DB Designer I
Cobol II

6/17/05 6/21/05 On-Site System Online and Data Project Manager 1

Loading Systems Analyst II
DB Designer I
Cobol II

7/1/05 7/1/05 Sign-Off Project Manager 1

Table 2 Project Schedule Form

- From the preceding information, it is evident that employees are linked to

specific project tasks through the project schedule. To maintain an

accurate record of such assignments, we require certain key information,

including the assignment ID, the name of the employee, the project

schedule task, and the start and end dates of the assignment, which may

vary based on the project timeline. An example assignment form is

provided in Table 3.

Project ID: 1 Description: Sales Management System

Company: SeeRocks Contract Date: 2/12/2006 As of: 03/29/06

SCHEDULED ACTUAL ASSIGNMENTS

Project Start End Skill Employee Start End

Task Date Date Date Date
Initial Interview 3/1/06 3/6/06 Project Mgr. 101—Connor S. 3/1/06 3/6/06
Sys. Analyst II 102—Burklow S. 3/1/06 3/6/06
DB Designer I 103—Smith M. 3/1/06 3/6/06

Database 3/11/06 3/15/06 DB Designer I 104—Smith M. 3/11/06 3/14/06

Design

Database 3/11/06 4/12/06 Sys. Analyst II 105—Burklow S. 3/11/06

Design Sys. Analyst I 106—Bush E. 3/11/06
Sys. Analyst I 107—Zebras S. 3/11/06

Database 3/18/06 3/22/06 Oracle DBA 108—Smith J. 3/15/06 3/19/06

Implementation

System Coding 3/25/06 5/20/06 Cobol I 109—Summers A. 3/21/06

& Cobol I 110—Ellis M. 3/21/06
Testing Cobol II 111—Epahnor V. 3/21/06
Oracle DBA 112—Smith J. 3/21/06

System 3/25/06 6/7/06 Tech. Writer 113—Kilby S. 3/25/06

Documentation

Final 6/10/06 6/14/06 Project Mgr.

Evaluation Sys. Analyst II
DB Designer I
Cobol II

On-Site System 6/17/06 6/21/06 Project Mgr.

Online and Sys. Analyst II
Data DB Designer I
Loading Cobol II

Sign-Off 7/1/06 7/1/06 Project Mgr.

Table 3 Project Assignment Form

- The actual hours worked by an employee on a given assignment are

recorded in a work log, which is a weekly form filled out by the employee

every Friday or at the end of each month. The form includes the date

(which is either each Friday of the month or the last day of the month if it

doesn't fall on a Friday), the assignment ID, the total hours worked during
 the week (or up to the end of the month), and the billing number to which

the work log entry is attributed. It is important to note that each work log

entry can be linked to only one billing number. A list of current work log

entries for the first sample project can be seen in Table 4.

Employee Week Assignment Hours Bill

Name Ending Number Worked Number

Burklow S. 3/1/06 1-102 4 xxx

Connor S. 3/1/06 1-101 4 xxx

Smith M. 3/1/06 1-103 4 xxx

Burklow S. 3/8/06 1-102 24 xxx

Connor S. 3/8/06 1-101 24 xxx

Smith M. 3/8/06 1-103 24 xxx

Burklow S. 3/15/06 1-105 40 xxx

Bush E. 3/15/06 1-106 40 xxx

Smith J. 3/15/06 1-108 6 xxx

Smith M. 3/15/06 1-104 32 xxx

Zebras S. 3/15/06 1-107 35 xxx

Burklow S. 3/22/06 1-105 40 xxx

Bush E. 3/22/06 1-106 40 xxx

Ellis M. 3/22/06 1-110 12 xxx

Epahnor V. 3/22/06 1-111 12 xxx

Smith J. 3/22/06 1-108 12 xxx

Smith J. 3/22/06 1-112 12 xxx

Summers A. 3/22/06 1-109 12 xxx

Zebras S. 3/22/06 1-107 35 xxx

Burklow S. 3/29/06 1-105 40 xxx

Bush E. 3/29/06 1-106 40 xxx

Ellis M. 3/29/06 1-110 35 xxx

Epahnor V. 3/29/06 1-111 35 xxx

Kilby S. 3/29/06 1-113 40 xxx

Smith J. 3/29/06 1-112 35 xxx

Summers A. 3/29/06 1-109 35 xxx

Zebras S. 3/29/06 1-107 35 xxx

 V. Entity Relationship Diagram

The relationship between the tables are as follows:

o REGION_ID in EMPLOYEE table is a foreign key that references REGION_ID in

REGION table.

o REGION_ID in CUSTOMER table is a foreign key that references REGION_ID in

REGION table.

o SKILL_ID in EMPLOYEE_SKILL table is a foreign key that references SKILL_ID in

SKILL table.

o EMPLOYEE_ID in EMPLOYEE_SKILL table is a foreign key that references EMP_ ID

in EMPLOYEE table.

o PROJECT_ID in PROJECT_ SCHEDULE _TASK table is a foreign key that

references PROJECT_ID in PROJECT table.

o CUSTOMER_ID in PROJECT table is a foreign key that references CUSTOMER_ID

in CUSTOMER table.

o TASK_ID in TASK_SKILLS table is a foreign key that references TASK_ID in

PROJECT_ SCHEDULE _TASK table.

o EMPLOYEE_ID in ASSIGNMENT table is a foreign key that references EMP_ID in

EMPLOYEE table.

o PROJECT_ID in ASSIGNMENT table is a foreign key that references PROJECT_ID in

PROJECT table.

o TASK_ID in ASSIGNMENT table is a foreign key that references TASK_ID in

PROJECT_ SCHEDULE _TASK table.

o EMPLOYEE_ID in WORK_LOG table is a foreign key that references EMP_ ID in

EMPLOYEE table.

o PROJECT_ID in TASK_SKILLS table is a foreign key that references PROJECT_ID in

PROJECT table.
VI. Conclusion