| 研究生: |
洪盟翔 Meng-Shiang Hung |
|---|---|
| 論文名稱: |
敏捷方法中使用高階與低階的溝通 Using High and Low Level Communication in Agile Method |
| 指導教授: |
陳振炎
Jen-Yen Chen |
| 口試委員: | |
| 學位類別: |
碩士 Master |
| 系所名稱: |
資訊電機學院 - 資訊工程學系 Department of Computer Science & Information Engineering |
| 畢業學年度: | 98 |
| 語文別: | 中文 |
| 論文頁數: | 23 |
| 中文關鍵詞: | 低階溝通 、高階溝通 、敏捷方法 |
| 外文關鍵詞: | Low Level Communication, Agile Method, High Level Communication |
| 相關次數: | 點閱:13 下載:0 |
| 分享至: |
| 查詢本校圖書館目錄 查詢臺灣博碩士論文知識加值系統 勘誤回報 |
本論文嘗試分析團隊溝通的內容,以 abstraction level 來分類,整理出週期規律,且提出一些準則。團隊溝通一開始會從 high level的需求,往 low level 的架構設計討論,然後再往更 low level 的實作。之後會在這些層級來回移動,循序漸進。本文提出開發環境監測系統的例子,在兩組人員的討論過程,可以明顯的看出這些規律。最後根據這些規律提出一些準則: 1) 循序漸進的溝通, 2) 文件的重要性, 3) 討論人數與abstraction level 的關係。
We tried to analyze communication of an agile team, classified contents of communication according to abstraction level, cleaned up a cycle rule, and proposed a number of practices. At the beginning, the team communicated from the highest level requirements, then go down to a lower level architecture design, eventually go to the lowest level implementation. After that, the communication will move back and forth in abstraction levels. In our example of developing the surveillance system, the cycle rule is obviously observed in the interaction of two pairs. At the end, we proposed three practices according to our observation: 1) communicate step by step, 2) the importance of documents, 3) the relationship between the number of people and the abstraction level.
[1] Martin Fowler. The New Methodology. [Online]. Available:
http://martinfowler.com/articles/newMethodology.html
[2] Manifesto for Agile Software Development. [Online]. Available:
http://www.agilemanifesto.org/
[3] Don Wells. Extreme Programming: A gentle introduction. [Online]. Available:
http://www.extremeprogramming.org/
[4] Schwaber, Ken, “Agile Project Management with Scrum”, 2005
[5] Don Wells. The Rules of Extreme Programming. [Online]. Available:
http://www.extremeprogramming.org/rules.html
[6] Don Wells. Pair Programming. [Online]. Available:
http://www.extremeprogramming.org/rules/pair.html
[7] Kai Stapel, Eric Knauss, Kurt Schneider, and Matthias Becker.
“Towards Understanding Communication Structure in Pair Programming”, 2010.
[8] Sara Shahzad. “Learning From Experience: The Analysis of an Extreme
Programming Process”, International Conference on Information Technology,
2009.
[9] Zahid Hussain, Martin Lechner, Harald Milchrahm, Sara Shahzad,Wolfgang
Slany, Martin Umgeher, Thomas Vlk. “Optimizing Extreme Programming”,
Proceedings of the International Conference on Computer and Communication
Engineering, 2008.
[10] Martin, Robert C. “Design Principles and Design Patterns”, Retrieved 2000.
[11] Bruno Pages. BOUML. [Online]. Available:
http://bouml.free.fr/