Restaurant & Cafe Chain Data Model
A governed relational model for restaurant operations, customers, orders, inventory, and sensitive information.
MY ROLE
Data modeler: conceptual design, 3NF relational schema, governance classification, and SQL queries.
THE DECISION
How should a multi-location restaurant chain structure operational data so it remains usable, consistent, and governed?
APPROACH
- Designed conceptual and relational models
- Normalized 11 tables and 57 attributes to 3NF
- Classified sensitive fields and data-quality risks
- Implemented representative business queries
EVIDENCE & DELIVERABLES
- SQLite database and schema
- Entity-relationship diagrams
- Four-part final submission
SELECTED WORK FILES
PDF
Relational Data Model
UC Davis Part 2 submission — relational model and normalization rationale.
302 KBSQL
SQLite Schema
3NF schema with 11 tables, primary/foreign keys, and sensitive-field classification comments.
4 KBSQL
Business Queries
Monthly revenue and multi-table menu-performance queries from the final assignment.
1 KBEVIDENCE INTEGRITY
This case is presented as uc davis final assignment. The label distinguishes observed work from simulated impact, proxies, historical comparisons, or proposed architecture.