ISSD Fall 2009 School of Information, UC Berkeley

No lecture from me and no reading assigned.  Each project team will take 8-10 minutes to present a status report. This should begin with a crisp description of your project's scope, primary stakeholders, and point of view. Next tell us what your M and S priority requirements are, and give some examples of design ideas for satisfying them. If use cases, blueprints or other process models would make it easier to communicate your work, present them. If you have less precise ideas, just discuss design ideas organized by "seven contexts." In either case, present as much "traceability" to previous work as you can specify.  Finally, tell us what else you expect to accomplish by the end of the semester (what specific "design artifacts" are you aiming to produce).

The primary goal of this status report is to get your team to evaluate where it is and make decisions about what can and what can not be accomplished in the remaining three (or at most four) weeks until your final presentations. Your team will be able to decide if it can make a final project presentation on Wed 12/9 or whether it wants to do one on Tuesday 12/15. I'd like to make a firm schedule for this as soon as all the presentations are finished.

A secondary goal is to inform your classmates about your work; they are likely to have comments and suggest design ideas for your projects.