Please enable JavaScript.
Coggle requires JavaScript to display documents.
Road Closures Application - Coggle Diagram
Road Closures Application
criteria
self-determined
provide the user with an alternate route to avoid road closures that are on the way to their destination
persona
Ninan
cant be in multiple places at once so needs road closures monitored so people can avoid the sites he isn't at
Bernadette
needs to know the road closures before she leaves to her destination on time
Adam
needs to see road closures so he can plan his journey
prescribed criteria
provide the users with information on adjoining suburbs
can filter results based on filter options and be easily readable
should pull data from one or more JSON files utilising the BCC API
can create account and register to receive notifications about road closures
must comply with the web content accessibility guidelines
security
hashing
anonymisation
tokenisation
encryption
data masking
requirements
RESTful web services
client server architecture
cacheable
stateless
layered system
resource-oriented
uniform interface
CIA triad
integrity
data is accurate
data is trustworthy
data is complete
availability
accessible to authorised user when they need it
reliable and timely access to information
confidentiality
data is only accessible to authorised users
protecting data from unauthorised disclosure
principles
Australian Privacy Principles
direct marketing
cross-border disclosure of personal information
use or disclosure of personal information
adoption, use or disclosure of government related identifiers
notification of the collection of personal information
quality of personal information
dealing with unsolicited personal information
security of personal information
collection of solicited personal information
access to personal information
anonymity and pseudonymity
correction of personal information
open and transparent management of personal information
principles of design
methods
contrast
repitition
position
goals
emphasis
harmony
balance
Software useability principles
error prevention and handling
efficiency
user control
learnability
feedback
visiblity
consistency
accessbility
simplicity
user testing and iteration
storage
local storage
coding languages
html
CSS
PHP
javascript
SQL
methods of data exchange
JSON
cons
only supports a limited range of data types
lacks some security features
doesnt have built in validation
pros
can represent the same data in smaller files making data transfer easier compared to XML
extends from javascript
easy to read
XML
cons
more complex requiring a tag structure
leads to higher storage and transportation cost
much harder to read compared to javascript
pros
more flexible
supports more complex data types
is not platform dependent