Information Systems and Service Design (Fall 2011) UC Berkeley, School of Information

The final report should act as a summary of your project and process. It should cover the various stages of your project, but  it is not simply a restatement of the artifacts/assignments you've submitted to date: it should synthesize the artifacts using your work in traceability and recast your work through the lens of the seven contexts of service system design. Highlight the more interesting parts of your project: unexpected findings, challenges, mid-process changes based on new information, etc. 

Explicitly address 2 or 3 of your main trace paths. You can diagram the trace path and/or simply discuss the evolution of the trace concepts through your project process and artifacts.

Note: 

• Do not just copy and paste text from your other assignments. Make sure the content flows and is relevant. 
• Also, ensure that any content submitted from previous assignments reflects or addresses the feedback given by your TA or Bob.
  
• Please proofread these reports for high-level organization, grammar, spelling, punctuation, etc. These reports should be polished and easy to read. 

Revisit the final reports assigned throughout the semester; they are good examples in length, content, and presentation.