會議導向敏捷軟體開發及系統設計：以大學畢業專題為例

以作者查詢圖書館館藏

、以作者查詢臺灣博碩士

、以作者查詢全國書目

、勘誤回報

、線上人數：10

、訪客IP：3.17.150.89

姓名

鄧高荃(Kao-chiuan Teng) 查詢紙本館藏

畢業系所

資訊管理學系

論文名稱

會議導向敏捷軟體開發及系統設計：以大學畢業專題為例
(Meeting-oriented agile software development and system design: Undergraduate students’ graduation project as an example)

相關論文

★ 專案管理的溝通關鍵路徑探討─以某企業軟體專案為例	★ 運用並探討會議流如何促進敏捷發展過程中團隊溝通與文件化：以T銀行系統開發為例
★ 專案化資訊服務中人力連續派遣決策模式之研究─以高鐵行控資訊設備維護為例	★ 以組織正義觀點介入案件指派決策之研究
★ 應用協調理論建立系統軟體測試中問題改善之協作流程	★ 應用案例式推理於問題管理系統之研究 -以筆記型電腦產品為例
★ 運用限制理論於多專案開發模式的人力資源配置之探討	★ 應用會議流方法於軟體專案開發之個案研究：以翰昇科技公司為例
★ 多重專案、多期再規劃的軟體開發接案決策模式：以南亞科技資訊部門為例	★ 一種基於物件、屬性導向之變更影響分析方法於差異化產品設計
★ 會議流方法對大學畢業專題的團隊合作品質影響之實驗研究	★ 實施敏捷式發展法於大學部畢業專題之行動研究 – 以中央大學資管系為例
★ 建立一個用來評核自然語言需求品質的線上資訊系統	★ 結合本體論與模糊分析網路程序法於軟體測試之風險與風險關聯辨識
★ 在軟體反向工程中針對UML結構模型圖之線上品質評核系統	★ 以模糊專家系統實作軟體專案調適準則

檔案

[Endnote RIS 格式]

[Bibtex 格式]

[相關文章]

[文章引用]

[完整記錄]

[館藏目錄]

至系統瀏覽論文 ( 永不開放)

摘要(中)

軟體專案的最大挑戰之一在於要應付變動中的需求，另一方面要在緊縮的時程內協同完成專案。因此，軟體團隊除了在技術上必須日益精進，更需要運用有效的開發方式，許多所謂的「輕量級」的軟體開發方法在此環境背景之下發展出來，而敏捷軟體開發方法為其中之一。敏捷軟體開發方法主要是週期性地逐項開發，並強調各層次的溝通及團隊協同，以求快速又能正確地發展所期待的軟體雛型。由於目前敏捷軟體開發方法在溝通及團隊協同的運作上並無一具體且可重覆實施的執行模式。
本研究即針對軟體開發中重要(substantial)之溝通及團隊協同工作，並運用會議形式，來嘗試建立一具體的溝通及團隊協同發展方式，即「會議導向敏捷軟體開發」方法。本研究並設計一群體支援的網頁操作系統，使專案團隊透過資訊系統之輔助運作本研究設計之模式，將團隊協同活動透過會議流方法定義出來，專案管理人員可依據系統產生之圖形化介面，了解專案團隊運作狀況並掌握專案風險。本研究最後將透過一適合敏捷發展典型的軟體開發，即大學畢業專題開發的實施案例，來說明模式及系統運作之可行性。

摘要(英)

One of the biggest challenges in software project is cope with changing needs, and in a tight schedule complete collaboratively the project. Software team should use more efficient processes of software development besides improving their technique. Many of lightweight software development methods developed in this context, agile software development method is one of them. Agile software development methodology is cyclic and incremental development, and stressed that all levels of communication and team collaboration in order to quickly and correctly develop the expected prototype of software. However, in agile software development method, there is no one repeatable implementation of specific modalities of communication and team collaboration.
This study attempts to establish a specific model for the substantial communication and team collaboration in development of software project by using the form of meetings, that is, “meeting-oriented agile software development” approach. And this study also designs a web-based information system to support the project team to operate the meeting-oriented agile software development model, to define the team collaborative activities through the meetings flow approach. Project managers could realize the operation situation and the risk of project through the graphics which generated by the system. In the end of this study, a typical agile software development case, an implementation of undergraduate students’ graduation project, is provided to explain the feasibility of the model and system.

關鍵字(中)

★ 群體支援系統
★ 團隊協同合作
★ 會議流方法
★ 敏捷軟體開發方法

關鍵字(英)

★ meetings flow
★ group support system
★ agile development method
★ team collaboration

論文目次

中文摘要...............................................i
英文摘要...............................................ii
致謝辭.................................................iii
目錄...................................................iv
圖目錄.................................................vii
表目錄.................................................ix
第一章、緒論...........................................1
1.1　研究背景..........................................1
1.2　研究動機..........................................2
1.3　研究目的與預期效益................................3
1.4　範圍與假設........................................3
1.5　研究步驟..........................................4
第二章、文獻探討.......................................6
2.1　專案管理與團隊協同................................6
2.1.1　專案的定義......................................7
2.1.2　何謂專案管理....................................8
2.1.3　工作分解結構....................................8
2.1.4　團隊協同運作....................................9
2.1.5　協同合作........................................10
2.2　敏捷軟體開發模式..................................11
2.2.1　何謂敏捷軟體開發................................12
2.2.2　敏捷軟體開發宣言................................13
2.2.3　敏捷開發方法論..................................14
2.3　會議流模式........................................15
2.3.1　會議的定義......................................15
2.3.2　專案開發的四大作業..............................16
2.4　群體支援系統......................................18
2.4.1　群體支援系統的定義..............................18
2.4.2　群體支援系統科技的三大特點......................19
2.4.3　群體支援系統的分類..............................19
2.4.4　群體支援系統的應用..............................20
2.5　UML(Unified Modeling Language)....................21
2.5.1　UML的演進.......................................22
2.5.2　UML的使用觀點與圖型.............................23
2.6　小結..............................................26
第三章、研究方法.......................................27
3.1　研究設計..........................................27
3.1.1　會議導向敏捷軟體發展模式架構....................27
3.1.2　會議導向敏捷軟體發展模式流程建構................28
3.1.3　會議導向敏捷軟體發展模式之建立..................32
3.2　會議導向敏捷軟體開發模式之實例運作................34
3.2.1　案例背景介紹....................................34
3.2.2　建立工作週期與會議類別..........................34
3.2.3　規劃會議導向團隊流程............................35
3.3　系統設計..........................................36
3.3.1　系統需求分析....................................36
3.3.2　系統邏輯架構....................................37
3.3.3　系統流程設計....................................39
第四章、系統案例展示...................................42
4.1　系統環境與架構....................................42
4.2　系統案例展示......................................43
4.2.1　建立工作週期與會議類別..........................43
4.2.2　規劃會議導向團隊流程............................46
4.2.3　會議流運作......................................49
第五章、討論與建議.....................................54
5.1　研究成果..........................................54
5.2　討論..............................................55
5.2.1　會議流與工作流..................................55
5.2.2　會議導向敏捷軟體開發模式可能的問題..............56
5.3　研究限制..........................................57
第六章、　結論與未來展望...............................59
6.1　研究貢獻..........................................59
6.2　未來展望..........................................60
參考文獻...............................................61

參考文獻

