Technologies · Year 10

Active learning ideas

Database Design: ER Diagrams

Active learning works especially well for ER diagrams because students must wrestle with abstraction by turning messy real-world situations into clear, logical structures. When learners sketch, critique, and revise diagrams together, they immediately see how design choices affect efficiency and integrity.

• ACARA Content Descriptions
• AC9DT10P02

• 20–50 min
• Pairs → Whole Class
• 4 activities

Activity 01

• Collaborative Problem-Solving
• 35 min · Pairs

Pairs: Library System ER Design

Pairs identify entities (Books, Borrowers, Loans), list attributes, and draw relationships with cardinality notation. They justify choices using a scenario sheet. Pairs swap diagrams for 5-minute peer feedback before finalizing.

Design an ER diagram for a school management system.

Facilitation Tip

During the Library System ER Design, give each pair a printed scenario and colored markers so they visibly separate entities, attributes, and relationships on paper.

What to look for

Provide students with a list of entities and their attributes for a simple scenario (e.g., a pet adoption agency). Ask them to draw the ER diagram, including entities, attributes, and at least one relationship with correct cardinality. Review for accuracy in representation.

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

Activity 02

• Collaborative Problem-Solving
• 45 min · Small Groups

Small Groups: Relationship Classification Challenges

Groups receive 10 real-world scenarios and classify each into one-to-one, one-to-many, or many-to-many. They sketch sample ER snippets for three scenarios. Groups share one example with the class for discussion.

Analyze how different relationship types (one-to-one, one-to-many) impact database design.

Facilitation Tip

In Relationship Classification Challenges, ask groups to categorize each relationship type by placing sticky notes on a classroom wall labeled One-to-One, One-to-Many, Many-to-Many.

What to look for

Present two ER diagrams for the same scenario, one using a one-to-many relationship and another using a many-to-many relationship where a one-to-many would suffice. Ask students: 'Which diagram is more efficient and why? How would the choice of relationship type affect data retrieval speed for common queries?'

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

Activity 03

• Collaborative Problem-Solving
• 50 min · Whole Class

Whole Class: School Management Build

Project a blank canvas; class nominates entities and attributes for a school system. Vote on relationships via hand signals, then draw iteratively on shared digital tool. Adjust based on class input.

Justify the inclusion of specific attributes for an entity.

Facilitation Tip

For the School Management Build, circulate with a checklist of normalization rules so students can self-assess if their design meets third normal form before whole-class discussion.

What to look for

Students work in pairs to design an ER diagram for a given system. After completing their design, they swap diagrams with another pair. Each pair evaluates the swapped diagram based on these questions: Are all essential entities present? Are attributes clearly defined? Is the cardinality of relationships logical? They provide written feedback on one area for improvement.

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

Activity 04

• Collaborative Problem-Solving
• 20 min · Individual

Individual: Attribute Justification Task

Students receive a partial ER diagram and add attributes to entities, writing one sentence per attribute explaining its purpose and data type. Submit digitally for quick review.

Design an ER diagram for a school management system.

What to look for

Provide students with a list of entities and their attributes for a simple scenario (e.g., a pet adoption agency). Ask them to draw the ER diagram, including entities, attributes, and at least one relationship with correct cardinality. Review for accuracy in representation.

• Apply
• Analyze
• Evaluate
• Create
• Relationship Skills
• Decision-Making
• Self-Management

A few notes on teaching this unit

Teach ER diagrams by alternating between quick modeling tasks and reflective critiques. Start with a simple scenario, model your own thinking aloud, then have students iterate. Research shows that frequent, low-stakes sketching followed by peer review builds both conceptual clarity and technical precision faster than lectures alone.

Successful learning looks like students confidently translating scenarios into ER diagrams with correctly labeled entities, attributes, primary keys, and cardinal relationships. They justify choices aloud and adjust diagrams after peer feedback.

---

Watch Out for These Misconceptions

• During Relationship Classification Challenges, watch for students defaulting to one-to-many relationships in every scenario.

  Have pairs present their classification choices to the class and justify why a one-to-one or many-to-many fits better; circulate with example cards of Person–Passport (one-to-one) and Student–Course (many-to-many) to prompt discussion.

• During Library System ER Design, students may treat entities as vague containers without identifying unique keys.

  Before they sketch, ask each pair to list three attributes for each entity and circle the one they would choose as the primary key, then share with another pair for feedback.

• During School Management Build, students may view ER diagrams as decorative rather than logical blueprints.

  After the whole-class build, display two student diagrams side by side and facilitate a critique session where the class identifies which design supports faster queries for common tasks like finding a teacher’s classes or a student’s timetable.

---

Methods used in this brief

• Collaborative Problem-Solving