Surfside Data Architecture
MySQL 8 · Relational design · WVU project

Surfside Surfboards Database

A normalized operating model for customers, fixed board configurations, reusable components, orders, reviews, and quarterly management reporting.

Created by Kristofor FigueiredoOriginal business rules and database concept developed at West Virginia University. SQL implementation reconstructed from the surviving project brief.
8Normalized base tables
2Reusable reporting views
9Integrity constraints
MySQL 8Target database engine

Schema reference

Select a table to inspect its purpose, keys, and relationships. The implementation separates customer identity, multivalued phone numbers, catalog configuration, transactions, and feedback.

Business-rule coverage

01Customers may be veterans, professional surfers, both, or neither.
02Customers may have multiple phone numbers and may exist before placing an order.
03Board models use fixed, company-defined component recipes; custom substitutions are excluded.
04One order belongs to one customer and may contain multiple board models and quantities.
05Quarterly analysis identifies top spenders, best sellers, and reviews that need follow-up.

Implementation files

Schema and views SQL → Synthetic sample records SQL → Quarterly analytics SQL → Integrity checks SQL → Local MySQL environment YAML →
Demonstration records are synthetic. This repository contains no real customer, veteran, or client information.