MySQL - used to manage, store, and manipulate data within the system. SQL could be used to store information relating to the recommendation status of a given indoor or outdoor event, although there is existing digital infrastructure available for sports directors and users of the system to output messages regarding the status of a given event (e.g., the Terrace app, Facebook, Twitter, etc.)

PHP - used to implement algorithms, manipulate data, and create the system more generally. PHP will be used to filter through the supplied API dataset and make algorithmically determined suggestions/recommendations to users. In essence, PHP algorithms will be implemented to ensure the given weather conditions of a date are satisfactory for the execution of a given event (if they do not meet preset weather thresholds, then the PHP program will recognise this and output the appropriate recommendation (presumably stating that the event is not recommended to be undertaken))

HTML - used to structure the user interface. HTML will be used to structure the interface by which users access the system. A well-developed interface that takes into account principles of usability and accessibility (alongside the elements and principles of visual communications) will increase the overall effectiveness of the system for users and thus the wider College community

Bootstrap, CSS - used to implement the desired stylistic design and aesthetic of the College (according to the College's style guide). Bootstrap will be used to provide a meaningful and useful aesthetic design to the interface of the system so as to ensure that optimal effectiveness and usability

Javascript - used to create a responsive web application; used to implement interactive behaviour within the system. Javascript is unlikely to be used extensively in this particular system given that only basic user interface outputs are expected to be used

Currently there are many avenues by which sports directors and administrators of the College community disseminate information relating to the cancellation of a given activity of a sport (e.g., Twitter, Facebook, Instagram, etc.). As such, since there is no central mechanism or system by which sports directors and other relevant authorities are able to provide this information to the community, there is a need for a centralised digital system. This system - the focus of this folio project - will aim to not only allow administrator users (sports directors and other authorities of the College) to publish information from a central interface (or to access all possible avenues of publication from one central source), but will also provide recommendations based on the weather and air quality of a given date

Relying on data from a central source of information (or multiple similar sources of information) is important given the fact that data may vary between sources. E.g., if air quality data was to vary considerably from source to source, then this would place students with respiratory illnesses and issues in jeopardy, as activities directors may make different, potentially dangerous decisions depending on their source of data

BOM API dataset - the Bureau of Meteorology makes a number of real-time forecasts available freely via the web. This data - which includes multiple weather and air quality datasets and properties - could be used as a basis by which to make recommendations within the system

Open Weather Map - the Open Weather Map API (available on Rapid API) supplies a varieties of forecasts for numerous major cities. This API cannot be used, however, as it does not include weather or air quality data for the city of Brisbane

Weatherbit - Weatherbit APIs include data for both standard weather properties (e.g., maximum and minimum temperatures, wind speed and direction, etc.), and also air quality data (specifically, the level of particulate matter within the area - a property of air quality data that is significant given the fact that particulate matter levels affect the playability of activities for those with asthma and respiratory illnesses)

Visual Crossing Weather - Visual Crossing Weather API provides instant access to both historical weather records and regularly updated forecasts, although - as compared to other APIs available for free - it only includes a small range of weather properties, and does not list data relating to wind direction or particulate matter levels, for example

The core capability of the system is to receive data from an API dataset and then filter through this to achieve a recommendation on the suitability of the College's outdoor and indoor activities. In general terms, this will require the system to first retrieve data from the API, convert it into a form that is compatible for use in PHP, and then filter through the dataset to determine which weather properties make a particular outdoor/indoor activity unsuitable on a given date (if any)

Users should be able to use two key filters. Firstly, given that it is likely users will want to plan ahead and make suitable arrangements for a given activity, users should be able to filter by date (i.e., choose a specific date for which a recommendation is then made). Further, as users may only be interested in one particular property of the weather, they should be provided with the option to choose which aspect of the weather the recommendation is based on. For example, the user should be able to generate recommendations on all properties and only maximum temperature if they so wish

An advanced version of the system should ideally automatically update event databases of the College (if such databases exist) to reflect the most recent recommendation made by the system. Although this capability is not developed in the system outlined in this folio, it should be implemented to remove the need for users to publish updates and announcements by themselves (i.e., this capability automates this process for users of the system)

In order to ensure users of the system have an idea of the amount by which an event is not suitable (e.g., by how much the temperature of a given date exceeded the maximum preset temperature value), exact numerical justifications should be provided to a user if an event is deemed unsuitable by the system

Due to lack of experience in Javascript and jQuery languages, responsive elements within the developed system may be limited in number. This limitation likely means that users of the system will experience a less effective and useable user interface, therefore detracting from the overall effectiveness of the solution/system

Some APIs may limit the number of requests or accesses within a given time frame (e.g., free accounts using the Weatherbit API 'Weather' may only access the API's data 35 times every day). Without an effective proxy to prevent APIs tracking user data, it may prove difficult to properly access the data of APIs used in the developed of the system. Therefore, this particular element of the development process is a limitation

Since only a set range of weather properties may be found within each API, an entirely comprehensive recommendation regarding activities may be difficult to obtain. That is, there may be meteorological datasets that contain a greater amount of information regarding the weather or air quality of a given day; this data set would be able to more validly and reliably recommend activity suitabilities, as it contains a greater amount of applicable information

API developers may choose to restrict access to users who request data from the API in regular, high volume fashions. Therefore, since the development of the system will likely involve a degree of trial and error, it is possible that certain API datasets may suddenly become unavailable (such as in the case of the BOM API weather forecast dataset, for example)

As per the technical proposal supplied at the beginning of the project, the web application ('system') must incorporate the use of dynamic event data. To successfully implement this key capability, live weather and air quality data will be utilised (e.g., BOM API dataset, Weatherbit APIs, etc.). Such datasets are dynamic in the sense that they are based on live data from various meteorological sources, and therefore change in response to real world events and weather conditions

The developed system must be accessible from multiple platforms. This key capability is particularly significant given that users who rely on the system (presumably parents, teachers, coaches, and activity directors of the College) may not always have immediate access to a laptop. Therefore, it is crucial that they are able to access the system from other devices, such as a phone or tablet. Without this key capability, it is possible that the effectiveness of the system be significantly hindered