跳到主要內容

臺灣博碩士論文加值系統

(35.175.191.36) 您好!臺灣時間:2021/08/01 00:41
字體大小: 字級放大   字級縮小   預設字形  
回查詢結果 :::

詳目顯示

我願授權國圖
: 
twitterline
研究生:趙耿暉
研究生(外文):Keng-Hui Chao
論文名稱:運用會議流模式來具體化軟體品質規範中有關需求生命週期管理之研究:以CMMI模式為例
論文名稱(外文):Implementing Software Requirement Life Cycle Management in CMMI using the Meeting Flow Model
指導教授:陳仲儼陳仲儼引用關係
指導教授(外文):Chung-Yang Chen
學位類別:碩士
校院名稱:長庚大學
系所名稱:資訊管理研究所
學門:電算機學門
學類:電算機一般學類
論文種類:學術論文
論文出版年:2007
畢業學年度:95
語文別:中文
論文頁數:76
中文關鍵詞:能力成熟渡整合模式軟體專案管理需求工程流程專注
外文關鍵詞:CMMISoftware Project ManagementRequirement EngineeringProcess Focus
相關次數:
  • 被引用被引用:3
  • 點閱點閱:139
  • 評分評分:
  • 下載下載:0
  • 收藏至我的研究室書目清單書目收藏:2
1984年SEI提出CMMI模式,提供軟體開發廠商流程發展時所需的規範。然而,CMMI模式提供流程發展時所需的規範及產出,並非具體的運作方式,導致CMMI模式給人抽象不易瞭解,過多產出及不易直接實施的印象。
對於軟體專案開發而言,傳統專案管理的過程時常過於片面與片段,而流程導向的專案管理方式為因之興起的管理方式。另一方面,需求開發是專案管理重要之工作,在執行需求工程的過程中常因溝通不良、未有良好的輔助工具等問題,導致專案進度、時程受到影響,甚至專案因而失敗。
因此,本研究結合會議運作流程模式對需求工程過程,運用CMMI的流程規範與文件產出將需求工程過程予以系統化、具體化,藉此提出一制度化的需求工程管理架構。此架構具管理不同層次、複雜的團隊合作,並且減低導入CMMI的困難度,協助企業達到CMMI的流程規範,利於企業面對系統日趨複雜的多元需求下,有效管理、實行開發流程。
SEI proposed CMMI model to offer necessary guidelines of software development process for manufacturers in 1984. Because the necessary guidelines and output of processing procedures that CMMI model offers are not concrete operations, it always makes the impressions on people that CMMI model is hard to understand, implement directly, and it has excessive outputs.
Project Management procedures were often too one-sided and trivial, so process-oriented project management arises and develops gradually. On the other hand, requirement development is an important part of project management. During the processes of carrying out the requirement engineering, some problems, such as bad communication and unsuitable assistant tools, etc., influence project progress and the schedule, and even make the project fail.
Consequently, this research, which accords with the meeting flow model to the requirement engineering, uses procedure guidelines and document output of CMMI to make the requirement engineering systematized and specified, and presents an institutionalized requirement engineering model. This model can help enterprises to manage different levels and complicated team cooperation, lower the difficulty in applying CMMI, and reach the procedure guidelines of CMMI, it makes it easier for the enterprises to make the management more efficient and implement the developing procedure under the requirements of the more and more complicated system.
長庚大學碩士論文著作授權書 iii
誌謝 iv
摘要 v
Abstract vi
目錄 viii
圖目錄 xi
表目錄 xiii
第一章 介紹 1
1.1 研究背景 1
1.2 流程導向專案管理與會議流 3
1.3 問題與研究動機 4
1.4 研究目的與預期效益:運用會議流模式來具體化CMMI規範 5
1.5 範圍與假設 6
1.6 研究步驟 6
第二章 文獻探討 9
2.1 專案管理(Project Management) 10
2.1.1 專案(Project) 10
2.1.2 專案管理(Project Management) 12
2.2 能力成熟度整合模式(CMMI) 13
2.2.1 CMM與CMMI 歷史沿革 13
2.2.2 CMMI模式 16
2.3 會議流管理 20
2.3.1 會議 20
2.3.2 專案開發的四大作業 21
2.4 需求工程 22
2.4.1 需求(Requirement) 22
2.4.2 需求工程(Requirement Engineering) 23
第三章 研究理論與架構 25
3.1 需求定義 25
3.2 需求工程 26
3.3 會議流模式與CMMI 32
3.4 會議流模式加強上下層級間的溝通 41
第四章 系統實作 45
4.1 系統架構 45
4.2 系統功能介紹 49
第五章 討論 66
第六章 結論與未來方向 68
6.1 結論 68
6.2 未來工作 70
參考文獻 72
中文部分:
[1]Luecke, R. 著,專案,就是要這樣管理,林凡譯,天下遠見出版,民國九十五年。
[2]林漢聲,「運用Petri Net來塑模軟體專案開發之會議流管理模式」,私立長庚大學,碩士論文,民國九十六年。
[3]資策會,CMMISM 導入指引 V1.0 (第三級),財團法人資訊工業策進會 資訊工程研究所,民國九十二年。
[4]溪江華,聖殿祭司的ASP.NET 2.0 專家技術,碁峰資訊,民國九十五年。
[5]章立民工作室,ASP.NET AJAX經典範例100 使用VB,碁峰資訊,民國九十六年。
[6]陳仲儼,「會議運作流程模式為基礎之專案管理:一項新方法」,中華民國資訊軟體協會,台北,民國九十四年。
[7]陳炳昇,「應用群組技術來調適專案管理會議流程運作之研究」,私立長庚大學,碩士論文,民國九十六年。

