Please enable JavaScript.
Coggle requires JavaScript to display documents.
IA3 Part 2 – Data Exchange Solution - Coggle Diagram
IA3 Part 2 – Data Exchange Solution
Client
Expectations
Web app proof of concept
Display Community Hall info + Food Truck info clearly
Criterion
Prescribed criteria
Halls: names, locations, hire conditions, hireable spaces, facilities, floor/site plans
Food trucks: food style, promo image, URL, social media link
User registration (username/password)
Accessible on desktops, laptops, mobiles
Retrieve + display API data (max usability)
Effective & efficient code
Constraints
Must use Brisbane City Council APIs
Limited timeframe (school due dates)
Only proof-of-concept, not full production
Users
Personas (summary)
Hayley (dance club organiser): needs halls for classes + food trucks for intermission
Daniella & Rakesh (parents): need birthday venues + catering options
User Needs
Easy navigation (hall + food truck search)
Accurate, updated info (API linked)
Accessible across devices
Simple login/booking system
Developer
Self-Determined Criteria
Self-Determined Criteria
Data sanitisation + cleanup of API fields
Smooth user experience (responsive UI, load speed)
Scalability for more datasets in future
Secure handling of user accounts & booking data
Data Structures
Data dictionaries (fields from Halls + Trucks APIs)
JSON format (nested, hierarchical)
Identify useful vs not useful fields (cleanup)
Algorithms & IPO Charts (min. 3)
Retrieve Hall data (Input: API JSON → Process: parse/transform → Output: display list)
Retrieve Food Truck data (Input: API JSON → Process: parse/transform → Output: display cards)
User Registration/Login (Input: username/pass → Process: validate, store → Output: access granted)
Data Flow Diagram (DFD)
Entities: User <-> Web App <-> APIs (Halls + Trucks)
Processes: Retrieve → Transform → Display → Store (accounts)
Evaluate
User Testing
Testing table (criteria tied to survey questions)
Ratings for usability, clarity, load time, accuracy
Visual Communication Features
Principles: proximity, alignment, repetition, contrast, balance
Elements: colour, line, shape, texture, icons, typography
Usability Principles
Accessibility (devices, inclusivity)
Effectiveness (does it work?)
Learnability (easy to use)
Safety (no data leaks)
Utility (meets real user needs)
Evaluation of Criteria
Prescribed: was each requirement met? (link to testing)
Self-determined: was UX, scalability, validation achieved?
Recommendations
Improvements for unmet criteria
Use user testing feedback as evidence
Suggest security or UX upgrades