1

Comprehensive Database Design and Implementation for Unified Products and

Services: Enhancing Operational Efficiency and Promoting Entrepreneurship in the

Philippines

Sean Endriga and Richard Vincent Gonzales

Caraga State University

ITE 16 - Database Management Systems

Mr. Edwin Manuel Jalarta

July,6,2024

Abstract

Unified Products and Services (Unified) offers a comprehensive range of services including
ticketing, remittance, bills payment, e-loading, insurance, travel and tours, and ferry booking.
This case study aims to analyze the business processes and data requirements of Unified, with
the objective of designing and implementing a relational database to support the company’s
operations efficiently. The scope includes understanding the key processes involved in booking
services, identifying necessary data entities, designing an ER diagram, implementing the
database, and testing its functionality. This study highlights the importance of a well-designed
database in promoting entrepreneurship and providing legitimate business opportunities in the
Philippines.

Keywords: Unified Products and Services, relational database, business processes, data

requirements, ER diagram

Introduction
 2

Comprehensive Database Design and Implementation for Unified Products and

Services: Enhancing Operational Efficiency and Promoting Entrepreneurship in the

Philippines

Background of the Study

Unified Products and Services (Unified) is a comprehensive business solution provider offering a

wide range of services, including ticketing, remittance, bills payment, e-loading, insurance,

travel and tours, ferry booking, and more. The company aims to provide a one-stop-shop

experience for its clients, streamlining various essential services into a single platform. Unified's

primary goal is to promote entrepreneurship and provide legitimate business opportunities to

every Filipino, emphasizing the importance of joining reputable companies.

Objectives and Scope of the Case Study

The objective of this case study is to analyze the business processes and data requirements of

Unified Products and Services. By doing so, the study aims to design and implement a relational

database that supports the company's operations efficiently. The scope includes understanding

the key processes involved in booking services, identifying necessary data entities, designing an

ER diagram, implementing the database, and testing its functionality.

Objectives

● Clear statement of what the case study aims to achieve:

○ Analyze the business processes of Unified Products and Services.

○ Identify and describe the data entities involved.

○ Design and implement a relational database to support these processes.

 3

○ Test and validate the database implementation to ensure it meets operational

needs.

Process Flow Overview

Detailed Description of Key Processes:

1. Booking Process:

○ Collect client details, including valid ID.

○ Process payment for the ticket.

○ Book the flight and confirm the itinerary.

○ Send the confirmed itinerary to the client.

2. Data Management:

○ Maintain customer and agent records.

○ Track bookings and payments.

○ Ensure data integrity and security.

Data Requirements and Entities

Identification and Description of Entities:

● Customer
 4

○ Attributes: Customer ID, Customer Name, Valid ID, Customer Address, Customer

Contact Information

○ Rationale: Captures essential information about the customer to facilitate

communication and order fulfillment processes.

● Travel Agent

○ Attributes: Agent Registration Code, Agent Name, Agent Email, Agent Rank,

Agent Contact Information

○ Rationale: Recording essential information about the Travel Agent that will be

assisting the customer for booking flights.

● Unified App

○ Attributes: App Name, Agent Registration Code, Customer ID, Book Flight, Issue

Ticket

○ Rationale: Storing valuable information about the booked tickets, customer, and

including the agent.

ER Diagram Design

Presentation and Explanation of the Entity-Relationship (ER) Diagram:

The ER diagram illustrates the relationships between the entities Customer, Travel Agent, and

Unified App. It shows how the attributes of each entity are related and how they interact within

the database.

1. Travel Agent - Customer

• Relationship Type: One-to-many

2. Travel Agent - Unified App

 5

• Relationship Type: One-to-many

 6

ER Model Vs Relational Model

The distinction between the ER model and the Relational Model is that the ER model describes

the relationship between entities and their attributes. On the other hand, the Relational Model

referred to the implementation of our model. The Relational Model is the implementation or

representational model, while the ER Model is the high-level or conceptual model. The data in

components such as entity sets, relationship sets, and attributes are represented by an ER model.

The Relational model, on the other hand, defines data in components such as tuples, attributes,

and attribute domains. As compared to a Relational Model, an ER model makes it easier to

understand the relationships between entities.

Mapping Cardinality is always a constraint in the ER model, while the cardinality constraint

cannot be defined in the Relational Model.

Classification and Relational of Entities and Attributes

Customer

Attributes: Customer ID: Unique identifier for each customer.

Customer Name: The name of the customer.

Valid ID: For the authentication of the customer.

Customer Address: The address of the customer.

