Shantae Baker's Webquest

Introduction

Hello students!!

For today's lesson I want you all to imagine walking into your favorite Starbucks Location. The barista remembers your name, your usual order, and even how you like your coffee—no sugar, extra foam. Ever wonder how businesses keep track of so much information, especially when they grow and have hundreds or thousands of customers?

Well, today is your day to figure it all out. It is now your turn to step behind the scenes.

Task

You’ve just landed an internship at a rising tech consulting firm that helps small businesses go digital. A real client is in desperate need of a better way to manage their growing chaos of data—customers, products, sales, and more are all stored in messy spreadsheets and sticky notes. They are desperately in need of a resolution.

Design a clean, efficient database system that solves their problems and helps them work smarter, not harder. You’ll play the role of a real database developer—analyzing needs, designing relationships, writing SQL, and even presenting your solution like a true tech consultant.

 

In teams, you'll design a relational database for a fictional business of your choice (e.g., bookstore, clinic, music store, gym). You must:

  • Identify entities and relationships

  • Create an Entity Relationship Diagram (ERD)

  • Define tables with appropriate fields and data types

  • Write SQL statements to create tables and insert sample data

  • Present your solution to the class 

Process

Step 1: Choose Your Business

Pick a business that has at least 3 types of related data (e.g., customers, products, orders).

Step 2: Analyze Requirements

  • What data needs to be stored?

  • What are the relationships between the data?

Step 3: Design Your ERD

Use the Lucidchart tool.

Step 4: Define Your Tables

For each table, list:

  • Table name

  • Fields (name, type, and constraints like primary key, foreign key, NOT NULL)

Step 5: Write SQL

Use basic SQL to:

  • CREATE TABLE statements

  • INSERT INTO for adding sample data (3–5 records per table)

Step 6: Presentation 

Show off your database design:

  • Explain your entity relationship disgrams.

  • Justify your choices

  • Show sample queries that a user might run

Evaluation

This rubric outlines the specific requirements and expectations for your Database Design WebQuest project. Use it as a checklist to guide your work and understand how your final submission will be evaluated.

 

Criteria

Excellent (4)

Good (3)

Fair (2)

Needs Improvement (1)

ER Diagram Design

 

 

 

Includes at least 3+ entities, proper relationships, all PKs and FKs, clean layout

2–3 entities, mostly correct relationships, few missing PKs or FKs

2 entities, some unclear or incorrect relationships, multiple missing keys

Fewer than 2 entities, unclear or illogical structure, missing key components

Table Structure

Each table includes at least 4 fields, with appropriate data types and constraints (PK, FK, NOT NULL)

Mostly correct fields and types, minor constraint issues

Basic fields present, but poor structure or incorrect types

Very few fields, wrong data types, missing or misused constraints

SQL Accuracy

All SQL statements (CREATE and INSERT) are fully functional, use correct syntax, and create complete structure with data

Mostly functional with minor errors or inconsistencies

Many syntax errors or missing pieces

Major issues, incorrect or non-functional SQL

Sample Data & Queries

Provides 3–5 sample INSERT statements per table and 2+ working SELECT queries demonstrating relationships

Inserts and 1–2 queries provided, mostly working

Few INSERTs and/or 1 basic query, limited demonstration of data usage

Little or no sample data or queries included

Presentation / Report

Clear explanation of design decisions, all group members contribute, well-organized slides or report

Mostly clear, some gaps in explanation or unequal participation

Presentation/report lacks clarity or detail, minimal team collaboration

Disorganized or unclear, little effort in communication

Teamwork & Professionalism

On-time submission, division of roles clearly shown, all members engaged and respectful

On-time, minor collaboration issues

Some teamwork problems or late submission

Major teamwork issues or missing deadlines
Conclusion

You have now experienced what real-world database designers do.  They analyze needs, structure data, and build smart systems. Think about how many apps and companies rely on databases behind the scenes. This is just the beginning of what you can do with data!!

Credits
Teacher Page

This WebQuest is designed for high school students (Grades 10–12) or first-year college students enrolled in an Information Technology or Computer Science course. It is suitable for students who are being introduced to database systems and relational database concepts.

Subject Area and Topic

  • Subject: Information Technology

  • Topic: Introduction to Relational Database Design and SQL

Learning Objectives

By the end of this WebQuest, students will be able to:

  • Identify entities and relationships in a real-world data scenario with 90% accuracy.

  • Competently create an Entity Relationship Diagram (ERD) using appropriate notation.

  • Define and structure relational database tables using appropriate field types and constraints.

  • Write basic SQL statements to create tables, insert data, and perform simple queries.

  • Demonstrate teamwork, presentation skills, and professionalism in a creative and cohesive manner.

Duration

4–5 class periods (45–60 minutes each)

Materials and Tools Required

  • Computers or devices with internet access

  • Word processor or presentation software (e.g., Google Docs, PowerPoint)

  • Access to online ERD tools ( Lucidchart)

  • SQL playground or environment (e.g., SQLiteOnline)

  • Web resources (e.g., W3Schools SQL Tutorial)

Prior Knowledge

Students have a basic understanding of:

  • What data is and how it is organized

  • Concepts such as tables, fields, and data types

  • Basic logical relationships (e.g., one-to-many)

Implementation Notes

  • Students will be divided into groups of 3–4 to encourage collaboration and shared responsibility.

  • Groups will be encouraged to select their own business scenario to enhance engagement.

  • Teachers may wish to review basic SQL commands and relational concepts before starting.

  • Teacher will offer formative feedback during the ERD and table design stages to guide student progress.

  • Students will be encouraged to present as if they are professional tech consultants pitching a solution to a client.

Assessment Strategy

  • Group project grading will be supplemented with individual reflection and peer evaluations.

  • Teacher will assess both the final product and each student’s contribution during the process.

  • The rubric covers design quality, SQL accuracy, sample data, collaboration, and presentation.