Please enable JavaScript.
Coggle requires JavaScript to display documents.
TMDB Data exchange - Coggle Diagram
TMDB Data exchange
The Client
-
-
Constraints
Developer Environment
-
-
-
Legalities, such as copyright
-
Functionality, Usability, Efficiency Criteria
-
Self determined
-
-
-
SD4: Ensure compatibility with screen readers (VoiceOver, TalkBack).
-
-
-
-
-
SD10: Support accurate interaction with minimal digital literacy, promoting learnability and usability.
SD11: Use proximity, balance, and alignment to enhance visual chunking and learnability.
SD12: Use repetition, spacing, and proportion to establish visual harmony and predictability.
-
-
-
The User
Personas
Persona 1 - Sophie
Motivations - Passionate about discovering films and learning about global cinema. Wants updates on the latest movie trends and genres
-
-
Persona 2 - Michael
-
Digital Literacy - Well versed, uses multiple devices
-
-
Impacts
PCI1 (Transmission): The application must provide dynamic data feeds of up-to-date movie and TV show information.
-
PCI3 (Use): The application must allow users to investigate the most popular movies and TV shows by genre and/or language.
PCI4 (Use): The application must present the data in a visually meaningful way based on user selections.
-
SDI2 (Use, Accuracy): API responses must be parsed and filtered accurately (e.g. genre, language).
SDI3 (Use, Dissemination, Ownership): TMDB’s terms of service must be followed (non-commercial, attribution, no redistribution).
SDI4 (Storage): User requests must not be stored or retained by the application to maximise an efficient interaction.
SDI5 (Use, Accuracy): App must provide clear error messages and handle errors appropriately.
SDI6 (Dissemination, Ownership): Data should only be temporarily displayed, not saved or shared externally.
SDI7 (Use, Dissemination, Storage): The app should be free to ensure accessibility and legal compliance.
SDI8 (Dissemination): Data, sensitive or not, should only be used for its intended and explicitly stated purposes.
SDI9 (Dissemination): As the application is to store user login details, it must comply with the Privacy Act 1988 (Australian Government, 2024) and the Information Privacy Act 2009 (Queensland Government, 2009).
The Developer
Data
-
Data types in the JSON object include Strings, Integers, Floats and Arrays
-
-
-
-
-
-