Assignment: Data Model Design (AI-Assisted)

Overview

In this assignment, you will design the data model for your project using a structured, AI-assisted workflow.

You will move from:

  • entities → attributes → relationships → schema

This builds directly on your previous work:

  • project idea
  • user stories
  • MVP definition

Learning Objectives

By completing this assignment, you will be able to:

  • Translate user stories into a data model
  • Design a relational schema appropriate for a web application
  • Use AI to assist (but not replace) design thinking
  • Critically evaluate and refine AI-generated designs
  • Constrain a schema to a realistic implementation scope

Deliverables

You will submit:

1. Data Model (Required)

  • List of tables
  • For each table:
    • columns (attributes)
    • data types (approximate is fine)
    • primary key
    • foreign keys

2. Relationships (Required)

  • Description of relationships between tables
    • one-to-many
    • many-to-many (if any)
  • Can be:
    • bullet list OR
    • simple diagram (recommended)

3. ER Diagram (Required)

  • Simple visual diagram
  • Hand-drawn, digital, or tool-generated
  • Must include:
    • tables
    • key fields
    • relationships

Keep it simple. Clarity > complexity.

4. Design Explanation (Required)

Short write-up (1–2 pages) explaining:

  • Why you chose these tables
  • How the schema supports your user stories
  • What you simplified for MVP
  • Any tradeoffs you made

5. AI Prompt Log (Required)

Include the prompts you used, such as:

  • entity identification prompt
  • schema generation prompt
  • critique/refinement prompts

For each:

  • include the prompt
  • briefly explain how you used the output

Required Process (Very Important)

You must follow this workflow:

Step 1 — Start from Your Entities

  • Use your previous assignment
  • Refine entities if needed

Step 2 — Generate Initial Schema (with AI)

Use a structured prompt like:

Using my project’s user stories and entities, design a relational database schema for a React/Node/MariaDB application.Please:
- define tables for MVP only
- list columns with data types
- include primary and foreign keys
- identify relationships
- avoid unnecessary complexity for a 7-week project

Step 3 — Critique the Schema (with AI)

Review this schema and:
- identify missing relationships
- identify redundant tables or fields
- suggest simplifications
- ensure it supports all user stories
- flag anything too complex for a 7-week project

Step 4 — Refine Manually

You must:

  • remove unnecessary tables
  • simplify relationships
  • ensure clarity
  • verify against your user stories

Constraints (Read Carefully)

Your design must:

  • be implementable in 7 weeks
  • avoid unnecessary features
  • avoid over-normalization
  • support your MVP only

Common Mistakes to Avoid

Do NOT:

  • blindly copy AI output
  • include every possible feature
  • create too many tables
  • ignore relationships
  • forget status fields (very common!)
  • skip explanation of decisions

Example (Reference Only)

For a campus event planner, a reasonable schema might include:

  • users
  • organizations
  • events

NOT:

  • notifications
  • messaging
  • analytics
    (unless explicitly required)

Grading Criteria

CategoryPoints
Correct tables & attributes25
Relationships & keys20
ER diagram clarity15
Alignment with user stories15
Simplicity / appropriate scope10
Design explanation10
AI prompt usage & reflection5

Timeline

Draft Due: March 27 LINK

Submit:

  • tables
  • attributes
  • rough relationships
  • initial ER diagram (can be rough)
  • AI prompts used so far

Final Due: March 30 LINK

Submit:

  • refined schema
  • clean ER diagram
  • full explanation
  • revised prompts + reflections

Final Advice

A good schema makes your project easy to build.
A bad schema makes everything harder.

And more importantly:

Do not let AI design your database.
Use AI to help you design it better.

Scroll to Top