Please enable JavaScript.
Coggle requires JavaScript to display documents.
Compass Koala (Client Story (Recommendations around the monitoring program…
Compass Koala
Client Story
The application must allow for the user to input and store relative Koala density data which will predict the densities across the seven distinct locations.
-
-
-
-
-
-
-
Allow user to input koala monitoring data and ensure they're able to keep count during the collection
-
Developer Problem
-
-
UX
Scientists
-
Given the option if password is forgot, link will be sent to the user through email, phone or username to allow the user to reset their password by sent link.
Homepage will appear, user information apparent, user able to chose between map, graphs and table data buttons. Each will take the user to a different section
Table page will display all data that the volunteer delivers regarding location, time and koala count. The data can be scrolled
From the homepage, scientists are able to click on the graph button allowing them to view trend models of the Koala population as a whole or as individual ages, and create a table display the percentage difference between the populations of two years
From the homepage, the scientists can also access the map where they can search by LGA (local government area), survey area, a certain year and certain age of a Koala.
Volunteers
Map displayed, when the user clicks on a location listed then the map will update to that location for the user. If the user enters further information regarding location, the map will update again.
The user will then have to enter how many Koalas, of the different ages, they have found
-
-
-
-
coding
SQL
Submit
While on an active volunteer tour, the public and scientists can add their koala count to the database
Search
Scientists can search the database by location, age of Koala
-
-
Create Graph
Used to allow scientists to determine the percentage difference between two years of Koala populations
Algorithms
Modularity
The scientist is able to login in to the application and access information not available to the volunteer for protection of the data
Sequence
When the application is run, the window will configure and images, labels and buttons will be displayed to the User
Iteration
If the user enters an incorrect sight name then a message box will appear to inform the user that the site name is not in the database.
If the user enters a wrong email or password, then the user will be displayed a message-box with the option to change password if forgotten
-
-
User Story
The user must be able to choose if they are a volunteer or a scientists. This will be decided when the user enters the application. Scientists will be able to sign in to the solution whilst the volunteers can just click the start monitoring button
Scientists
Will be able to sign into the application through a login system, this will ensure that they can access the database which is not available for the public volunteers.
Will be able to access scientific data including ID numbers, methodology, survey number and site number.
-
-
Will have knowledge of the application and therefore will not need extra learnability implements such as labels
-
Less notable counter, focus more on the overall data from that location rather than the current data.
-
Usability
be able to easily identify relationships with the data such as trend line, sum of koalas in certain areas.
-
-