4-person project presentation

ManufacturerSystem

PHP web app · Oracle 21c XE database · Shared CSS interface

PHP Oracle 21c XE CRUD Relational DB SQL
Presenters  ·  Reign  ·  Angelo  ·  Jhun  ·  Cervales
scroll
Speaker — Reign
01 / Introduction

System Overview
& Database Design

What the system manages, how requests flow, and the entity-relationship structure.

  • The system manages three record groups: products, components, and suppliers.
  • Users can create, view, update, and delete records through a simple PHP web interface.
  • Each page follows the same layout: navigation menu, input form, and records table.
  • Basic request flow:
Form Input
→
PHP Handler
→
SQL Exec
→
Refreshed Table
Entity-Relationship Diagram
PRODUCT
ID · Name · Qty
──
PRODUCT_COMPONENT
Bridge table
──
COMPONENT
ID · Name · Desc
SUPPLIER
ID · Name · Contact · Address
──
SUPPLIER_COMPONENT
Bridge table
Conceptual: products use components
Suppliers provide those components
Speaker — Reign
02 / Data Model

Manufacturer SystemData Model

This section introduces the structure behind the project: the high-level conceptual flow, the table relationships, and the schema fields that support the CRUD pages.

Conceptual View Logical Model Schema Details
What This Slide Covers
Core Entities PRODUCT, COMPONENT, and SUPPLIER define the main records tracked by the app.
Bridge Tables PRODUCT_COMPONENT and SUPPLIER_COMPONENT map the many-to-many relationships cleanly.
Database Intent The structure is built to keep the UI simple while keeping the data connected and extensible.
Reference Diagrams
Conceptual Model
PRODUCT
REQUIRES
COMPONENT
SUPPLY
SUPPLIER
Logical Model
PRODUCT
PK
product_ID product_name quantity_on_hand
PRODUCT_COMPONENT
PKFK
product_ID component_ID quantity_used
COMPONENT
PK
component_ID component_name description
SUPPLIER_COMPONENT
FKFK
supplier_ID component_ID unit_price load_time
SUPPLIER
PK
supplier_ID supplier_name
Schema Details
PRODUCT
PKproduct_ID
TXTproduct_name
INTquantity_on_hand
PRODUCT_COMPONENT
PK/FKproduct_ID
PK/FKcomponent_ID
INTquantity_used
COMPONENT
PKcomponent_ID
TXTcomponent_name
TXTdescription
SUPPLIER_COMPONENT
FKsupplier_ID
FKcomponent_ID
DECunit_price
TXTload_time
SUPPLIER
PKsupplier_ID
TXTsupplier_name
TXTcontact_info
TXTaddress
Speaker — Angelo
04 / Module

Products Module

How the product page works from the user side and from the PHP side.

User Side
The form accepts the product name and quantity on hand. A table below shows all current records, with action buttons for editing or deleting each row.
Program Side
The PHP file checks which action was requested, then runs the matching SQL statement for insert, update, or delete. The page re-reads the table so the latest data appears immediately.
Why It Matters
Bound parameters keep SQL clean and safely pass input into Oracle. The updated table delivers instant feedback after every action.
Core Pattern
One module page
manages one record set
with a straightforward
form + table interface.
CRUD Workflow
C
CREATE
R
READ
U
UPDATE
D
DELETE
Speaker — Jhun
05 / Modules

Components &
Suppliers Modules

Different data, same clean workflow and user experience.

⚙️
Components
Parts & materials used in manufacturing
  • Stores parts or materials used in manufacturing.
  • Each record includes a component name and description.
  • Full add, edit, delete, and view support — identical to Products.
🏭
Suppliers
Where materials & components come from
  • Stores supplier name, contact information, and address.
  • Helps track origin of all materials and components.
  • Uses the same structure — users need no relearning.
Both modules reuse the same navigation, form layout, and table style — improving usability and making the project significantly easier to maintain.
Speaker — Cervales
06 / Database & Conclusion

Database Design
& Closing Summary

3
Core Tables
2
Bridge Tables
21c
Oracle XE
Oracle 21c XE stores the main PRODUCT, COMPONENT, and SUPPLIER tables with identity-based primary keys.
PRODUCT_COMPONENT and SUPPLIER_COMPONENT model relationships instead of keeping records isolated.
Design is ready for future features: part tracing, material computation, supplier link views.
Sample data in the SQL file makes the system easier to test and demonstrate.
A simple but functional CRUD system that combines web pages, PHP logic, and a relational Oracle database.
End of presentation
Reign Angelo Jhun Cervales