Advanced Applied Interactive Media


Working in teams of 4, the Advanced AIM will work in a Star Structure (Ivers text, page 68-69) working either from a menu base (like Figure 7.1 on page 157 of the Finkelstein text) or with stacks working out from an interactive map (Finkelstein, Chapter 6). Keep in mind that a map does not literally have to be a work of geography, but could be an image with menu elements in a setting, similar to http://www.flickr.com/photos/cogdog/269039506/, except that you would be working in PowerPoint, as per chapter 6.

Each Team member will be responsible for developing a content track that will branch into 2, or more, sub-branches, as they move out from the hub (either an interactive map or menu base). As with the Intermediate AIM, these slides should use media extensively, with text balanced by images, path animation, and sound helping to carry the message, as appropriate. Periodic Review Slides are expected to re-route students back through an area if a concept is missed, or proceed onward when content mastery is manifest. Here our focus has shifted somewhat from a more intricate navigation structure to allow greater use of multimedia. Feel free to use a wide array of media, just be sure it ties into your topics/subtopics well. Remember that gratuitous media is distracting and detracting. Use your team members to advise you on how well your media contributes to your message.

Instead of interlacing, however, this project is expected to expand. Each content provider should plan to branch their content at least once in a cluster-tree structure (see Ivers, page 68, Figure 4.6 on page 70, and page 82), from the initial ray off of the star structure (Ivers, pages 68-69 and 82). This star structure is not limited to a single idea in the context of a single screen, though. Each of the 2 (minimum) cluster stacks coming from each tree should have a minimum of 4 content slides with a central review slide in the middle. Both branches are expected to relate to the "trunk" ray/tree stack coming from the star structure, and the star structure is expected to be cohesive. The end result should be a fairly extensive exploration of a topic. See AdvancedAIMStructure.doc.

In addition, these roles will be required from each team.
  • Producer
  • Editor
  • Navigator
  • Recorder/Reporter
With a larger team, the Producer will have more work to do "supervising" other team members, so the filing of paperwork (Intention Outline, Planning Sheets, Flowcharts, and Storyboards) falls to the Recorder/Reporter. Stack Planning Sheets and Storyboards still are the responsibility of each team member on their own stacks, the same reports for areas the Editor is working on (regarding the Introduction Stack) are done by the Editor, and the Flowchart still is done by the Navigator, but the Recorder makes sure those tasks are completed. The Recorder/Reporter also communicates with each team member 2 or 3 times per week to record what that team member is working on, and files a consolidated report to me on a weekly basis.

The Producer is in regular communication also with team members to keep them on task, to help with issues that arise in the content stack development or in the roles each team member carries. The Producer communicates with me if there are issues that the Producer is unable to work through with team member challenges. At the Producer's discretion, with the consent of other team members, the Producer may divide content development responsibilities across two or more content stack groups so that some have responsibility for text and others for locating and obtaining appropriate media. If so, the Producer will indicate to the course professor how these assignments have been realigned.

The Editor and Navigator positions are largely unchanged from the roles in the Intermediate AIM. The Editor will be responsible for Intro content stack and for reviewing all stacks for writing, spelling and grammar.

While the Navigator will not have to be concerned with interlacing this project, there still will be the responsibility to ensure that the content tracks have correctly functioning Black Slide and Hidden Slide features and that there is a consistent, and appropriate, Navigation pad on each slide (returning one to the initial slide of a given content stack, and to the Main Menu or Interactive Map at the center of the star structure.

Calendar - Performance Records

The week of
November 19-25, Proposal Due (Due by November 25)
  • The Producerwill need to
    • Ensure that the group is able to Decideon a topic and to file a Proposal as an attachment for an email.
      • The Proposal should include the overall topic and the subtopics each team member will develop.
    • Note the roles each team member has agreed to accept in the Design of the project
    • Explain the Producer's strategy (timeline and communication methods) for following up on team role assignments as the project Develops.
  • Each week each person is asked to submit a report of their progress on the content area chosen.
    1. The first week's report can explain why you chose the subtopic you did – what interests you about it and how you would like to develop the idea.
    2. The second week the Storyboard takes the place of the personal report.
    3. The third week your personal report can explain what you have been able to contribute to the project draft the Producer has uploaded and what you still want to do.
    4. The fourth week the Self-Evaluation and Group Evaluation take the place of a personal report

November 26-December 2, Draft (Due by December 2)
  • Each Team member will need to
    • submit a Storyboard for each content stack slide that explains:
      1. The Title of the Slide
      2. What the slide is about, relative to developing the subtopic
      3. What media is anticipated for use on the slide. If graphics are used what will they show, if sound is used will it be a voice recording or a sound file of music, sound effects, etc., and if it is an animation, what will the animation show?
      4. What links will be on the page?
      5. Will there be any background or anything special about the text used (color, oversized, etc.)

December 3-9, Progress (Due by December 9)
  • The Producer will need to upload a draft version of the project.
  • The Navigator and Editor should have as much as possible done for linking and editing.
  • Each Team member will need to send your personal report to explain what you have been able to contribute to the project draft the Producer has uploaded and what you still want to do.

December 10-16, Completion (Due by December 16)
  • The Producer will need to upload the competed project
  • The Editor will need to have all editing completed.
  • The Navigator will need to have all linking in place (including Black Slides and Hidden Slides) and tested.
  • Each Team member will need to
    • have each content stack completed
    • Complete a self assessment (by email attachment) with Self-Evaluation.doc
    • Complete an assessment of group dynamics (by email attachment Evaluating the overall group dynamics with comments on how the writer and other group members contributed, or did not contribute, to the success of the project, using GroupEvaluation.doc
.

OPTIONAL
I understand these files may be large and difficult to manage and move. In addition, I am more interested in your work on your own projects, both the project itself and the cooperative group work. So, I am not asking you to do the Peer Evaluation of projects in Ivers, Page 150. However, if you wish to contribute your thoughts on the Ning on each others projects, please consider the questions in the Peer Evaluation master that the Ivers text provides. :-)