Please enable JavaScript.
Coggle requires JavaScript to display documents.
IA3, Proof of Concept - Coggle Diagram
IA3
-
-
-
-
-
Requirements
Prescribed
Non-Functional
The web application must accommodate for users with accessibility issues and follow the Australian Accessibility Standards. (Functionality for alternative text, screen readers, keyboard navigation, colour-blind friendly colour scheme, Etc).
The website must adhere to legislative requirements (Privacy Act, Copyright, Safety Design principles etc)
Functional
The proof of concept must have a web application client and server back end and API using Flask, Python and SQLite.
The proof of concept must have strong data security for capture, transmission and storage of data.
-
Self-Determined
Functional
-
The web application must allow the user to login, view interests, activities and other users profiles.
Non-Functional
The web application must follow the useability principles such as Utility, Learnability & Effectiveness, Accessibility and Safety
The web application must follow the Contrast, Alignment, Repetition and Proximity design principles.
-
Proof of Concept
-
-
-
-
Requirements
Prescribed
Functional
-
The web application must use HTML, CSS, Python, Flask and SQLite.
Non-Functional
The API must provide personal data about the member such as name, age, year level, boarder/non-boarder.
The API must provide non-personal data such as activities, hobbies.
Self-Determined
Functional
The web application must allow the user to view profile data, interests, activities and other users profiles.
The web application must have a login feature with security features such as password masking and hashing.
Non-Functional
The web application must have no errors with code done to a high standard with comments for ease when making improvements in the future.