角色
Roles

学生以四或五人组成一组，每位学生认领一个或几个角色。 角色包括：(未以特定顺序排列)

Students will be organized into groups of four or five, with each student adopting one or more roles. Roles can include the following, in no particular order:

• 编辑
  Editor
• 撰稿
  Writer
• 程式设计师
  Programmer
• 制作人
  Producer
• 技术设计师
  Technical architect
• 多媒体设计师(图形、声音、影像)
  Multimedia designer (graphics, sound, video)
• 专案管理人
  Project manager
• 设计师
  Designer
• 资讯架构师
  Information architect
• 分镜脚本写作员
  Storyboarder
• 联系员
  Liaison
• 内容采集者
  Content gatherer

专题
Projects

本课程主要着重在小组专题的发展过程。专题不需一定是个网站，但必须是某种互动的电子通讯媒体形式。 所有的专题计划书必须经由指导老师核准认可。 小组可自选或从几个下列建议专题想法中选择专题。 成功的专题需融合有趣的点子、 丰富的内容、充分地运用技术和与观众强而有力的互动。

The primary focus of the class is the development of the group projects. Projects definitely do not have to be Web sites, but they must make use of some kind of interactive, electronic communication medium. All project proposals must be approved by the instructors. Groups may choose a project of their own design or from a list of several suggested project ideas (below). Successful projects blend an interesting idea, rich content, thoughtful use of technology, and strong audience interaction.

• 选择自己大胆尝试的线上书籍和游戏
  Choose-your-own-adventure online books, other games
• 线上固有的社群
  Online residential communities
• 为小学架设的网站，重点在帮助老师减轻工作量
  Web site for an elementary school, with a focus on how teachers could use it to lighten their workload
• 学生/ 教职员入口网站
  Student/faculty portal
• 针对MIT社群所做创新革命的线上服务
  New innovative online services targeting the MIT community
• 协助未来的新生跟既有学生沟通的网站
  Site for prospective and/or incoming frosh to communicate with current students
• 促进新生与高年级生之间辅导关系的网站
  Site to facilitate mentoring between frosh and upperclassmen
• 重新设计MIT的顶级首页
  Redesign of MIT's top-level home page

要求
Requirements

本文件提供修习21W.785课程学生要求的概要说明。学生应密切地配合本指导原则。

This document gives an overview of what is expected for each of the major student assignments in 21W.785. Students should follow this guideline closely when doing project work.

有关部份包括:

Relevant sections include:

• 专题计划书简报的要求
  Project Proposal Presentation Expectations
• 书面计划书的要求
  Written Proposal Expectations
• 期末口头简报的要求
  Final Oral Presentation Expectations
• 期末书面报告的要求
  Final Written Report Expectations

专题计划书简报的要求
Project Proposal Presentation Expectations

学生需做具视觉效果的PowerPoint简报或是网站投影片，简单直接地传达专题计划的内容。 限时15-20分钟。简报需包括：

Students are required to create either a PowerPoint presentation or Web slide show with visuals to communicate their project proposal simply and directly. Time limit is 15-20 minutes (max.) The presentation should include:

• 绪论: 专题的背景动机。这部分主要是建立此专题的必要性，并且陈述主要与次要的观众
  Introduction: background motivation for the project. This section establishes the need for the project and states the primary and secondary audience.
• 专题描述:藉由描述提议的外观与感觉、采取的设计策略、技术需求、工具以及如何取得的过程、平台/浏览器附属连结，让我们得以“看”到这个专题。
  Description of project: makes us "see" the project by describing proposed look and feel, design strategies you will employ, technical requirements, tools needed and how you will acquire them, platform/browser dependencies.
• 初步的模型
  A preliminary mockup.
• 专题时程和甘特图
  Project timeline and/or Gantt chart.
• 缴交项目: 本学期末前能实际完成的部份
  List of deliverables: what you can realistically finish by the end of the semester.
• 专题小组角色
  Project team roles.
• 提问与回答
  Q & A.

