For this assessment you must use GitHub Codespaces
Your teacher will give you a link to the GitHub Classroom assignment based on this repo
If you do not have a game or your game is not appropriate for the database assessment you can copy this game.
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.