We started by fixing the url problem the exam board had with their scenario web pages and quickly demonstrating what css is. That might come in handy for the e-portfolio stuff briefly.
Then we talked about the outputs that Dawn’s system needs. We decided that Tracy the Consultant would produce some outputs, probably at the party (hosted, if you remember, by Gwen) and using the Spreadsheet system. Derek the Admin assistant would also produce some outputs using the Database.
We talked briefly about how there was a link between Tracy and Derek – Tracy phoning in the orders (using the list) and Derek sending the completed orders back to Tracy (with a Dispatch Note in the package). We talked about what sorts of information would need to be on each of the outputs as well.
I think we decided that there were at least 6 outputs that were needed. I’m not going to list them here as there are marks for doing that sort of thing…
Advantages of ICT solutions:
I showed you some examples of invoices and receipts at this point. Some were nice, others were hand written – these will be linked on the internets once I get a chance. We did talk about some of the advantages of using an ICT solution for the sales receipt – points like readability, speed, reliability of calculations, ability to change prices quickly, consistency of style and branding for example. Some of these were good reasons to use a spreadsheet – these will be handy in the Technical Justification section of the specification.
Then we talked about the inputs needed into the system. Tracy will need to input some stuff. She’d certainly need to input the details of an individual order (say when Daisy orders the products she wants) and probably input a few other details as well – perhaps some personal details and maybe the details of the host etc…
Derek would then take Tracy’s phone call and she’ll be dictating the party order over the phone to him. He’ll need to input that in some way into the Database. He also needs to be able to input things like new products and new consultants details into the database.
I think I probably mentioned the data flows between the two systems again. It would be a really, really good idea to come up with an Information Flow Diagram at some point fairly soon. This is a good summary for the specification section and will help you envisage the system. I even showed you how to do this more easily using a Drawing Canvas in Word (and, while I think about it, it’s probably a good idea to use a fairly small font size for this btw…).
Jobs to do:
Work on the specification and the Information Flow Diagram.