internet kiosks internet kiosks internet kiosks internet kiosks internet kiosks web kiosks web kiosks web kiosks web kiosks web kiosks kiosk software kiosk software kiosk software kiosk software multimedia touch screen kiosks multimedia touch screen kiosks multimedia touch screen kiosks cbt interactive computer based training cbt interactive computer based training cbt interactive computer based training cbt interactive computer based training kiosk-in-a-box kiosk in a box web kiosk commander interactive kiosks interactive promotions advertising web development shockwave development java development multimedia kiosks multimedia cbt multimedia computer based training |
INTRODUCTION
Whether you’re creating your kiosk in-house or via a third party, there are certain documents that should be created by you in order to translate your kiosk application from a concept into a design specification. These documents should include:
The Screen Blocking Diagram is nothing more than a graphical representation of how your kiosk interface will react with the user. You begin by drawing rectangles on a piece of paper - one rectangle for each screen. Within each rectangle (or beside the rectangle), label the name of the screen (like "Welcome Screen" or "Attract Screen #1"). If your screen has, for example, 5 menu buttons on it, sketch the buttons within the rectangle and then draw arrows out from these buttons and include the link (screen name).
A Screen Blocking Diagram will allow you, your peers, and/or the consultant to quickly visualize the project. It’s also a great way to "walk through a kiosk session" and begin analyzing bottlenecks, confusion points, information overload, etc.
Using the Screen Blocking Diagram as your guide, a storyboard is created. A storyboard is a document that contains the "meat" of each individual screen. It is usually laid out in landscape format, and looks something similar to the following:
There is no actual "industry standard" for a storyboard, other than the requirement that it very closely resembles the application on paper, so don’t be intimidated and let it flow. The Media and Text components don’t have to be "full blown" in detail. For example, the graphic requirements may be as simple as "use a ocean theme"; the audio as simple as "Welcome..."; the text as simple as "welcome.doc". When you are nearing the final version of your storyboard, consider numbering all screen, media, and text components. Numbering the references provides for easy referencing during the development phase, and also assists you in creating the Content Description Form.
The Content Description Form allows you to flesh out the Media and Text components of your kiosk. For example, if you have audio and/or video, the scripts should be contained within this document. Creating this document is especially necessary if you are going to involve a consulting firm, as it provides necessary details for proper bidding.
When designing your kiosk remember the golden rules and concepts presented within this course. You should also analyze your presentation material and make a decision about which delivery method - browser or non-browser - would work best for your application. Be aware that "mixing" the two modes (browser / non-browser) is not only possible but becoming quite popular. For example, if you decide that your Internet site will be the focus of your presentation, you may still augment the presentation at the kiosk by supplying a touchable object that plays a brief video and/or sound snippet. Now you may enjoy both the benefits of a browser-based presentation and the benefits of a local multimedia show.
During each draft of your specification documents, allow yourself - and others - to analyze your application. Have them perform a virtual walk-through. Cut out any unnecessary screens or media components. Make sure there’s always a way out, and don’t overcomplicate the experience.
After your specifications are complete, analyze your hardware requirements. Do you really need a printer? Is the attraction sound clip going to cause everyone to go insane? Do you need an enclosure? It should be apparent at this stage of design. Remember to keep it simple. |
|