角色
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).