中文部分
中華民國內政部，民國43年，中華民國內政部會議規範。
林東清，2002，「資訊管理：e 化企業的核心競爭能力」，台北：智勝。
林漢聲，民國95年，「運用Petri Net來塑模軟體專案開發之會議流模式」，私立長庚大學，碩士論文。
梁定澎，2006，「決策支援系統與企業智慧」，台北：智勝。
連榮祥，民國95年，「以會議為主題之物件導向專案開發管理之研究與設計」，私立長庚大學，碩士論文。
陳仲儼，民國94年，「會議運作流程模式為基礎之專案管理：一項新方法」，中華民國資訊軟體協會，台北。
陳炳昇，民國95年，「應用群組技術來調適專案管理會議流程運作之研究」，私立長庚大學，碩士論文。
趙耿暉，民國96年，「運用會議流模式來具體化軟體品質規範中有關需求生命週期管理之研究：以CMMI模式為例」，私立長庚大學，碩士論文。
蔡東廷，民國97年，「塑模專案導向團隊流程：動態會議流規劃系統的設計與實作」，私立長庚大學，碩士論文。
英文部分
Anumba, C.J., Ugwu, O.O., Newnham, L., Thorpe, A., 2002. Collaborative design of structures using intelligent agents, Automation in Construction, Vol. 11, No. 1, pp.89-103.
Aoyama, M., 1997. Agile Software Process Model, Proceedings of the 21st International Computer Software and Applications Conference, pp.454-459.
Beck, K., 2000. eXtreme Programming explained, 2nd ed., Addison-Wesley.
Boehm, B., 2002. Get Ready for Agile Methods, with Care, IEEE Computer, Vol. 35, No. 1, pp.64-69.
Bolstad, C.A., & Endsley, M.R., 2003. Tools for supporting team collaboration, Human Factors and Ergonomics 47th Annual Meeting, Denver, Colorado.
Booch G., Jacobson, I. and Rumbaugh, J., 1998. The Unified Modeling Language User Guide, Addison Wesley.
Bostrom, R.P., Anson R., Clawson V.K., 1993. Group facilitation and group support systems, Group Support Systems: New perspectives, Jessup L, Valacich J ed., Macmillan: New York, pp.146-168.
Bruegge, B., Dutoit, A.H., 2003. Object-Oriented Software Engineering Using UML, Patterns, and Java, 2nd ed., NJ: Pearson Prentice Hall.
Chen, C.Y., Chao, K.H., Chen, P.C., 2007. A preliminary study of meeting flow management for software project development: the prototype (MfPMIS), IEEE IEEM.
Chen, C.Y., 2009. Conducting team-based senior project development: the Meeting-Flow approach, unpublished paper.
Chen, C.Y., 2009. Meetings, meeting flows, and software project’s team processes, unpublished paper.
Chen, C.Y., 2009. A meetings flow approach for conducting student final-year projects, Journal of Computing Sciences in Colleges, Vol. 24, No. 6, pp.28-34.
Cleland, D.I., King W.R., 1983. Systems Analysis and Project Management, New York: McGraw-Hill.
Cockburn, A., 2006. Agile Software Development: the Cooperative Game, 2nd ed., Addison-Wesley, Boston.
Cockburn, A., 2004. Crystal Clear: A Human-Powered Methodology for Small Teams. MA : Addison-Wesley.
Dennis, A.R., George, J.F., Jessup, L.M., Nunamaker, J.F. and Vogel, D.R., 1988. Information technology to support electronic meetings, MIS Quarterly, Vol. 12, No. 4, pp.591-619.
Dennis, A.R., Garfield, M.J., 2003. The adoption and use of GSS in project team: Toward more participative process and outcomes, MIS Quarterly, Vol. 27, No. 2, pp.289-323.
Dennis, A.R., Gallupe, R.B., 1993. A History of Group Support Systems Empirical Research: Lessons Learned and Future Directions, Group Support Systems: New Perspectives, NY: Macmillan Publishing Company, pp. 59-77.
Dennis A.R., Heminger, A.R., Nunamaker, J.R., Vogel, D.R., 1990. Bringing automated support to large groups: the Burr-Brown experience, Information and Management, Vol. 18, No. 3, pp.111-121.
DeSanctis, G., Gallupe, R.B., 1987. A foundation for the study of group decision support systems. Management Science, Vol. 23, No. 5, pp.589–609.
Dix, A., Finley, J., Abowd, G., Beale, R., 1993. Human-computer interaction, New York: Prentice Hall.
DoD (USA), 1998. Department of Defense Handbook Work Breakdown Structure.
DSDM consortium, Stapleton, J., 2003. DSDM: Business Focused Development, 2nd ed., MA: Addison-Wesley.
Dyer, J., 1984. Team research and team training: a state-of-the-art review, Human Factors Review, CA: Human Factors Society, pp.285-323.
Ellis, L., Gibbs, S.J., & Rein, G.L., 1991. Groupware: some issues and experiences, Communications of the ACM, Vol. 34, No. 1, pp.38-58.
Faraj, S., Sproull, L., 2000. Coordinating expertise in software development teams, Management Science, Vol. 46, No. 12, pp.1554-1568.
George, J.M., Jones, G.R., 2008. Understanding and Managing Organizational Behavior, 5th ed., Prentice Hall.
Ginsberg, M., Quinn, L., 1994. Process tailoring and the software capability maturity model, Technical Report, CMU/SEI-94-TR-024.
Hackman, J., Morris, C., 1978. Group tasks, group interaction process, and group performance effectiveness: A review and proposed integration. In L. Berkowitz ed., Group Process, NY: Academic Press, pp.1-15.
Haugan, T.G., 2002. Effective Work Breakdown Structures, Management Concepts, Vienna, Virginia.
Hazzan, O., Dubinsky, Y., 2008. Agile Software Engineering, London: Springer-Verlag.
Helbrough, B., 1995. Computer assisted collaboration – the fourth dimension of project management? International Journal of Project Management, Vol. 31, No. 5, pp.329-333.
Hollingshead, A.B., McGrath, J.E., 1995. Computer-assisted Groups: A Critical Review of the Empirical Research, Team Effectiveness and Decision Making in Organizations, Jossey-Bass, San Francisco, pp.46-78.
Huber, G. P., 1984. Issues in the design of group decision support systems, MIS Quarterly, Vol. 8, No. 3, pp.195-204.
Humphrey, W. S., 2000. The team software process, Technical Report, CMU/SEI-2000-TR-023.
Humphrey, W. S., 2002. Three process perspectives: organizations, teams, and people, Annals of Software Engineering, Vol. 14, No.1-4, pp.39-72.
IBM, 1997. Project Management Fundamentals Handbook.
ISO, 2005. ISO 9000:2000-Quality Management Systems.
Jones, E., Watson, B., Gardner, J., Gallois, C., 2004. Organizational communication: challenges for the new century, Journal of Communication, Vol. 54, No.4, pp.722-750.
Jugdev, K., Muller, R., 2005, A retrospective look at our evolving understanding of project success, Project Management Journal, Vol. 36, No.4, pp.19-31.
Kerzner, H., 2006. Project Management: A Systems Approach to Planning, Scheduling and Controlling, 9th ed., NJ: John Wiley & Sons.
Kloppenborg, T.J., Opfer, W.A., 2002. The current state of project management research: trends, interpretations, and predictions, Project Management Journal, Vol. 33, No. 2, pp.5-18.
Kruchten, P.B., 1995. The 4+1 view model of architecture, IEEE Software, Vol. 12, No. 6, pp.42-50.
Lammers, J.C., Barbour, J.B., 2006. An institutional theory of organizational communication, Communication Theory, Vol. 16, No. 3, pp.356-377.
Liou, Y.I., Nunamaker, J.F., 1993. An investigation into knowledge acquisition using a GDSS, Information & Management, Vol.24, No. 3, pp.122-132.
Liou Y.I., Weber, E.S., Nunamaker, J.F., 1990. A methodology for knowledge acquisition in a group decision support systems environment, Knowledge Acquisition, Vol. 2, No. 2, pp.129-144.
Maclachlan, L., 1996. Making Project Management for You, London: Library Association.
McBride, T., 2008. The mechanisms of project management of software development, The Journal of Systems and Software, Vol. 81, No. 12, pp.2386-2395.
Nunamaker, J.F., Weber, E.S., Chen, M., 1989. Organizational crisis management systems: planning for intelligent action, Journal of Management Information Systems, Vol. 5, No. 4, pp. 7-32.
OMG, 2009. UML home page: http://www.uml.org/
Palmer, S.R., Felsing, J.M., 2002. A practical Guide to Feature-Driven Development, NJ: Prentice-Hall, Englewood Cliffs.
PMI, 2004. A Guide to the Project Management Body of Knowledge, 3rd ed., (PMBOK Guides.)
Ramsin, R., Paige, R. F., 2008. Process-centered review of object oriented software development methodologies, ACM Computing Surveys, Vol. 40, No. 1, pp.1-89.
Ritchie, L., Price, V., 1991. Of matters micro and macro: Special issues for communication research, Communication Research, Vol. 18, No. 2, pp.133-139
Robillard, P.N., 1995. Experience in teaching team software design, Proceedings of the 6th World Conference on Computers in Education, Birmingham, UK, pp.441-453.
Robillard, P.N., Robillard, M.P., 2000. Types of collaborative work in software engineering, The Journal of Systems and Software, Vol. 53, No. 3, pp.219-224.
Roschelle, J., Teasley, S., 1995. The construction of shared knowledge in collaborative problem solving, In C. O'Malley ed., Computer-supported collaborative learning, Berlin, Germany: Springer-Verlag, pp.69-197.
Salas, E., Rozell, D., Mullen, B., Driskell, J.E., 1999. The effect of team building on performance: an integration, Small Group Research, Vol.30, No. 3, pp.309-329.
Schwaber, K., Beedle, M., 2002. Agile Software Development with Scrum, Prentice Hall.
SEI, 2006. CMMI for Development, Version 1.2, CMU/SEI-2006-TR-008.
Sharp, H., Robinson, H., 2007. Collaboration and co-ordination in mature extreme programming teams, International Journal of Human-Computer Studies, Vol. 66, No. 7, pp.506-518.
Sieli, E.M., 1991. Managing a project as a process, AT&T Technical Journal, Vol. 70, No. 2, pp.33-39.
Turner, R., 2003. Using CMMI to balance agile and plan-driven methods, CMMI technology conference.
Vaaland, T. I., 2004. Improving project collaboration: start with the conflicts, International Journal of Project Management, Vol. 22, No. 6, pp.447-454.
Wang, Q., Li, M., 2006. Software Process Management: Practices in China. Unifying the Software Process Spectrum, Vol. 3840, pp.317-331.
Whitten, J.L., Bentley, L.D., 1998. System Analysis and Design Methods, 4th ed., NY: McGraw-Hill.
Workflow Management Coalition, 1999. Workflow Management Coalition Terminology and Glossary, WFMC-TC-1011, Issue 3.
Wysocki, R.K., Beck, R.J., Crane, D.B., 1995. Effective, Project Management: How to Plan, Manage, and Deliver Projects on Time and within Budget, NY: John Wieley & Sons.
Yabuuchil, Y., Kocaoglu, D., Watada, J., 2006. Analysis of Project Management in Software Development, Technology Management for the Global Future, Vol. 6, pp.2809-2814.
Zigurs, I., Buckland, B.K., 1998. A theory of task-technology fit and group support systems effectiveness, MIS Quarterly, Vol. 22, No. 3, pp.313-334.

指導教授

陳仲儼(Chung-yang Chen)

審核日期

2009-7-8

推文