![]() |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| A. Storyboarding, Logging
and Archiving: 1. Storyboard A direct translation of our group diagram, which breaks text down into 4 main characters with 8 scenes each based around an event. This is the fundamental structure of our product and its interactivity; which centres around the users choice of perspective. Used to compile a list of the core assets needed to create the product- 32 QuickTime video clips, 16 screens of graphics, Flash clip for the intro, & Graphical interface to display product, and then assign team member roles. As Director Programmer it provided a reference in compiling a list of Director/Lingo considerations that would need addressing i.e. how could I create a menu which is controlled by scrolling buttons in Director? (See ‘Personal Activity Log’ for full list in Q&A format). Used in creating paper prototype, as our product was quite complex this provided me with an essential reference when building the product, as at a glance I could see character, location, time-all info I had to input into Director to make product work & make sense. 2. Logging A group Blog was used to post minutes from each group meeting, product
ideas, tutorial feedback and usability results:
Christiana created 3 assets logs in Excel: 1. DSWMEDIA - of all media elements in product Having a description of each file helped me locate assets more easily, as there were so many similar files in the product. Also, having a reference for uncompressed graphics made them easy and quick to locate when changes needed to be made during product building. I backed up the ‘Sites’ folder (with all .dir files, images & .html for product) daily using usb flash drive, and also zipped and emailed it to myself 3 times each day. Once QuickTime was added I zipped and stored ‘Sites’ on the usb drive and burnt onto CD daily. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||