Customer Contact Information: The customer's phone number to quickly reach out.

Rationale: Captures essential information about the customer to facilitate

communication and order fulfillment processes.

 7

Travel Agent

Attributes: Agent Registration Code: A unique identifier for each agent.

Agent Name: The name of the agent.

Agent Email: The email of the agent.

Agent Rank: The rank of the agent in the business.

Agent Contact Information: The agents' phone number for quick communication.

Rationale: Recording essential information about the Travel Agent that will be assisting the

customer for booking flights.

Unified App

Attributes: App Name: Name of the application.

Agent Registration Code: Identifier linking to the agent.

Customer ID: Identifier linking to the customer.

Book Flight: Flight booked by the Agent.

Issue Ticket: Status of the ticket booked.

Rationale: Storing valuable information about the booked tickets, customer and including the

agent.Last Name

CREATE TABLE Travel_Agent (

AgentRegistrationCode VARCHAR(20) PRIMARY KEY,

 8

AgentName TEXT,

AgentEmail VARCHAR(100),

AgentRank TEXT,

AgentContactInformation NUMERIC(11)

);

CREATE TABLE Customer (

CustomerID INT PRIMARY KEY,

CustomerName TEXT,

ValidID TEXT,

CustomerAddress VARCHAR(100),

CustomerContactInformation NUMERIC(11)

);

CREATE TABLE Unified_App (

AppName TEXT PRIMARY KEY,

AgentRegistrationCode VARCHAR(20),

CustomerID INT,

BookFlight VARCHAR(100),

IssueTicket VARCHAR(100),

FOREIGN KEY (AgentRegistrationCode) REFERENCES

Travel_Agent(AgentRegistrationCode),

FOREIGN KEY (CustomerID) REFERENCES Customer(CustomerID)

 9

);

-- Insert Mock Data

INSERT INTO Travel_Agent (AgentRegistrationCode, AgentName, AgentEmail, AgentRank,

AgentContactInformation) VALUES

('TA001', 'John Doe', 'john.doe@example.com', 'Senior', 12345678901),

('TA002', 'Jane Smith', 'jane.smith@example.com', 'Junior', 23456789012),

('TA003', 'Emily Johnson', 'emily.johnson@example.com', 'Senior', 34567890123);

INSERT INTO Customer (CustomerID, CustomerName, ValidID, CustomerAddress,

CustomerContactInformation) VALUES

(1, 'Alice Brown', 'ID123456', '123 Elm Street', 45678901234),

(2, 'Bob White', 'ID789012', '456 Oak Street', 56789012345),

(3, 'Charlie Black', 'ID345678', '789 Pine Street', 67890123456);

INSERT INTO Unified_App (AppName, AgentRegistrationCode, CustomerID, BookFlight,

IssueTicket) VALUES

('App1', 'TA001', 1, 'Flight A1', 'Ticket A1'),

('App2', 'TA002', 2, 'Flight B2', 'Ticket B2'),

('App3', 'TA003', 3, 'Flight C3', 'Ticket C3'),

('App4', 'TA001', 2, 'Flight D4', 'Ticket D4'),

('App5', 'TA002', 1, 'Flight E5', 'Ticket E5');

Testing and Validation

 10

Methods Used to Test and Validate the Database Implementation:

1. Data Integrity Checks: Verify that relationships between tables are correctly enforced.

2. Functional Testing: Test the database with various queries to ensure it supports all

necessary operations (e.g., booking a service, processing a payment).

3. Performance Testing: Evaluate the database performance under different loads to ensure

it can handle expected usage.

Conclusion

Summary of Key Findings and Outcomes:

The case study successfully mapped out the key business processes and data requirements of

Unified Products and Services. The ER diagram accurately represented the relationships between

the entities involved. The implemented relational database in MySQL (or PostgreSQL) was

tested and validated, confirming it meets the company's operational needs. This study

demonstrates the importance of a well-designed database in supporting efficient business

operations and promoting entrepreneurship through legitimate business opportunities.

 11

What is unified all about?

-Unified Products and Services is a one stop shop business with Ticketing, Remittance, Bills

Payment, E loading, Insurance, Travel & Tours, Ferry Booking & many more.

What is the process in booking?

 12

When processing bookings first you have to get the details of the client including her/his Valid

ID. Send her/his payment for the ticket, then proceed for booking the flight. After confirmation

the confirm itinerary will be sent to a client.

What is the objective of unified?

Unified objective is to encourage Entrepreneurship, legitimate Business opportunities for Every

FILIPINO."

The most important thing is you join the legitimate Company! And Unified is one of those!