Skip to main content

Teaching portfolio · Monash EDF5146

Digital educator portfolio: a VCE Applied Computing database unit

Eight curated resources for a Year 11 relational database unit, a curriculum map of VCE Applied Computing, a teaching reflection, and a short video for other digital technologies teachers.

This is my digital educator portfolio for EDF5146 at Monash University. It brings together eight curated resources that support my AT1 lesson plan on relational databases, a map of where that unit sits in VCE Applied Computing, a reflection on how I would teach with the resources, and a short video made for other digital technologies teachers. Every resource can be previewed, run and downloaded on this page.

1. Professional introduction​

Who I am as a future VCE Applied Computing teacher, in a two-minute captioned video, with the script I recorded from and the four things it covers.

Video: arvinhay.vercel.app/teaching/intro.mp4

Video 1. Teaching portfolio introduction, 1 minute 51 seconds. The captions are part of the picture.
Video transcript

Hi, I'm Arvin. I'm currently studying the Master of Teaching (Secondary) at Monash University, specialising in mathematics and digital technologies. I'm currently on placement at John Monash Science School, and I'm interested in teaching VCE Applied Computing.

My background is actually in computer science. I've worked as a DevOps engineer at Monash eSolutions, and a systems and automation engineer at NEXTDC. So I've had quite a bit of an experience working with technology outside of the classroom, and that has influenced how I see teaching.

For me, computing isn't just about learning how to use a software or getting a piece of code to run. I think it's more important that students understand how and why technology works, why we use it, and the reasoning behind the decisions they make.

In the classroom, I like to start by showing students an example and explaining the story behind the technology. From then, I want to give them the freedom to explore different approaches and work things out between themselves.

At the same time, I think it's very important that they understand how to use technology responsibly, especially when dealing with data and privacy.

One strength I can bring to teaching is my industry experience, but I'm also aware that knowing something technically and being able to teach it to beginners are two different things. There's something I want to keep improving, especially with Python and SQL.

I want to become better at supporting students as they move from Year 10 into VCE and continue learning from other teachers through the Digital Learning and Teaching Victoria.

Thanks for watching!

Values and teaching philosophy
Computing is not about getting a piece of code to run. Students should understand how and why technology works, and the reasoning behind the decisions they make.
Vision for digital learning
Start with an example and the story behind the technology, then give students the freedom to explore different approaches and work things out between themselves, using technology responsibly, especially with data and privacy.
Strengths
Industry experience: DevOps at Monash eSolutions, then systems and automation engineering at NEXTDC. Knowing something technically and teaching it to beginners are two different things, and I keep working on the second.
Professional goals
Keep improving how I teach Python and SQL to beginners, support students as they move from Year 10 into VCE, and keep learning from other teachers through Digital Learning and Teaching Victoria.

My placement experience and the way I run a lesson are on my Teaching page.

2. Curriculum map​

VCE Applied Computing as four threads across Units 1 to 4. Select an outcome to see what it covers, which of my resources serve it, and where it leads.

Year 11 · Units 1 and 2Applied ComputingSchool-assessed outcomes
Year 12 · Units 3 and 4Data AnalyticsSAC · SAT · examination
Year 12 · Units 3 and 4Software DevelopmentSAC · SAT · examination
Data

Year 11 · Units 1 and 2 · Applied Computing · School-assessed

Unit 1 · Outcome 1: Data analysis

Interpret teacher-provided requirements and designs. Build a relational database with tables, primary and foreign keys and consistent naming, query it with SQL, validate and test the data, and present findings with data visualisations.

My Ridgeview database unit sits here; R7 is the professional learning behind it.

Resources

Pathway

Programming
Projects
Security

Year 11 · Units 1 and 2 · Applied Computing · School-assessed

Unit 1 · Outcome 1: Data analysis

Interpret teacher-provided requirements and designs. Build a relational database with tables, primary and foreign keys and consistent naming, query it with SQL, validate and test the data, and present findings with data visualisations.

My Ridgeview database unit sits here; R7 is the professional learning behind it.

Resources

Pathway

Outcome summaries paraphrased from the VCE Applied Computing Study Design, accreditation from 2025 (VCAA, 2025); the VET pathway from VCAA (2026). SAC: School-assessed Coursework. SAT: School-assessed Task. Units 3 and 4 end with an examination in each study.

The map reads left to right: Year 11 Applied Computing (Units 1 and 2) leads to a choice of two Year 12 studies, Data Analytics or Software Development (Units 3 and 4), each assessed by coursework, a School-assessed Task and an examination (Victorian Curriculum and Assessment Authority [VCAA], 2025). Each row is a thread through the whole study: data, programming, projects and security. Unit 1 Outcome 1 is the root of the data thread, where my Ridgeview unit and resources R1 to R8 sit.

Data Analytics Unit 3 Outcome 1 repeats the Unit 1 moves on large repositories, so the jump ahead is scale; my resources make the reasoning visible while the data is small. R4's optional Python extension reaches across to Software Development Unit 3 Outcome 1. Unit 2 Outcome 1, the first full problem-solving methodology cycle, rehearses the School-assessed Task; Unit 2 Outcome 2 leads to both Unit 4 security outcomes. A parallel pathway, VCE VET Creative and Digital Media (Certificate III in Screen and Media), runs alongside Applied Computing with its own scored Unit 3 and 4 sequence (VCAA, 2026).

The same map as a single diagram, drawn in Lucidchart. Select it to zoom, or open the editable original.

Figure 1. The map as one diagram, drawn in Lucidchart (Lucid Software, n.d.). Open in Lucidchart · Full-size image

3. Resource collection​

Eight resources support the five lessons of my AT1 unit, in which Year 11 students turn a messy sign-up spreadsheet for a fictional school, Ridgeview, into a tested SQLite database: learning activities, a real public dataset, scaffolds with worked samples, an ethical case study, the database tool itself, and a professional learning review. None repeats the slide deck, ERD activity sheet or exit ticket I built for AT1. All data are synthetic or public. The unit runs in four steps:

  1. A messy sign-up spreadsheet. A duplicate row, names typed two ways, a room that moved for some rows and not others, an impossible date. Students find the faults before they meet the fix.

  2. Entities, keys and relationships. The same data as an entity relationship diagram, with each design choice justified.

  3. A tested SQLite database. Built from the diagram, then queried in SQL and from Python, in the browser or on a laptop.

  4. A chart and a written answer. A query becomes a chart, and the chart becomes a short written answer to the question the school asked.

Figure 2. The unit in four steps. Select a picture to open the resource it comes from (R1, R3, R4 and R6).

3.1 The resources​

Each card says where a resource sits in the unit and the curriculum, and holds its files. Preview a resource to read it page by page and, for R4 and R8, to run the database and Python files in your browser.

3.2 Where each resource sits in the unit​

Table 1. Where each resource sits in the five lessons of the AT1 unit, and its role in each.

LessonFocusResources and their role
Why relational databases?A messy spreadsheet, and why one table breaks: duplicates, update anomalies and missing values.
  • main
  • discussion
Designing relational databasesEntities, attributes, keys, relationships and an ERD for Ridgeview. The slide deck, ERD activity sheet and exit ticket are from AT1.
  • starter dataset
  • extension
Building a responsible databaseFrom diagram to tables and constraints, a retrieval clinic on exit-ticket errors, and a checkpoint on handling personal data.
  • clinic
  • retrieval
  • checkpoint
  • begins
  • tool
Querying with SQLSELECT, WHERE, JOIN and aggregates through predict, run, investigate, modify, make. The missing join condition happens on purpose.
  • main
  • tool
Testing, analysing and communicatingTest the database against the brief, chart an answer, explain it in writing. Summative.
  • summative
  • tool

, the professional learning planner, runs across all five lessons: it is how I plan the thinking behind each one, not a student resource.

3.3 How each resource supports the unit​

Table 2. How each resource supports the unit: AT1 success criteria, Unit 1 Outcome 1 key knowledge, research base and APST standards.

ResourceFormatAT1 lessonSC1 EntitiesSC2 KeysSC3 RelationshipsSC4 Justify designU1O1 key knowledgeKey researchAPST
R1 Data DetectiveActivity (spreadsheet)L1 (L2 starter data)●○○Data quality; validationTPACK (Mishra & Koehler, 2006)2.1, 3.4
R2 Untangle the OlympicsActivity (public dataset)L2 ext. / L3●●●●RDBMS structure; PK and FKWorked examples (Atkinson et al., 2000)2.1, 2.2
R3 ERD ClinicScaffold + samplesL3 start○●●○RDBMS structure; data typesHinge questions (Black & Wiliam, 2009)5.1, 3.6
R4 SQL with PRIMMActivity (code)L3, L4○○SQL; validation and testing; naming conventionsPRIMM (Sentance et al., 2019)2.6, 3.4
R5 De-identified?Ethical case studyL1, L3●Data quality; responsible data handlingOAIC (2018)4.5, 2.6
R6 Test, chart, explainScaffold + rubricL5○Testing; data quality; visualisationFeedback (Hattie & Timperley, 2007)5.1, 5.2
R7 PL reviewProfessional learningTeacherDesign tools (query designs); naming conventionsDLTV (n.d.); VCAA (2024)6.1, 6.2, 6.4, 7.4
R8 DB Browser for SQLiteTool/platformL3 to L5○○SQL; validating and testing dataTPACK (Mishra & Koehler, 2006)2.6, 3.4

● main focus · ○ supports. SC1 to SC4 are the AT1 Lesson 2 success criteria: identify entities and attributes; choose and explain keys; state relationships and cardinality; construct an ERD and justify a decision.

3.4 Annotations​

R1Ridgeview Data Detective

Lesson 1; full dataset for the Lesson 2 starterLearning activity: data analysis task

A 41-row synthetic sign-up sheet with ten planted faults and nine tiered tasks.

Outcome
U1O1 data quality and validation; AT1 success criterion 1 (entities).
Pedagogy
students find redundancy and update anomalies before I name them, so the case for separate tables comes from their own evidence; a familiar tool keeps attention on the new idea (TPACK; Mishra & Koehler, 2006).
Access
Core, Application and Challenge tiers; worked example row.
Limits
planted faults are tidier than real data; R2 follows with real data.

R2Untangle the Olympics

Lesson 2 extension or Lesson 3 retrievalLearning activity: real public dataset

A 12-row excerpt of real Olympic swimming data that students normalise into five entities.

Outcome
RDBMS structure, primary and foreign keys, cardinality; AT1 success criteria 1 to 4.
Pedagogy
moves the Lesson 2 ERD process onto new surface features, which is when worked examples transfer best (Atkinson et al., 2000); deciding where Age belongs needs justification, not recall.
Access
Core names the entities; sentence starters reused.
Limits
real data is noisy, so the excerpt stays at 12 rows (Griffin, 2018).

R3ERD Clinic

Start of Lesson 3, after exit ticketsScaffolded activity with constructed work samples

Three hinge questions and four teacher-constructed designs that nearly work, each showing a common novice error.

Outcome
AT1 success criteria 2 and 3; choosing SQLite data types.
Pedagogy
hinge questions give whole-class evidence in seconds (Black & Wiliam, 2009); students explain consequences, such as a phone number losing its leading zero.
Access
relationships in words and symbols; samples labelled as constructed.
Limits
new exit-ticket errors become new samples.

R4Querying Ridgeview with SQL

Lessons 3 and 4Learning activity: code practice (PRIMM)

A Ridgeview database with validation rules, a PRIMM worksheet with tested answers, and two Python files.

Outcome
SQL across related tables; validation and testing; naming conventions (U1O1).
Pedagogy
PRIMM asks students to predict before writing (Sentance et al., 2019); Investigate removes the linking line, a known novice error (Miedema et al., 2021).
Access
runs in R8 or in the browser; stretch tasks optional.
Limits
the Python extension goes beyond U1O1, previewing Software Development Unit 3 Outcome 1.

R5Is it really de-identified?

Lesson 1 discussion; Lesson 3 data-handling checkpointEthical case study

A fictional survey case and a collect, transform or drop decision for each Ridgeview field.

Outcome
U1O1 data quality and responsible handling; previews U2O2 and Data Analytics U4O2.
Pedagogy
students test whether changing a survey's emails makes it de-identified, using OAIC (2018) guidance, then rate sources of test data, including generative AI.
Access
all values invented; no student shares their own information.
Limits
it simplifies privacy law; teacher notes give precise terms.

R6Test it, chart it, explain it

Lesson 5 (summative)Scaffold, rubric and teacher model

A boundary-value test table, a query-to-chart walkthrough, a teacher model and a rubric.

Outcome
testing; factors affecting data quality; visualisations to present findings (U1O1).
Pedagogy
boundary-value tests turn "it works" into something students can check; a single-point rubric from AT1's criteria focuses feedback on next steps (Hattie & Timperley, 2007).
Access
writing frame and word bank support EAL/D learners.
Limits
the rubric rewards evaluation, so copying the model earns little.

R7Three ways of thinking: professional learning review

My professional learningProfessional learning: DLTV module and VCAA briefing

A review of DLTV's three ways of thinking module and the VCAA Unit 1 Outcome 1 briefing, turned into changes to the unit.

Purpose
maps computational, design and systems thinking onto each lesson (Digital Learning and Teaching Victoria [DLTV], n.d.).
Impact
the VCAA (2024) briefing led me to add query designs to R4, one naming convention throughout, and data quality factors to R6.
APST
6.1, 6.2, 6.4 and 7.4.
Limits
the module is pitched below VCE, so I translated it; the planner is reviewed each term.

R8DB Browser for SQLite

Lessons 3 to 5Tool/platform

The tool for R4 and R6: a visual schema, an Execute SQL tab, and constraints that fail in front of students.

Outcome
SQL; validating and testing data (U1O1).
Pedagogy
chosen on TPACK grounds (Mishra & Koehler, 2006): a spreadsheet cannot show a foreign key refusing a bad row; DB Browser shows it without hiding the SQL.
Affordances
free on every platform; Browse Data and Execute SQL tabs match R4's predict-run cycle.
Limits
needs installation, so the same database also runs in the browser here.

4. Teaching reflection and pedagogical analysis​

How I would teach with the resources in Part 3, what research supports those choices, where the risks are, and where I need to grow.

4.1 Pedagogical approach

My approach to this unit is my approach to teaching in general: show the thinking clearly, then hand it over. Database design asks novices to hold entities, attributes, keys and cardinality in mind at once, which is where cognitive load theory predicts that minimally guided discovery will fail (Sweller et al., 2019). So these resources are explicit first and constructivist second. Each models the reasoning once, then moves students into what Vygotsky (1978) called the zone of proximal development, where scaffolds such as hinge questions, sentence starters and a worked row let them attempt what they could not yet do alone; Hmelo-Silver et al. (2007) argue that inquiry works when it is scaffolded this way.

R1 lets students find the faults in a flat spreadsheet before I name redundancy, so the case for separate tables comes from their own evidence. R2 moves the Ridgeview worked example onto real Olympic data, because worked examples transfer best when practice varies the surface features (Atkinson et al., 2000). R4 uses PRIMM, so students read and predict a query before writing one (Sentance et al., 2019).

Placement taught me that working through every example loses the students who already have the method, so the structure is fixed but the reasoning is theirs: why a relay gold breaks a medal count has no procedure to copy.

4.2 Technology integration

I used TPACK to test each technology choice: does the tool fit both the content and the way I want students to learn it (Mishra & Koehler, 2006)? R1 starts in a familiar spreadsheet, so attention goes to redundancy, not the interface. R8, DB Browser for SQLite, arrives only when the content needs it, because constraints and joins cannot be shown honestly in a spreadsheet; because it must be installed, every file also runs in the browser.

The Python extension shows why a parameterised query matters: one apostrophe turns a roll search into thousands of rows. For inclusion I applied Universal Design for Learning (CAST, 2024): relationships are labelled in words and symbols, every activity has a paper version, and the tiers change the support, not the goal. Technology is also a subject for ethical judgement: R5 asks whether a survey file with changed emails is really de-identified (OAIC, 2018).

4.3 Curriculum connection

Every resource serves Unit 1 Outcome 1, which asks students to interpret teacher-provided requirements and designs, analyse data and present findings visually (VCAA, 2025). My unit centres on its database work, so the resources treat spreadsheet and chart skills as prior knowledge: R1 starts from a familiar sheet, and R6 asks for a chart only once the database has been tested.

The VCAA (2024) briefing on Unit 1 Outcome 1 also shaped the plan: it names query designs as a design tool, so R4 asks students to plan each query before writing it, and R6 asks them to evaluate the factors affecting data quality. R4's optional Python extension goes beyond it, previewing Software Development Unit 3 Outcome 1.

4.4 Challenges and risks

The biggest risk is time: five lessons cannot hold every resource, so R2 and the Python extension are optional, and R3 is used only when exit tickets call for it. A second risk is extraneous load from real data. The Olympic file's missing heights and broken characters help a data quality discussion but could swamp a student unsure about keys, so I limited it to twelve rows. Third, SQL novices predictably leave out join conditions (Miedema et al., 2021), so R4 makes that error happen on purpose, before assessed work.

Fourth, constructed samples (R3) and a teacher model (R6) can be copied instead of understood, so both are labelled and paired with tasks that ask for consequences. Finally, the resources still have to prove themselves with a class.

My placement feedback was direct: my lesson structure was sometimes hard to follow, and I could spend so long with one student that the class drifted. The resources answer that. PRIMM gives R4 one visible sequence, R3's hinge questions check everyone at once, and the Core, Application and Challenge tiers let me release the class sooner. I plan to trial them with a Year 11 class and adjust each lesson from what hinge questions and exit tickets show, not from the plan (Black & Wiliam, 2009).

4.5 Professional learning goals

My strength is the technical content; the area I am developing is pedagogical content knowledge for databases: which misconceptions to expect and when to step in. Placement taught me that precise language matters: saying a query "joins" tables hides the reasoning as surely as saying logarithms "cancel".

My first goal is to build that knowledge for SQL through the research literature and mentors. My second is to learn from Applied Computing teachers how they move students from DB Browser to Python, and where students struggle. My third is to follow Study Design support materials and DLTV events, where I can test these resources against practising teachers' experience. R7 records these goals.

5. Public-facing contribution​

A short video for other digital technologies teachers, with the paragraph that accompanies it. The query it describes runs underneath, so a viewer can test the claim.

Video: arvinhay.vercel.app/teaching/explainer.mp4

Video 2. Decisions, not diagrams: three ways to teach database design. 1 minute 55 seconds, captioned.
Video transcript

Decisions, not diagrams. These are three ways to teach database design.

Students can draw a perfect entity relationship diagram and still build a database that breaks. I think that's because we teach the diagram as the goal, when it's really a record of decisions. Here are three ways I teach those decisions in VCE Applied Computing, Unit 1.

One. Let students find the problem first. Before I say the word redundancy, I give them a messy sign-up spreadsheet for a fictional school. One teacher's name is typed two ways. A room change was made in some rows and missed in others. With tools they already know, like COUNTIF, they find the faults themselves, and separate tables start to make sense.

Two. Make them predict before they type. This follows PRIMM: predict, run, investigate, modify, make. I include one query that goes wrong on purpose. Twenty students, forty registrations. Remove the join condition, and the count jumps to eight hundred. Missing join conditions are a known novice error, so I'd rather students meet it here than in an assessment.

Three. Treat privacy as a design decision. Use invented data, and ask students to justify every field against its purpose. Taking the names out doesn't always make data de-identified, and that's a good question for a class to argue about.

All of these resources are free, with teacher answers, on my website. I'd love to hear how you teach SQL in Unit 1.

5.1 Accompanying paragraph

This short video is for other digital technologies teachers. It turns the design choices behind my Ridgeview resources into three moves for VCE Applied Computing Unit 1: let students find the faults in a messy spreadsheet before naming redundancy, have them predict a query's result before running it, including a join that fails on purpose (Sentance et al., 2019; Miedema et al., 2021), and treat every field as a privacy decision (OAIC, 2018). The resources shown are free in this portfolio.

5.2 Try the query from the video

Loading SQLite…

The linking line has gone. Predict the count, run it, then explain the number using primary key and foreign key.

6. References​

AI Acknowledgement​

I acknowledge the use of Claude (Anthropic) as an assistant in preparing this portfolio.

Generate ideas, structure suggestions or other preparatory support
I used Claude to brainstorm ideas and suggest ways to organise the portfolio.
Generate text, rewrite or paraphrase
I used Claude to help draft and revise portfolio text, edit my English, and improve language and clarity.
Generate other content
I used Claude to help generate Python and SQL code and supporting resource materials, and to format documents for the resources.

I personally edited and reviewed all work, including AI-generated content, before submission. I take responsibility for the final submission.

Word count​

Table 3. Words in each assessed part. The reference list is not counted.

PartWords
1. Professional introduction (video script)267
2. Map annotations182
3. Resource annotations614
4. Reflection812
5. Public-facing contribution (video script and paragraph)322
Total2,197