书面计划书的要求
Written Proposal Expectations

除了口头计划报告之外，学生需交一份10页长的书面计划书。虽然某人可能担任编辑与内容取得者，但小组中的所有学生需要制作计划书中有关他们主要负责的各段落。

In addition to the oral proposal, students are asked to submit a ten-page written proposal. Although a single student may be serving as editor and content gatherer, all students in the groups are required to author sections of the proposal related to their chief area of responsibility.

前言
Front Matter

• 题目页：专案标题、小组成员姓名、小组电子邮件地址、报告种类(计划书)和日期
  Title page: name of project, names of team members, group email address, type of report (proposal), and current date.
• 摘要: 列出一段，大约150字。陈述问题、方法、预期结果；在摘要中不需列出表格或参考书目资料；勿用第一人称代名词来写作
  Abstract: one paragraph, ca. 150 words; state the problem, methods, expected results; no figures or references in abstract; do not use first person pronouns.
• 目录
  Table of contents.
• 图表清单，如果你们有四个或以上的图表时，需以编号与标签分类
  List of figures, if you have four or more. Figures should be numbered and labeled.

本文
Body

• 绪论: 本专题的背景动机。本段在确立此专题的必须性，并说明首要与次要读者。
  Introduction: background motivation for the project. This section establishes the need for the project; state primary and secondary audience.
• 目标: 为专题设定清楚的目标、服务/位址的目的以及其范围
  Statement of objectives: the clear objectives set for your project, purpose of the service/site; its scope.
• 专题描述: 经由描述提议的外观与感觉、采取的设计策略、必须的技术需求、工具以及如何取得的过程、平台/浏览器依存状态，让我们得以“看”到这个专题。
  Description of project: makes us "see" the project by describing proposed look and feel, design strategies you will employ, technical requirements, tools needed and how you will acquire them, platform/browser dependencies.
• 工作项目与时程: 利用甘特图将专题的时程分成明确的工作项目(纵轴)，纵跨几周的时间(横轴)。在横轴上确立预期达成的重要里程碑
  Tasks and milestones: show a Gantt chart which divides the life of the project into definable tasks (vertical axis) over time in weeks (horizontal axis). Punctuate the horizontal axis with important milestones you are expected to meet.
• 每位小组成员所要扮演的角色
  Roles each team member will perform.
• 技术执行计划的大纲(如适用的话)
  Overview of the technical implementation plans (if applicable)

结尾
End Matter

• 参考书目
  References
• 附属连结
  Dependencies

期末口头简报的要求(与期末书面报告共占40%)
Final Oral Presentation Expectations (40% with final written report)

学生也需以期终口头简报方式来评估其专题。期末口头简报大部份以进度报告的形式，来报告已达成的细节、变更、如何想达到的原始目标、可行性测试的结果等。此简报的另外部份是专题示范，学生将透过现场线上示范，对全班展示他们的期末专题。

Students are also required to assess their project in a final oral presentation. The final oral presentation will be largely in the form of a progress report that details what you have done, what you have changed, how you attempted/reached your original goals, what the results of usability testing were etc. Another big part of this presentation is the project demonstration where students will show their final project to the class through a live online demo.

时间限制: 每组成员各有5分钟的演说时间，10-15分钟的专题示范，5分钟的问答时间。
Time limits: 5 minutes speaking time per group member, 10-15 minutes for project demonstration, 5 minutes for Q&A.

绪论
Introduction

• 报告专题名称与简报者的名单
  State title of project and names of presenters.
• 重述动机、范围与目标 (如果从一开始，你们专题的原始目的或范围有所变更，说明原因)。 简短地重申动机，重点是在目的。
  Reiterate motivation, scope, and statement of objectives (tell us if your original objectives or scope of project has changed since the proposal, and why). Brief restatement of motivation; objectives are more important.

本文
Body

• 目前的活动状态。两个关键问题: 到目前为止已完成什么? 还剩哪些尚待完成?
  Current state of activities. Two key questions: What have you accomplished so far? What remains to be done?
