本論文提出文件製作活動，來延伸極致編程在嵌入式系統上的應用以期解決: 1) 原始極致編程缺乏先期文件來降低開發風險、 2) 文件在專門且廣泛的知識領域上，設計考量不易周延、以及 3)傳統文件製作過程困難且緩慢。
為解決上述問題，本論文提出一個名為Documenting Game 的文件製作方式，Documenting Game是一個模組化的方法，包含1)文件分析、 2)邀請人員、 3) 收集意見、 4)分析意見、 5)細部設計、 6)決策討論及 7)知識共享等文件製作步驟。
本論文有以下預期優點: 1) 快速精確製作文件，提供系統所需之先期設計文件， 2) 增進開發人員之間的溝通，文件製作自信提高，以及3) 將文件導入文件共享平台，知識內容不斷傳承分享。

This thesis presents the “documenting game” to extend eXtreme Programming for developing Embedded Systems. The approach attempts to: 1) use early documents to reduce development risks, which is lacking in eXtreme Programming, 2) address the highly specialized and diversified knowledge required by Embedded Systems development, and 3) remedy the difficult and slow process of producing traditional documents.
The documenting game is a structured method to produce documents with the above considerations. It consists of the following steps: 1) document analysis, 2) inviting people, 3) collecting comments, 4) analyzing comments, 5) detailed design, 6) policy discussion, and 7) document sharing.
The expected benefits of this approach are: 1) to quickly and precisely produce the required early design documents, 2) to promote developers’ communication that results in higher confidence in documents, and 3) to facilitate knowledge distribution through the “document sharing platform”.

[1] James Grenning: Extreme Programming and Embedded Software Development
[2] Philip Koopman: Embedded System Design Issues, Engineering Design Research Center Carnegie Mellon University Pittsburgh.
[3] Bill Greene: Agile Methods Applied to Embedded Firmware Development, Intel Corporation, 2002.
[4] Capability and Maturity Model (CMMISM) V1.1, March 2002.
[5] K. Beck, Extreme Programming Explained: Embrace Change, Addison-Wesley,2000.
[6] William C. Wake, Extreme Programming Explored, Addison-Wesley,
pp. 1-8, July 2001.
[7] Kent Beck, Extreme Programming Explained, Addison-Wesley, Chapter 10,
October 1999.
[8] “Essential XP Documentation”, Ron Jeffries, November 2001.
[9] Etienne Wenger: Communities of Practices, Learning As A Society System”, Published in the "Systems Thinker", June 1998.
[10] Blood, Rebecca: “Weblogs: A History and Perspective”, Rebecca''s Pocket, September 7, 2000: see http://www.rebeccablood.net/essays/weblog_history.html.
[11] Hourihan, Meg. “What We''re Doing When We Blog”, O''Reilly Network, June 13, 2002. www.oreillynet.com/pub/a/javascript/2002/06/13/megnut.html.
[12] TWikiTM - an Enterprise Collaboration Platform, http://twiki.org/
[13] Integrated Collaboration and Change Management for Software Development, http://www.intland.com/
[14] Source: "Liberating the Innovation Value of Communities of Practice" in the forthcoming textbook on "Knowledge Economics: Emerging Principles, Practices and Policies."http://www.entovation.com/coming-soon.htm
[15] Evolving communities of practice: IBM Global Services Experience, by P. Gongla, C.R. Rizzuto, in IBM Systems Journal 2001. http://www.findarticles.com/m0ISJ/4_40/issue.jhtml
[16] Building and Sustaining Communities of Practice - a study by American Productivity and Quality Center, http://www.apqc.org/