Production
Storyboard
I thought about doing screenshots for a storyboard, perhaps using HTML or Word drawing tools, but I decided this would take too much of my valuable time.
Instead I drew out some initial screens on paper and scanned these in for inclusion with this report. Scans of these can be seen through the links below.
Flowchart
I also created a flow chart of the application using Word drawing tools. This helped me more than the story board to visualise what I was going to do.
[See accompanying document flowchart.doc]
Pedagogical Aims & Objectives
After using the application, learners should be able to:
- Define the different terms relevant to HTTP
- Explain the differences between a HTTP request and response
- Explain what is in a HTTP request and response
- Draw a simple diagram showing how HTTP works
The learning experience is intended to be self-paced, allowing learners to step back and forward as they wish.
The concept being covered is abstract – there is no concrete object to see when a web page is requested from a browser. The diagram is a powerful way of helping learners to visualise what is happening.
Some students may ‘get’ this quite quickly just by being given a verbal description while others need to see it in pictures to make sense of it.
Delivery Medium
Initially the application will be a stand-alone Flash movie. This is to facilitate its use for learners who may not have internet access. Thus it could be burned onto CD or copied to portable memory.