Please enable JavaScript.
Coggle requires JavaScript to display documents.
Cultural Threads Queensland - Coggle Diagram
Cultural Threads Queensland
Developer
Data Sources
Data extracted from the Indigenous languages of the map.csv, which is located on the Queensland Government website.
The database was first created in 2020 and hasn't been regularly updated since.
The original .csv file was in a standard format but was saved as a UTF-8 which allows for better handling of diverse character sets.
Relevant Data: Language, Pronunciation, Introduction, Dialect, Common Words
Additional Data: Location
User Experience
Registered User
Register mandatory details (full name, email and password)
Redirected to book page after completing registration. Fill out booking details (location, venue, date, time)
User gets a confirmation message for their booking outlining the details.
From the confirmation page, they can go to learn more about Indigenous languages.
Filter through languages and the corresponding data will be displayed: pronunciation, introduction, dialect, common words as well as location.
Admin User
Through the register user page, admin users can select to login.
Admin user enters their login details (email and password).
Admin user is redirected to the manage bookings page, where they can approve, waitlist, or decline bookings for registered users.
User
Chloe (REGISTERED)
Currently holidaying in QLD from NSW where she visits various historical landmarks.
Wanting to book a yarning circle with her travelling group.
Has no prior information on the dates available or the offered locations.
When visiting a yarning circle, she would like an app to provide her with historical information on the traditional owners and languages.
Jennifer (ADMIN)
She oversees the utilisation of Aboriginal landmarks within Ipswich/Brisbane/Moreton Bay regions.
Does not strictly work from a desk and travels between cities each day.
She accesses Charlottes spreadsheet once a week to check if a landmark has been booked, then adds it to her own spreadsheet.
Makes it easier if she can access the booking data in one place with all the information she needs.
Charlotte (ADMIN)
Manages and confirms all yarning circle booking requests in QLD.
Currently handles requests through unorganised emails or phone calls.
Confirmed bookings are entered into an excel spreadsheet.
Mostly works out of office as she also manages other bookings events on behalf of QFNTC.
Using a mobile application is necessary for Charlotte to access new requests throughout the day.
Client
Constraints
User
Data is relevant to Queensland.
Accessibility Constraint: encounter difficulties to access application due to internet connection, location, or disabilities.
Device Limitation: users access the application through different devices.
Platform Constraint: users access application from various platforms such as Samsung,
Motivation Limitation: aimed towards Queensland residents and interstate tourists wishing to attend a yarning circle.
Developer
Time Constraint: 8 weeks
Device Constraint: access to different type of laptops such as HP or Microsoft Windows, which operate on different systems.
Software Constraint: has access to limited resources such Balsamiq, Thonny (tkinter) and Diagrams.net.
Skillset Limitation: due to the developer current skillset in design and coding, limiting their ability to create a more complex prototype.
Criteria
Self-Determined
SD1: ensure data used is relevant, discard unneeded data.
SD2: Cultural Threads Queensland will include necessary features for both guest and registered users.
SD3: interface designed to avoid errors. Establish two different authorisation levels for guests users and admin users.
SD4: Maintain consistency and uniformity by standardising data.
SD5: application is easy to learn and focus on simplicity. Eliminate unnecessary elements to declutter page.
SD6: must produce accurate and expected results without errors.
SD7: identify and remove duplicate records and ensure no data is lost.
SD8: incorporating colours of ochre, yellow, brown, white, red and lack - symbolises Indigenous people and connection to culture.
SD9: well-defined hierarchy and elements are organised.
SD10: choosing a sans-serif font like Helvetica enhances legibility and modern appearance.
SD11: pseudocode must be straightforward and concise language. Logic is easy to follow, using indentations and comments.
SD12: pseudocode addresses the problem, conduct testing to confirm algorithm is correct. Avoid using break statements.
SD13: avoid unnecessary details that will clutter the pseudocode.
SD14: use appropriate data structures and algorithms to minimise resource consumption. Use FOR loops instead of IF-THEN-ELSE.
SD15: reliability of pseudocode relies on error handling, testing, usability, and predictability. Algorithm should be able to manage errors and exceptions.
SD16: algorithms must be maintainability, readability, modularity, testability and proper documentation.
SD17: documentation and comments should be included in the code.
SD18: code should be modular and reusable, well organised functions and classes that reduce redundancy and improve maintainability.
SD19: error handling should be prioritised, incorporating proper exception handling to manage unexpected inputs.
SD20: efficiency and performance are important, ensuring algorithms and data structures are optimised.
SD21: code should be clear and structured, using meaningful variable names, indentation, and proper formatting.
Prescribed
PC1: develop a mobile application for QFNTC that allows visitors to book yarning circles throughout Queensland. As well as learning about the languages.
PC2: caters to Queensland residents and interstate visitors by enabling them to submit booking requests. QFNTC admins can manage bookings.
PC3: registered users can filter through language and the corresponding data will show up (introduction, pronunciation, dialect, common words and location).
PC3: generate a prototype of the application which can be further assesses and improved.