Please enable JavaScript.
Coggle requires JavaScript to display documents.
Brisbane Explorer Data - Coggle Diagram
Brisbane Explorer Data
Code (Data Exchange)
Exchange Processes
Whilst the JSON code has been retrieved, it must be converted in to swift using the decoder. This will allow the data to be manipulated and displayed later on.
Store the data in arrays by adding each record into the array of structures. This can then be extrapolated on the screen for users to interact with.
Retrieve the JSON code from the dataset to the app. When the dataset is updated or modified, the app will be able to transfer the new changes.
Connect app to the data store using getData function. This will allow the fields and structures from the dataset to be displayed on the app later.
From the arrays, the data will be displayed using structures and data types. For the prototype, the data will be showed when a 'Retrieve Data' button is pressed.
Security Strategy
-
CIA triad
Confidentiality
When signing up, users will be taken to the actual sign up URL which is most likely encrypted by Brisbane City Council security team
Ensure the app does not require users to enter any personal details that may be compromised - the app will be free to interact with without creating a profile or account to join.
Integrity
Data displayed on the app will always be taken directly from the Brisbane City Council to maintain integrity and accuracy of information
-
Data
Chosen fields
Location (String)
Location was chosen because it explicitly depicts where the event is being held. This is very important for users as it informs users whether they will require public transport or other means of transportation to arrive at the destination.
-
Description (String)
The Description field was able to add further explanation as to what each event comprised of. As well as this, the descriptions can also encourage people to partake in the activities which is a key intention of the Brisbane City Council.
Sign Up (Bool)
The Sign Up field was needed to notify users as to whether they required to sign up to the event prior to its commencement. Without this information, some users may show up to the event and be denied access, resulting in frustration.
Title (String)
Title was an important field because it provided a brief insight into the activities of each event. Since there are a range of users from different ages and interests, it is important that the activity titles are clear to avoid confusion.
Payment (Bool)
While the payment information can be located in the description field, this boolean provides a simple 'true' or 'false' answer to depict the event details clearly.
Event ID (Int)
Event ID was chosen because it uniquely identifies each event with an automatic value. This makes the organisation of the data efficient, and ensures that there are no accidental repetitions of events. The ID will also be available as a reference to public since qualitative data can restrict the ability to find specific fields.
Sign Up URL (String)
Following the Sign Up field, the URL is also an included field. This allows users to directly sign up when they are interested in an event.