• 针对专题发展或可能的观者，说明在技术需求方面的任何变动
  State any changes in technical requirements for project development or for intended audience to view it.
• 说明遭遇的关键问题，并且解释解决的过程。说明如果问题无法解决时，将如何影响专题和设计?
  Identify key problems encountered, and explain how they were solved. If problems were not resolved what effects did they have on the project and its design?
• 管理与小组间的变动。如何组织你们的专题?
  Management/group dynamics. How did you organize your project?
• 在提议的外观和感觉上的变化。
  Changes in your proposed look and feel.
• 从可行性测试所导致的结果变化。
  Changes due to results from usability testing.
• 专题展示: 示范设计的目前状态，并解释其与原始计划间的改变。
  PROJECT DEMO: show us the current state of the design. Explain changes from initial proposal.

结论
Conclusion

• 根据已修改过的时程图展示已达成的进度。
  Show the progress achieved by reference to a revised time chart.
• 说明隐约可见的问题和解决危机的方法。
  Indicate what looming problems you expect and how you hope to resolve these crises.
• 解释专题的延伸以及未来的可能改善方案
  Mention extensions to your project and possible future improvements.

问答
Q&A

• 小组成员请观众提问题并回答问题。
  Group members invite and respond to questions from the audience.

期末书面报告的期望(40%跟期末口头简报)
Final Written Report Expectations (40% with final oral presentation)

学生需写一份以期末简报为基础的10-15页期末报告，并且加入专题外的额外细节。

Students are required to write a 10-15 page final report that should build upon their final oral presentation, and fill in extra details about their projects.

前言
Front Matter

• 首页: 专题名称、一致资源定址器（URL）、报告类型、作者、地点与日期
  Title page: name of project, URL, type of report, contributors, location, and date.
• 摘要: 约50字，问题/需求、方法、结果/结论/建议(简要的报告，不需图表或参考文献)
  Abstract: ca.150 words, problem/need, methods, results/conclusions/recommendations (the whole report in miniature; no figures or references).
• 目录(列出报告中所有的标题)
  Table of contents (all headings in the report appear here).
• 图表清单与相关标签(如果超过四个以上的话)
  List of figures & their corresponding labels (if more than four).

本文
Body

• 绪论: 专题的背景/动机与预定的观众。引导出整体设计的目标与大致说明。
  Introduction: background/motivation and intended audience(s) for your project. Leads to a statement of objective and general description of your overall design.
• 技术面方法: 设计的选择、使用的工具、依附的平台(如果有使用的话)；执行该设计的需要。协调不同的浏览器设备。效能问题。
  Technical approach: design choices; tools used; platform dependencies (if any); what you needed to implement the design. Accommodations for different browsers. Performance issues.
• 设计说明: (口头简报时，以附有图表的书面报告来取代示范)此专题的整体象征、外观与感觉、运作方法、使用者情境、导航、连结到位址与其理由。
  Description of design: (with figures in written report instead of demo as in oral presentation); overall metaphor for the design; look and feel; how it works; user scenario(s); navigation; links to sites and reasons for those links.
• 从动机的观点来衡量设计：问题、尚未完成处；失败点与对专题的影响
  Evaluation of design in light of motivation: problems; what you had to leave undone; what didn't work and effects on project; studies of users; project management – were your time estimates realistic?
• 对未来工作的结论/建议: 如果专题继续进行，有什么仍须完成；维护专题的最佳之道
  Conclusions/Recommendation for future work: what still needs to be done if the project were to be continued; how best to maintain the project.

结尾
End Matter

• 致谢词(如果有的话)
  Acknowledgements (if any).
• 参考文献: 书面影本与网站参考资料
  References: hardcopy and Web references.
• 附录(适当地记录写程式的过程—不需将程式码或Java码等印出来—说明模组/等级的概况即可)
  Appendices (documentation of programming when appropriate – no need to print out code or Javadocs etc. – an overview of modules/classes designed will be sufficient).