Unit 3 - 7.5%

Task 3: Database Practical Assessment

Three-week practical assessment building a Microsoft Lists single-table database with data types, primary key, forms, query views, report views, interface, documentation and final LMS submission.

Open Resource Pack Open Task 3 database hub

Assessment Details

Type
Practical
Timing
Week 5-7
Weighting
7.5%
Topics
Microsoft ListsData typesPrimary keyFormsQuery viewsReport viewsDocumentation

Task Overview

Task 3: Three-Week Database Practical Assessment

Summary

Students build a working single-table database solution for an equipment loans scenario using Microsoft Lists in a web browser. The three database lesson weeks are the assessment sequence; there is no separate one-day assessment after the sequence.

Assessment Details

Field Details
Unit Unit 3
Assessment type Practical test
Weighting 7.5%
Timing Term 2 Weeks 5-7 database lesson sequence
Assessment window Assessed across the three database lesson weeks
Final submission End of Week 3 as directed in the LMS
Raw mark 50

Purpose

Assess database skills for creating a working single-table database, selecting suitable data types, using a primary key, creating forms, creating Microsoft Lists query views, creating reports, creating a visual interface for database users, and producing database documentation.

Tool Mapping

Database requirement Microsoft Lists equivalent
Table Microsoft List
Field Column
Data type Column type
Primary key Required unique LoanID column
Form New/edit item form
Query Saved filtered/sorted/grouped view
Query evidence Saved Microsoft Lists views with filter, sort, grouping, visible column and screenshot evidence
Report Saved report-style view
Visual interface Clear view navigation, form order, meaningful names and selected columns

Scenario

Students create an equipment loans database for school items such as laptops, chargers, cameras, microphones and adapters.

Student Evidence

  • One Microsoft List used as a single-table database.
  • At least 10 suitable columns using appropriate column types.
  • A required unique LoanID primary key equivalent.
  • At least 12 sample records.
  • A logical form or item entry layout.
  • At least 4 saved query views.
  • A short Microsoft Lists view evidence response.
  • At least 2 report views.
  • Database documentation.

Three-Week Assessment Sequence

Week Assessment focus Evidence produced
Week 1 Database foundation List structure, fields, data types, LoanID, sample records
Week 2 Query views, report views and interface Saved query views, report views, form/interface evidence, usability improvements
Week 3 Documentation and final submission Evidence document, Excel export, Microsoft Lists share link, final checklist

Required Submission Package

Students submit a three-part evidence package through the LMS:

  1. CSCGT_Task3_2026_Surname_FirstName_Evidence.docx - completed evidence document with screenshots and short explanations in rubric order.
  2. CSCGT_Task3_2026_Surname_FirstName_DataExport.xlsx - Microsoft List exported to Excel so records, fields and sample data can be checked efficiently.
  3. Microsoft Lists share link pasted into the LMS submission comment box - shared with the teacher using school account access so views, forms and interface choices can be verified.

The DOCX and XLSX are the permanent submission evidence. The live Microsoft Lists link is used for verification and must remain accessible until marking and any moderation checks are complete.

Conditions

  • Conducted during the three-week database lesson sequence.
  • Software and resources provided by school.
  • Microsoft Lists is used in the browser. The retired iOS/Android Lists mobile app is not used.
  • Students build and submit their own final product. Teacher support during the sequence may include skill instruction, checkpoints, clarification and access support, but the submitted database evidence must be the student's own work.

School Policy Reminder

  • Missed assessments, extensions, late submissions and academic integrity follow the Secondary Assessment and Reporting Policy.
  • Authentication checkpoints and in-class validation may be used.

Resource Package

The supporting package is stored in content/assessments/tasks/task-3/ and exported through scripts/export-task-3-lms.py.

Student-facing website documents:

  • Student task sheet
  • Three-week assessment instructions
  • Final submission LMS instructions
  • Microsoft Lists how-to guide
  • Database documentation template
  • Equipment loans sample data and example workbooks

Teacher-only marking, administration and moderation files remain in the repo but are not part of the student website document set.