英文部分:
[1]Bersoff, E.H., Davis. A.M., ”Impacts of life cycle models on software configuration management”, Communications of the ACM, 34, 8, pp. 104-117, 1991.
[2]Boehm, B.W., “SOFTWARE ENGINEERING.”, IEEE transactions on computers, C-25, 12, pp.1226-1241, 1976.
[3]Brooks J., Frederick P. “No Silver Bullet: Essence and Accidents of Software Engineering”, Computer, 20, 4, pp. 10-19, 1987.
[4]Chrissis, M.B., Konrad, M., Shrum, S., Cmmi: Guidelines for Process Integration and Product Improvement, 5th printing Addison-Wesley, Boston, 2004.
[5]Cleland, D.I., King W.R., Systems Analysis and Project Management, McGraw-Hill, New York, 1983.
[6]Crosby, P.B., Quality is free, McGraw-Hill, New York, 1979.
[7]CMMI Product Team, CMMI® for Development, Version 1.2, 2006.
[8]Damian. D., Chisan, J., “An Empirical Study of the Complex Relationships between Requirements Engineering Process and Other Processes that Lead to Payoffs in Productivity, Quality, and Risk Management”, IEEE transactions on computers, 32, 7, pp.433-453, 2006.
[9]Dennis, A., Wixom, B.H., Tegarden, D., Systems analysis and design with UML version 2.0: an object-oriented approach, 2nd Ed., John Wiley & Sons, New Jersey, 2004.
[10]Dooley, A., “The death of project management”, IEE Review, 44, 1, pp.28-29, 1998.
[11]Duncan, W.R., A Guide to the Project Management Body of Knowledge, 1996.
[12]Faulk, S.R., Software requirements: A tutorial. Tech. Rep. NRL-7775, Naval Research Laboratory, Washington, D.C. 1995.
[13]Fliedl, G., Kop, C., Mayr, H.C., Salbrechter, A., Vohringer, J., Weber, G., Winkler, C., “Deriving static and dynamic concepts from software requirements using sophisticated tagging”, Data & Knowledge Engineering, 61, 3, pp.433-488, 2007.
[14]Hassan, G., “Reusable software requirements and architecture for families of systems”, The Journal of systems and software, 28, 3, pp.189-202, 1995.
[15]Heerkens, G.R., Project Management, McGraw-Hill, New York, 2001.
[16]Hollingsworth, D., Workflow Management Coalition The Workflow Reference Model, Workflow Management Coalition, 1994.
[17]IEEE Standards Board, IEEE Standard Glossary of Software Engineering Terminology, IEEE Standards Board, 1990.
[18]Keil, M., Rai, A., Cheney Mann, J.E., Zhang, G.P., “Why software projects escalate: the importance of project management constructs”, IEEE Transactions on Engineering Management, 50, 3, pp.251-261, 2003.
[19]Kerzner, H., Project Management: A Systems Approach to Planning , Scheduling and Controlling, 8th Ed., John Wiley & Sons, New Jersey, 2003.
[20]Knudson, J. and Bitz, I., Project management:How to plan and manage successful projects, AMACOM, New York, 1991.
[21]Kotonya, G., Sommerville, I., “Requirements engineering with viewpoints”, Software engineering journal, 11, 1, pp.5-18, 1996.
[22]Meredith, J. R. and Mantel, S. I., Project Management, John Wiley & Sons., New York, 1989.
[23]Paulk, M.C., Curtis, B., Chrissis, M.B., Weber, C.V., Capability Maturity ModelSM for Software,Version 1.1, 1993.
[24]Pressman, R.S., Software Engineering A practitioner’s Approach, McGraw-Hill, New York, 2005.
[25]Project Management Institute, A Guide to the Project Management Body of Knowledge (PMBOK Guide) Third Edition, Project Management Institute, 2004.
[26]Rakos, J.J., Software Project Management for Small to Medium Sized Projects, Prentice Hall, New Jersey, 1990.
[27]Sieli, E.M., “Managing a Project as a Process ”, AT&T Technical Journal, 70, 2, pp.33-39, 1991.
[28]The Standish Group, The CHAOS Report (1994), The Standish Group, 2003.
[29]Verner, J.M.; Evanco, W.M., “In-house software development: What project management practices lead to success?”, IEEE Software, 22, 1, pp.86-93, 2005.
[30]Wang, Q., Li, M.,”Software process management: Practices in china ”, Lecture Notes in Computer Science, 3840, pp. 317-331, 2006.
[31]Wysocki, R.K., Jr, R.B., Crane, D.C., Effective, Project Management: How to Plan, Manage, and Deliver Projects on Time and within Budget, John Wiley & Sons, New York, 1995.
QRCODE
 
 
 
 
 
                                                                                                                                                                                                                                                                                                                                                                                                               
第一頁 上一頁 下一頁 最後一頁 top