Please enable JavaScript.
Coggle requires JavaScript to display documents.
Data Exchange Applications - Coggle Diagram
Data Exchange Applications
Components
Data Interface - User Interface
Design principles
Usability principles
Data server - serving/API being called
API
Data Store
Data client (consumer)
Data Structures
Data exchange methods/structures --> compound types
JSON
CSV
XML
Lists, arrays, objects --> preoperative (simple) types
Boolean
String
Number
Data Security
Authentication - prevents unauthorized access
Password
Two factor authenticaion
SSD
Encryption
RSA
Asymmetric Encryption
Hashing
Verify data transmission (hasn't been intercepted)
Middle-man attacks
Success Criteria
Self-Determined Criteria
Be able to filter data
Prescribed Criteria
Must connect to API
All fields are valid and complete
Must process data in human readable
Data can be dynamic - real time data
Proto/user - personas (talk about how they can use it)
Data Server
OpenActive data frormat is JSON
Different data providers for OpenAcitive
Letsride - cycling activities
Better range of fitness activities
OpenActive dashboard lists data providers
FlexDigital - cross Fit activities
W3C standard data model is more flexible
Datastructure for each data provider is different
Main items common to all providers are name, description, startDate, endDate, duration, location.name
Data Consumer
HTTPGET to obtain data from API
HTML structure
CSS style to present data
Test in browser
Javascript to manage interactions with data sever
CORS plugins may be needed for test browsers