Level 3 database assessment 2026

• A summative assessment is used to determine your grade for an achievement standard.
• After you submit, your work will be marked, moderated, and grades will be uploaded to KAMAR.
• It is held under real assessment conditions — any violations result in an instant Kāore i whīwhī/Not Achieved grade.

• 🗓️ You have five (5) spells in which to complete your task.
  • 🏫 You may work on this assignment at home.
  • 🕰️ Due to being able to work on this at home, no Extra Time will apply.
• 💬 You may not communicate with anybody other than your kaiako.
  • 🚻 If you need to use the bathroom, let your kaiako know.
  • 🚾 You will not be allocated extra time to compensate for your absence.
• 🌎 You may consult the web, API documentation, etc.
  • You may also consult:
    • the resources posted to this website
    • the cheat sheet
    • your previous database work from this and last year
    • SQLite documentation
    • LibreOffice Base documentation
    • DB Browser for SQLite documentation
• 📖 You must not submit database work that you did not 100% create as your own. This includes:
  • work copied from your neighbours
  • database structures copied from outside sources
  • database designs or SQL generated by a large language model, such as Copilot, ChatGPT, etc.

Failure to adhere to these conditions will result in an instant Kāore i whīwhi/Not Achieved grade. You will then need to reassess as part of project management

Use complex techniques to develop a database involves:

• designing the structure of the data
• using appropriate tools and appropriate techniques to organise, query and present data for a purpose and end users
• applying appropriate data integrity and testing procedures
• addressing relevant implications — you will get this for free

Use complex techniques to develop an informed database involves:

• using information from testing procedures to improve the quality of the outcome
• structuring, organising and querying the data logically

Use complex techniques to develop a refined database involves:

• iterative improvement throughout the design, development and testing process
• using efficient tools and techniques in the outcome’s production
• presenting the data effectively for the purpose and end users

Complex techniques will include a selection from:

• structuring the data using multiple tables or nodes
• creating queries which insert, update or delete to modify data
• creating customised data displays from multiple tables or nodes, such as reports, PDFs, web pages, dashboards, or program interfaces
• dynamically linking data between the database and a front-end display
• applying data access permissions as appropriate to the outcome

::: {.task} Bungee High School’s Japanese Department is struggling to keep track of classroom resources.

The department owns a large number of items including:

• textbooks
• manga
• readers
• flashcard sets
• cultural resources
• games
• electronic devices

Currently, resources are tracked informally, resulting in:

• resources being misplaced
• students forgetting to return borrowed items
• duplicate purchases being made
• teachers being unable to quickly determine what resources are available

The Head of Department has asked you to develop a database system that allows staff to manage the department’s resources and loans.

The database should allow users to:

• view information about all resources owned by the department
• categorise resources appropriately
• record who has borrowed a resource
• record when resources were borrowed and returned
• record the condition of th eresources when loaned/returned
• identify which resources are currently available
• identify which resources are currently on loan
• identify overdue loans
• produce useful reports for staff

The final outcome must provide an effective way for staff to organise and retrieve information.

The database must include:

• stored item records
• stored borrower/user records
• stored loan, hire, rental, or booking records
• queries that retrieve meaningful information
• queries that work across related tables
• evidence that data integrity has been considered and tested
• reports and/or forms (or other form of display) suitable for the end user’s needs

Your database must include at least TWO (2) of the following:

• querying data from multiple tables, such as showing the borrower’s details for a loan
• filtering and ordering queries, such as:
  • filtering to only showing currently borrowed items
  • sorting by name, due date, item category, or loan status
• editing records, including any ONE (1) of:
  • inserting new records
  • updating existing records
  • deleting appropriate records

Data requirements

Use the data below in your database:

Data must be presented in an appropriate way for the purpose and end users.

This includes:

• clear field names
• clear report or form headings
• dates shown in standard New Zealand date format
• currency, if used, shown in New Zealand dollars with two decimal places
• reports or displays that are easy to read
• data from multiple tables presented clearly where appropriate
• easy to read, with appropriate sizing and colours

Examples of useful reports or displays include:

• all available items
• all unavailable items
• current loans
• overdue loans
• borrower loan history
• item loan history
• items grouped by category
• loans ordered by due date

You must test both the database structure and the database outcome.

You should test at least the following parts of the database:

You must also record evidence of errors occurring purely within your database.

You can use SQLite editor, DB Browser for SQLite, LibreOffice Base, or another suitable database tool to test:

You must submit evidence of:

1. Your completed database file.
2. Your Entity Relationship Diagram.
3. Your final table structures.
4. Your queries.
5. Your forms, reports, dashboards, or customised displays.
6. Your testing table.
7. Evidence that your testing led to improvements.
8. Screenshots or exported files showing the database working.
9. A short explanation of how the database meets the purpose and end users’ needs.

For Kaiaka/M and Kairangi/E, your evidence should clearly show that you improved your database after testing.

For Kairangi/E, your evidence should clearly show iterative improvement throughout the design, development, and testing process. The presentation of information must also be appropriate.

If your submitted database file cannot be opened, cannot be checked, or is missing important evidence, it may not be possible to award the grade you are aiming for.

• Cheat sheet
• SQLite documentation
• DB Browser for SQLite
• LibreOffice Base documentation
• Crow’s feet ERD notation