there were so many thigns wrong with that algorithm
all year they've been telling us
"use intrinsic documentation"
"comment your code"
"make your code elegant"
that algorithm goes against everything they've ever tried to hammer into us
for part a i put that if the message header is anythign else, eg if there was an error in transmission or anything, the whole system would shut down. I think i stuffed the second part up because I thought systemstatis was passed on from one of the terminals cos it says inthe text that at the end of the day, the supervisor shuts down the system by entering system status = off
the deskcheck: hey a deskcheck won't help solve such a crappy algorithm. I put down that eventticketsavailable could be negaitve, and that a ticket is issued even if if there are no seats.
i didn't finsih part b
and why did they read system datae and systemtime twice?