HANDYMAN SERVICE SYSTEM

DATABASE MANAGEMENT SYSETEM PROPOSAL

TABLE OF CONTENTS

01 Introduction

02 Business Requirements

03 Database Design

04 UI Application
INTRODUCTION

In today's fast-paced world, the demand for efficient

and reliable handyman services is on the rise.
However, managing a business in this industry can be
quite challenging without the right tools. By utilizing a
database management system, handyman service
providers can easily track and manage their
appointments, assign tasks to their technicians, and
keep a record of completed jobs.
BUSINESS REQUIREMENTS

There are several requirements and expectations for this

project. Requirements currently include:

(1) Customers must see their personal information,

appointed schedule, and mode of payment.

(2) The handyman must see the customer's address, mode

of payment, and the date appointed.

(3) Provide managers to access all handyman, customer’s

input and generate a report.

(4)Allow the owner to access reports from the manager.

(5)The supplier must see the inventory for resupply.

BUSINESS
REQUIREMENTS

Some expectations are:

(1) Automatically updated when there's a change in

customer information.

(2) Create a secure database so customer data is not

accessed by unauthorized individuals or organizations.

(3) Have a secured payment transactions

BUSINESS
REQUIREMENTS

Table 1. Database Requirements

This table illustrates the business requirements related to the database design.
DATABASE DESIGN | Conceptual Model

Figure 1. Database Conceptual Tables.

In the Conceptual Model we can see in the figure 1 linking within different tables. This model provides the snapchat of the
relationships between entities.
DATABASE DESIGN | Logical Model

Figure 2. Database Logical Tables

In this model it will be include the entities, attributes, relationship, Primary Key and Foreign Keys. The Primary Key in the Entities
is represented by the Logical Model, and the relationship is one-to-one.
DATABASE DESIGN | Physical Design

Table 2.1 Appointment Table.

DATABASE DESIGN | Physical Design

Table 2.2 Client Table.

DATABASE DESIGN | Physical Design

Table 2.3 Handyman Table.

DATABASE DESIGN | Physical Design

Table 2.4 Inventory Table.

DATABASE DESIGN | Physical Design

Table 2.5 Login Table.

DATABASE DESIGN | Physical Design

Table 2.6 Owner Table.

DATABASE DESIGN | Physical Design

Table 2.7 Repair History Table.

DATABASE DESIGN | Physical Design

Table 2.8 Roles Table.

DATABASE DESIGN | Physical Design

Table 2.9 User Table.

U I A P P L I C A T I O N | Flowchart
THANK YOU FOR
LISTENING

Members Jhay Vic G. Ambata

John Robert Lunca

France Lawrence F. Sunguad