AS91902 - Use complex techniques to develop a database
|
Brief:
Lizard People! Lizard people are everywhere! They are in the school.... They are watching.... Design and create a database using Microsoft Access (Lizard people hate Microsoft Access) to record suspicious behavior. Each instance of suspicion needs to record where it happened (H block, Admin Block etc). To avoid multiple entries only some types of suspicion will be allowed. Users should be able to view all the instances, update locations and types of suspicion. In addition, users should be able to search by date or name for records. Users should also be able to delete the currently viewed suspicious members entry (REMEMBER to make a separate file for the DELETE version. Also create a backup or two) Current records are here: Download lizard record here You are going to be assessed on how successfully you: - plan the outcome, tables, datatypes, queries, and input/output wireframe sketches. - apply complex techniques to logically structure, organize and query the data - use efficient tools and techniques while producing your database - demonstrate iterative improvement throughout the design, development and testing process, to refine and improve the quality of your database outcome - present data effectively for the purpose and end users through the interface. - address relevant implications (e.g. functionality, usability, security). Complex Techniques are:
|
|
Planning and Design
|
You will need to provide documentation showing:
Design of the structure of the data Provide: - An analysis of the data requirements of your chosen context to help you decide upon appropriate fields, tables and data types. - A description of the table/s and data types used. - A diagram showing how the tables are linked together (ERD) - A list of queries/features to be implemented with test data for each query. - Wireframe Sketches of bot your forms(input) and reports(output) Hint: Use https://app.diagrams.net/ Mockups for wireframe sketches. For Excellence: Show Iterative development of your database, If there are changes to your forms or database/connections you need an updated query/wireframe etc. If there are updates because of testing, you will need to show a new version of the wireframe/query. |
Output Wireframe Example
Database & Interface Construction
|
The Interface must present the data appropriately for the task and the end users. This means creating a report button that will print a report based on the specifications mentioned above.
|
For Merit: you must structure and organise your data in a logical way.
This means that redundant data is removed and queries make it easy to find items in the database. For Excellence you must do two things: 1.) Use efficient tools and techniques, which means being efficient with the database structure, number of queries code in scripting language. 2.) Data should be presented in an effective way to fit the purpose of the end user. This means using drop down lists, check boxes and good design principles. |
For Merit: You need to show that you have improved your outcome through testing procedures.
This would mean gathering and recording feedback then making improvements to the functionality of the database. For Excellence: You need to show evidence of Cycles of Iterative development, This would mean having multiple versions of documentation and designs that have been improved through testing. (I would expect at least 3 cycles of development for excellence). Click here for more information: https://www.freybergdigital.co.nz/iterative-development.html The bottom of the documentation has the iterative development section. |
Testing and Refinement
During the development of the database and interface, you will be expected to apply ongoing trialing and testing procedures to iteratively improve the quality and functionality of the database, throughout the design, development and testing of the database and web interface. Ensure that the data is logically structured, organized and queried.
You should be testing to ensure you have addressed the implications that you identified above and for the required functionality:
Testing of the final outcome may include screenshots with a table of what has been tested or a screen cast with an explanation showing that the database and interface have been tested and works as expected. You should provide annotations to explain what is being shown in the screenshots or screencast. |
|
Relevant Implications
There are a range of implications that are relevant to your outcome. You need to provide evidence of how you have identified and addressed these in the process of developing the database and web interface. For Example:
- Does your interface block access to different tables? Can a hacker easily get in and play with the settings? Does the admin have full rights to change things? - Does your database address functionality;
|
How do I hand this In? - File Management
|
The root directory of your website should look like the image to the right.
Ensure that under images you have given me all versions of the database/documentation Once you have done this, zip the entire folder up and name it like this: MarkSutherland-AS91903-Attempt1 |
|
