Please enable JavaScript.
Coggle requires JavaScript to display documents.
Clean Energy Regulator (CER) - Coggle Diagram
Clean Energy Regulator (CER)
Functional
UI componets
interactions with user
layout of UI
simple layout that is easy to understand and flow
clear button and variable names
simple instructions
use of balsamic mockups to create UI
key elements
tables
entry boxes
treeview
buttons
instructions
Data Interface
specific dataset
File format for dataset
consistent table/variable names
thought-out order of columns
Data structure
alphabetical order
numerical order for postcodes
split into states
consistent flow and tables between all systems
cleaning data
removing errors within dataset
removing double ups within postcodes/suburbs
removing any blank rows
restructure/filter data
collect new data
admin updates
Coded components
code modulus (algorithims)
process of outpit
data collection
SQL database
IPO chats
DFD's
Usability of Program
Allow the Admin user to update the database
Veiw Records
Add Records
Add Records
Delete Records
Allow the student user to filter the database records on:
Any postcode or suburb
any single year (2014-2018)
any single energy type
Solar
Solar Hot-Water
Hydro
Winds
Installation or output (KWh)
Restrict Admin to three logins
The Clean Energy regulator (CER) requires:
the database (called CER.db) is to be created
data to be imported into the database
Non-Functional
Legal considerations
copyright
clean energy regulator (CER) 2020
intellectual property
scientific information
specific data
must be up-to-date and from a reliable source
contractual arrangements
government funded app for school students yrs 8-10
free for students to use
Economic considerations
cost
app is to be free and is sponsored by the Australian Government
available recourses
the developer will be given resources from the government to create the app
will receive up to date information to create the app
maintenance
the data within the app can be updated at anytime by the Admin
Environmental considerations
appropriate for use within Australian schools
simple app that can be used by anyone
available for different types of computers and screen sizes
Aesthetic requirments
organisation of program
consistent flow throughout pages
consistent colours (60.30.10)
Window Headings
Hierarchy of information
must be on each window
Window titles
Must Appear at the top of each page
appropriate for the window
different in each window
Elements
Input that is mandatory is clearly labelled
clear format
dates
months
years
locations
non-mouse navigation
sequential access to window elements
can be sued for different functions
entry boxes
radio buttons
checkboxes
buttons
Error messages
clear
specfifc
does not make the window completely reset
Accessibility
contrast between text and background
general instructions for the user input at the top of window
colour contrast