Database Design and Integration
A presentation deck for Week 4 that explains how relational databases are structured, how ER models guide design, how normalization helps, how SQL works, and how Spring Data JPA connects Java applications to data.
- Covers the five Week 4 topics in an expanded slide deck.
- Designed for teaching, revision, and team workflow discussion.
- Use arrow keys, buttons, or slide dots to navigate.
Focus
Week 4 Presentation
Use
Teach this page live or review it before class.
What this week is about
Week 4 is about designing a relational schema and integrating an application with the database.
- 4.1 Introduction to Relational Databases
- 4.2 ER Modeling
- 4.3 Database Normalization
- 4.4 SQL Basics
- 4.5 Spring Data JPA Overview
Focus
Overview
Use
Teach this page live or review it before class.
Tables store data in a structured way
Relational databases organize rows, columns, keys, and relationships so the application can query data reliably.
- Tables focus on one subject at a time.
- Primary keys identify records uniquely.
- Foreign keys connect related tables.
Focus
4.1 Relational Databases
Use
Teach this page live or review it before class.
Relational design supports consistency
A well-designed relational model reduces repetition and makes data easier to manage.
- Data is organized for clear querying.
- Repeated facts are easier to avoid.
- Relationships are explicit instead of hidden.
Focus
4.1 Why it matters
Use
Teach this page live or review it before class.
ER diagrams describe the business structure
An ER model shows the entities, attributes, and relationships before the tables are created.
- Entities become tables.
- Attributes become columns.
- Relationships guide foreign keys and junction tables.
Focus
4.2 ER Modeling
Use
Teach this page live or review it before class.
Cardinality drives the final schema
One-to-one, one-to-many, and many-to-many relationships affect how tables are linked.
- Cardinality should be resolved during design.
- Many-to-many relationships often use a join table.
- ER modeling reduces confusion before SQL starts.
Focus
4.2 Planning
Use
Teach this page live or review it before class.
Normalization removes unnecessary repetition
Normalization splits data into better-shaped tables so updates stay consistent.
- 1NF removes repeating groups.
- 2NF removes partial dependency.
- 3NF removes transitive dependency.
Focus
4.3 Normalization
Use
Teach this page live or review it before class.
Good normalization improves maintenance
Cleaner table design reduces anomalies and makes updates safer.
- Insert, update, and delete anomalies are reduced.
- Related facts are stored once.
- The schema becomes easier to understand.
Focus
4.3 Benefits
Use
Teach this page live or review it before class.
SQL reads and changes database data
SQL gives the application a standard way to create, read, update, and delete records.
- SELECT retrieves rows.
- WHERE filters results.
- JOIN combines related tables.
Focus
4.4 SQL Basics
Use
Teach this page live or review it before class.
CRUD operations map to SQL actions
Create, read, update, and delete are the core operations behind many database features.
- INSERT creates data.
- SELECT reads data.
- UPDATE and DELETE modify stored rows.
Focus
4.4 CRUD
Use
Teach this page live or review it before class.
Spring Data JPA simplifies Java persistence
Spring Data JPA adds repository abstractions on top of JPA so Java applications can access databases with less boilerplate.
- Entities map Java classes to tables.
- Repositories provide CRUD methods.
- Custom queries can still be added when needed.
Focus
4.5 Spring Data JPA
Use
Teach this page live or review it before class.
What students should remember
Week 4 is about designing data structures and connecting applications to them cleanly.
- Relational design gives structure to application data.
- ER models guide the schema before implementation.
- Normalization, SQL, and JPA keep data access manageable.
Focus
Recap
Use
Teach this page live or review it before class.