"One more feature we are keen to implement in to the design is ‘facebook’ integration, The expanded events view contains a segment which shows which of the users facebook friends are attending"
** This is the wrong tone for a design doc. We WILL implement facebook features. If we cant then we lose some marks on the implementation perhaps, but this is the design stage, and we intend to have FB.
2.2 needs some grammar/spelling/phrasing work.
List of figures?
"causing the Left Bar and Right Events to be hidden, and causing the filters page to expand out."
causing used twice, remove the second one and it still makes sense
2.2.5 - Detail the event scrollbar (David worked hard on it, it deserves a mention)
2.2.6 - spacing in title
Maybe put in some stuff about Facebook Connect and how we want it to look with it in there.
2.2.8 Administrator/USer with Admin access, not a User
3.0 - [Figure Whatever]and "Figure Whatever"
Nothing on SQL
no links between features and requirements
sequence and useage diagrams need improving, see https://duo.dur.ac.uk/bbcswebdav/pid-1830681-dt-content-rid-9158967_1/users/dcs0sad/SEG/SEG12.pdf for some really good examples
lacking in overall dataflow - user clocks here, method() is called in JS, which sends thingyGET to backend, which runs PHPSQLQuery to database, which queries THESETABLES, returns THESERESULTS, parsed into JSON and sent via HTTP to FRONTEND which INTEREPRETS and DISPLAYS
that sort of stuff. See above link for more good examples.
No error handling