The Information Architecture Analysis 2 (IAA2) project results in a critical 8 minute, video-driven chronology of the G2P project: development, design, playtesting, refinement. The project emphasizes how core information architecture concepts and strategies impacted the process. The IAA2 is challenging because it demands careful presentation of the project's history from a reflective research perspective.
This project requires only a final submission. All files are submitted to an InfoArchAnalysis2 folder in your shared course space on Dropbox.com.
The submission includes the following documents:
Document type: memo, screencast video
Document length: 150 words (memo), 8 to 10 minutes (video)
Project value: 200 points
Evaluation rubric: _RPW350_Eval_InfoArchAnalysis2.pdf
The IAA2 requires you to distill the most important design and learning moments from the Game 2 Prototype project into a detailed, coherent video report. Your report should offer a chronology of project stages (e.g., development, design, playtesting, refinement), and must connect throughout to the principles of information architecture (e.g., design strategy that anticipated user needs & expectations; easy-to-understand information patterns; clean, professional visual design; user-aware interaction patterns). Emphasize your on-going decision-making processes, and how you focused on becoming and remaining user-aware throughout the project.
Because your game design experience now encompasses both physical and digital environments, consider how the the migration of design process into TableTop Simulator has impacted the way you think about the design of your game. Because you have already presented an examination of the Game 1 Prototype in your previous Analysis, feel free to remind viewers now of the highlights and key takeaways from that first design phase. That will offer you time to focus more on the evolution of design and strategy into the digital context.
Your screening document once again should stand in as an effective representation of your report even without your presence as a presenter. That means viewers (or readers) ought to be able to discern the core details and explanations from the content available on each screen. However, the document should be designed to serve primarily as the on-screen object during your screencast recording.
To meet these ends, your screening document must incorporate the following content and design elements.
Record your screencast using the screening document as your designated recording window. Use the content from that document as the basis for your presentation, but avoid reading it to viewers. Rather, bring it to life through your discussion. Although the screening document should serve as the anchor for the analysis, you should also consider implementing video from playtesting.
Test the resulting video file prior to submitting your project. Make sure that the audio is strong and clear, and that the video is free of glitches or background sounds.
Prepare your report for streaming by posting the video file to Screencast.com (or another streaming service). One advantage of Screencast.com over some other services is that you control whether or not your files are publicly accessible. Copy the SHARE link and add it to your project Memo (see below) prior to submission of the project.
A memo of transmittal introduces the accompanying document to its audience(s). Your memo should be addressed from you to me, and should introduce the accompanying project. Your memo should incorporate the following content elements.
Read and attend carefully to these submission guidelines. Failure to do so may result in points lost on the final evaluation of your project.
Create a project folder inside your shared class folder on Dropbox.com. Remember, I can only view files that you place inside the shared folder. Until you place files in that space, you have not in practice submitted them.
Name the folder InfoArchAnalysis2.
When you assemble your submission for the IAA2 project, there will be 2 files in the folder. Again, model your filenames on the examples listed here.
Note. Do not share the individual files with me. By placing them in your project folder, you have already shared them by default.
Take the time to organize your work as directed here, and to name each file properly. This helps me keep track of your work, and makes clear which files are meant to represent the on-going and final stages of project development.
There are 200 possible points for the project. You will earn points according to the standard described on the policies page (40% content development, 40% design execution and delivery, and 20% professionalism & attention to detail; see Policies). The specific areas of emphasis for this project are drawn from the description and discussion of the project, and are detailed in the evaluation rubric (_RPW350_Eval_InfoArchAnalysis2.pdf).
Remember that I will only post the point values for projects on the Grades page in SVSU Canvas. I will post the details relevant to that evaluation in your class folder in a project-specific file.
If you are here because of random chance, or because this content came up in a search, then poke about, and read if you see something useful or interesting. If you are a teacher in any context and would like to use any of this content in your courses, feel free to do so. However, if you borrow this material, please do two things: