Friday, October 19, 2007

Week 10: Assignments

To do for next week:

  • Edits to storyboards (assignments below)
    • changes discussed in 10/18 meeting
    • further development if missing test/activity items
    • review images for your section, specify which ones to use where
    • if lacking images, note what you want and where - including illustrations, graphics
    • if lacking content, note what you need and where (specifically test/activity items)
    • tell Emily what content/images you need
  • Lesson 1 - HueiHsien, Emily
  • Lesson 2 - Ahram
  • Lesson 3 - HueiHsien, Remi
    • HueiHsien add in all content
    • Remi help develop test questions
  • Lesson 4 - Emily
  • Unit 2 - Kazu
  • Prepare flash file for development
    • interface, symbols, design guidelines - Daisy, Emily
    • plan for consistency between files (Flash guidelines - layers, scenes, names, etc.)
  • Submit documents for review - Emily
  • Contact Holly for content needs - Emily

Team meeting: October 25, 4-6pm, 603 Aderhold
(regular meeting room, Em check availability)

  • show group plan for Flash file
  • divvy out development work based on storyboards

Wednesday, October 17, 2007

Prototypes and resources

Storyboards
Coming soon

Edited content for storyboards (10-17)

Prototype resources

Week 9: Report

A good bit has happened since my last posting. Our Task Analysis, Performance Objectives, User Profile, Hardware/software Specs, and Formative Evaluation Plan were all approved by our client.

Daisy has done more work on our screen design and treatment rationale. This document will be coming together very soon with the supporting info for the learning system design. This part of the project will be designed in a pre-set template, so this shouldn't be too much to add.

Kazu, HueiHsien and I have brainstormed ideas for our interactions and test items. We presented these to the team in our last meeting. This past week, while Daisy has done more graphic development, the rest of us have each worked on a prototype for a particular lesson. These should be based on the storyboards presented last week, as well as our team discussion. We're using a basic screen design to determine how much space we have for content and activities in our prototypes. This work will help us line up work for assembling our module. Some of our interactions will require a bit of creative programming and our SME's support through providing and approving test content.

I've also recruited Myra, one of our 6200 consultants, to help look at the page flow of our content, as well as final edits. I really hope we'll be able to divvy out work to our other 6200 consultants soon. I expect we will have graphic work and other parts that we'll need help on.

I've consolidated all of our storyboards into one document that details our project from the top of the learning system to lesson activities. With a little bit of elaboration, this should serve us well for the learning system documentation.