Please enable JavaScript.
Coggle requires JavaScript to display documents.
RAWG API Data Exchange Solution for EB Games - Coggle Diagram
RAWG API Data Exchange Solution for EB Games
Non-functional Requirements
Impacts
Personal
Social
Economic
Limit Negative Impacts of the Solution
Usability Principles
Learnability and Effectiveness
Utility
Safety
Accessibility
Comply with Accessibility Guidelines adapted from the Australian Accessibility Standards
Elements and Principles of Visual Communication
Space, Colour and Tone, Line, Shape, Texture and Form, Proportion and Scale
Data Security Processes
Confidentialty
Protect Sensitive/Private Information
Prevent Unauthorized Access
Integrity
Protect Data from Unauthorized Deletion or Modification
Availability
Data and System Avaliability
Correct Authentication Mechanisms
Functional Requirements
Data Input
JSON Data Format
HTTPS Transfer Protocol
Restful API Framework
Request Parameters
parent_platforms
genres
metacritic
release date
Data Output
Response Objects
Only the name, Metacritic rating, parent platforms, and genre information will be available to the user
Presentation Widgets
Labels will be used to display game data to the user
Data Types
Data will be inputted into solution as JSON object, then converted into Python dictionary.
Data Exchange Methods
API Key
Requests Client Library
Constraints
Personas
Robert
Helping EB Games Customers Instore
Lucca
Avid Gamer
Renuka
Parent of Gamer Child
Application must cater to persona needs
Client Requirements
Client: EB Games Australia
Proof of concept mobile application that searches the RAWG Video Games Database API
Show data exchange between two digital systems
Data must be presented to users in a visually meaningful way
User Environment
Mobile phone compatible application
Users can filter the RAWG API and retrieve game information
Must login to use solution
Time Constraints
7 weeks to develop the data exchange solution and associated documentation
1-2 min functionality demonstration video