Please enable JavaScript.
Coggle requires JavaScript to display documents.
Big Brekkie management system (Developer problems (Data environment…
Big Brekkie management system
Client problems
Challenges to the sytem
Pre-existing data would need to be digitalised into the system as older records will need to be kept as well. This will require a human to maually input the data which would take a long time.
To ensure efficient storage of data, all variables and table names have been kept short in MySQL. These shortenings would also make it harder for a malicious hacker to understand the data if they gained acces to the database.
The design and development of the system were restricted to a short period of time. This means that fabrication needed to be fast and efficient.
Why it's important
To keep perpetual, non-physical records of the big brekkie program that cannot be lost or accidentally destroyed.
To make these records easily accessable by anyone with knowledge of SQL.
User problems
Challenges to the system
Because many different devices will be used to view and interact with this system, the webpages will all need to be interactive and change depending on the resolution of the viewing screen.
Images will all require alt-texts so that vision impaired clients can access the website as well.
A lack of a computer or smart device with a stable internet access means that users can't access and interact with the system.
Some users may not be as technically dept as others. Therefore, it will be important to make sure that the system is as easy to use as possible.
Why it's important
Being completely run by code, this system is very low maintanance. The lack of hardcoded content also means that admins don't have to monitor it.
Users want the reassurance that there will be no chance of human error when being rostered, and this system will negate that.
The users want the system to be as easy to use and familiar as possible.
Developer problems
Data environment
Databases will need to be used to store data.
Personal information security is a top priority and MUST be guarded and protected by the system.
To priooritise user privacy of information and security of information, Users must have their email verefied before they are officially allowed to sign up for an account.
Data being stored must be as efficient as possible to ensure the clients are using up the minimal ammounts of resources possible.
Coding environment
Coding languages needed:
PHP
Bootstrap
HTML
Very small ammounts of javascript (to bounce user between pages)
SQL
The system will need to be able to send emails automatically.
Queries need to be optimised and efficient to cut down on load times.
User interface
Functionality
Data
Account data
Prefered shifts
login details
password (snumber)
username
Age
First name
Last name
Email
Security
An SHA1 hashing function will be used on every password to ensure that passwords are secure in the event that a hacker gets hold of the information.
The Use of a variety PHP builtins such as trim(stripslashes(htmlspecialchars(
USER INPUT
))) will be used to ensure that the user can't attack the system with any malicious code through means of PHP/SQL injection.
Processes
Login
Sign up
Displaying open shifts
user choosing prefered shift
Email authenticatin
Parent approval
Displaying user's upcoming shifts
Appearance/ interface design