Please enable JavaScript.
Coggle requires JavaScript to display documents.
IA3 - Part 2, Note: JSON list is limited to 200, RSS and XML are to 1000,…
IA3 - Part 2
Developer Problem
Coding Environment
Data
Brisbane event List
eventID - Numerical integer value, neccessary for efficient retrieving and storage of event specific information
-
-
-
-
-
openSignUp - Boolean text provides a neccessary input to determine whether to display a sign-up url or to display
-
pastDeadline - Provides the second input to determine whether to display the sign-up URL or to state they have missed the deadline
-
-
-
-
eventActionUrl - Provides a functional URL to a calender function which can embed the event into the Users, "Outlook Calender" or Apple Calender
-
Although image links and size specifications were included in the dataset, this information was not included as the user could source relevant imagery from the event sign-up information. In addition to this, the user may not have an internet connection prior to or during the event itself in which they may be using the application. Furthermore it is unknown whether all events will have, or will always have, image information.
Data Security
Integrity
Source is secure and is unlikely to be altered due to the nature of the information being publicly available, containing no private or immediantly critical information
Failure will result in all users being shown false information and potentially being physically directed to harm or having their locally stored personal information altered.
It would be optimum if a secondary/backup location of the same information could befound allowing information to be cross-checked in order to allow the application to determine significant, unexpected, variances in the information. This would allow the app to stop, prevent misguiding users until the discrepencies are resolved by administrators.
Confidentiality
Information is only Broadcast, unencrypted, from the official Brisbane City Council website - personal information is stored internally only
Personal information consists of potentially event preferences, and planned event locations and times. Does not monetary or personal location information and likely will not explicitly require information individualising the user
Failure may result in an individual user tracked to locations or the users identity/outgoing preferences being leaked
A form of local encryption should be incorporated into the UI to prevent personal information being accessed
Availability
Source of event information is owned by a government organisation and is active/online 24/7 and requires an internet connection to allow data transfer
-
In the event of failure by DDOS attacks to the brisbane data website, in the event the retrieved information remains until updated, all users are allowed to operate off of data that is no longer gurranteed to be up to date. All user's will still have access to personal information
The application to should be designed to store the most recent information locally and/or explain to the users the servers are currently offline
-
-
-
Note: JSON list is limited to 200, RSS and XML are to 1000
-
- This is beneficial as realistically the user will not require that many events and because by reducing the total data sent,
- less time to download the information,
- improves apps response speed
- reduces the likelyhood of significant time
spent requesting missing bits of data being resent during transmission
-
Error: In the event the data is updated and the user has stored a copy of this information, The information will not be removed
- This means event data will remain even if the actual event has passed which is a flaw