from TKI

from NZQA: Computing/digital technologies clarifications

This achievement standard involves using advanced techniques to develop a database.

Students are required to design and create a database to organise, query and present. Students will show evidence of their use of iterative improvement throughout the development and testing process and of their use of efficient tools and techniques in the outcomes production.

The step up from Level 1 is the requirement for students to design the structure of the data. This suggests that the database is relational and should have more than one table.

The assessment activity must provide opportunity for students to demonstrate advanced techniques. Advanced techniques include:

• linking data in related tables or nodes using queries or keys

• writing custom queries to filter and/or sort data

• using logical, mathematical and/or wildcard operators

• customising presentation of the data

• using custom forms to add user input to the database

• setting validation rules for data entry.

Common database technologies include PHP, MySQL, MariaDB, SQLite. HTML and CSS may be used to provide output. Other technologies such as web frameworks (e.g. Flask or ASP.NET) provide further opportunities.

Students are required to collect evidence as they develop (iterate) their database outcome. Evidence could include:

database planning:

• design descriptions or diagrams outlining the structure of the database including a description of the tables and data types used

• identification of data duplication within a table and creation of a second related table

• how the data in tables can be linked, so that one can query data from more than one table

• identification of what data might be expected

database testing:

• results of data entry including expected and invalid input

• screen captures showing error messages that appear when users attempt to enter invalid data

• various queries working as expected

• testing of outcome with end user/s, confirming it meets the purpose and end user considerations

• data presentation (i.e. screenshots) in the selected format (e.g. report, web page or table)

• consideration of relevant implications.

Written documentation including screenshots and annotations, or short video screencasts could be used by students to provide evidence of planning, testing and consideration of the relevant implications. Students should provide any relevant files for their outcome using an appropriate method for the chosen technology and available resources.

91892: Use advanced techniques to develop a database

Updated December 2021. This document has been updated in its entirety to address new issues that have arisen from moderation

Advanced techniques are given in Explanatory Note 4. The evidence needs to demonstrate at least two advanced techniques in the database.

Design of the structure of the data will include some planning for the database, including:

• planning the table or tables to be used

• selecting appropriate types for the data

• planning any queries needed to address and meet end user requirements.

Student evidence needs to explain the relevant implications for the database. This explanation is then used to inform the design and development of the database. There is a dedicated clarification document which expands on what is meant by relevant implications.

The database must present data. This can be done in various ways, depending on the assessment task and the database application used. Strategies may include the use of forms, reports or web-based interfaces.

Data integrity and testing should show the database functions as intended, and that the data is relevant for the purpose and end user. Evidence needs to include testing to show that the data in the database is correct.

For Merit

Evidence of how the outcome was improved using testing procedures is required. Student evidence could be provided using annotated screenshots. The evidence needs to show how the relevant implications have been addressed.

For Excellence, iterative improvement is required throughout the design, development and testing process. Iterative improvement involves cycles of improvement. For example, evidence of developing the database in sprints throughout the development process.

For Achieved

A working database is required for Achieved. The database should work more efficiently as a result of iterative improvement. Evidence could be supported by screenshots that show iterative improvements. There is a dedicated clarification document which expands on what is meant by iterative improvement.

For Moderation

Where the evidence uses PHP and SQL or similar web-based methods, a link to show the database running on a webserver should be provided, rather than submitting the evidence to be unpacked into a webserver by the moderator.

Alternatively, a screencast showing the functional database and website operation could be submitted. The video should include some voice-over or subtitles, describing what is happening and explaining what the database does and how it functions.

Assessors will need to ensure that all prepared evidence, such as voice-over video files, online version control tools or separate testing documents are visible to the moderator. When files are password-protected the access settings should be changed appropriately to allow the moderation process to occur.