Please enable JavaScript.
Coggle requires JavaScript to display documents.
PROBLEM ANALYSIS, Data Environment (Interconnecting) - Coggle…
PROBLEM ANALYSIS
User Problem
Personas
Candice McKenna
Simplistic user interface
Record data when timing equipment is nonfunctional
Insertion parameters accurately constrain data input
Keen to publish each current record holder
Requires a progressive pointy tally for inter-house competition
Lisa Thomson
Advocate for iPad and tablet use
Desires a robust interface
Data input is sanitised
Sense of professionalism
Retain the college's digital architecture
CSS style guides (blue and green)
Text and font sizes
Wants the college to publish event results
Output must be stylised through non-tangible views of data
Interested in data accuracy
Sally Leslie
Interested in aggregate house performance (Laver)
Interested in tracking student performance
Wants to monitor information from her iPhone
Wants to analyse areas of concern with participation
Grant Peel
Interested in his (student) performance
Interested in comparing his results to others
Desires knowledge of what events he has completed
Phil Shapcott
Open-source compatability with mobile devices
Desires filtering of records for each age group
Client Problem
Administrative intention
Upload of CSV data for record holders pre-commencement of the carnival
Optimistic
security model
Exportation and extraction of relevant information
Establishment of an active directory is assumed as native to the college's digital architecture (
domestic
security model)
Token-based and client-based authentication from hashed (encryption is unnecessary) office 365 credentials
Central database schema
Accurate retainment of stored data (valid types and variable length)
Ever-changing userbase
Data loading is efficient
Size of database is optimised
Database scalabilty
Horizontal
Sharding of data
Offloading of database
Vertical
Note: Defined by college architecture
Autoscalability
Migration to cloud services
Comparatively analyse individual student performance
Determine the ranking of houses through a total house points algorithms
Aggregation of data (graphs and tables)
Data of insertion is asynchronously updated
Meaningful information generated through joining of datasets
Relational database defining the cardinality between normalised tables: Events, Records, Students, HousePoints and Results
Robust data-driven system
Capacity to 'back up' through storage of a temporary 'view' and/or instantiation of the database
'Cubing' of data packets occurs instantaneously
Developer Problem
Programmed Components
Development Environment
Intelligent
HTML
Real-Time Updation
Visual Studio (ASP.NET Core)
Syntax error compilation
Native debugging
Current deployment framework (3)
Algorithmns
Efficient
Usage of indexing
Only relevant data is 'pulled' as a packet
Accurate
Inputs individual performance; outputting aggregated metadata
Mobile phone usage
Open source compatability
Dynamic variables (see responsiveness)
User Interface: User experience
Usability Principles
Learnability and effectiveness
Items are remembered through cache (Recall vs recognition)
Coherent CSS design
Contrast
Alignment
Repitition
Proximity
Accessibility
Voice commands for visually impaired
Alternative text for multimedia
Adaptive colour slider for visual impairment
Portability and responsiveness
Global variables based on device's axis (adjust to screen size)
Cross-platform compatibility with Windows and Apple
Safety
Psychological privacy
Sense of control (navigation buttons)
Feedback mechanisms (stages of loading)
Asteriks over sensitive information
Confirmation prompts to prevent data loss or corruption
Data Environment (Interconnecting)