Please enable JavaScript.
Coggle requires JavaScript to display documents.
Web application proposal - Coggle Diagram
Web application proposal
Data solution story
programming and development tools
local host
tables
signing in/logging in
user details
only accessible to admin
media uploads
connected through primary keys
key: student Id
Algorithms (pseudo code)
connect in a logical way
efficient(fewest no. steps)
effective (does what it should)
visual studio code
create html doc to connect refined data to local host tables
coggle it
exploration of the task to identify criteria and requirements
lucidchart
create site mao
create data flow diagram
Developer problem
evaluation
Algoritms
against proto-types
against criteria
prescribed
self-prescribed
impacts
testing strategies
need to be tested
functionality
compadibility
useability
interface
security
performance/load
how to test
lighthouse
survey across year 12 cohort
user interface
visual communication
elements
space
line
tone
form
shape
colour
texture
scale
proportion
principles
balance
contrast
proximity
harmony
allignment
repetition
heirachy
useability principles
accessibility
utility
safety
effectiveness
learnability
page flow
flowchart
constraints and limitations
legal
copyright
representation
data
time
4-6 weeks
client problems
scope and boundaries
scope
greater security
hashing password
no unnecessary information asked for
boundaries
impacts
social
less environmental impacts
more inclusive - everyone can contribute
economic
cohort will save money
personal
safety of users
User Problem
Target Audience
proto personas
Indigo (contributor level acceess)
add entries
date
image
Mary (administrator level access)
view:
Student number
first and last name
email address
passwords (Hashed)
Maggie (public access)
existing solutions
An actual yearbook
user story
why should i be made?
whos it for?