1. NCCU Academic Hub
  2. 學術產出
  3. College of Commerce
  4. Theses
  5. Item

學術產出-Theses

Article View/Open

Publication Export

Google ScholarTM

政大圖書館

Citation Infomation

  • No doi shows Citation Infomation
題名 Requirements Management of Software Development in CMMI
以CMMI為基礎提升軟體開發需求管理
作者 蘇毓婷
Su, Yu-Ting
貢獻者 曾淑峰
Tseng, Shu-Feng
蘇毓婷
Su, Yu-Ting
關鍵詞 能力成熟度整合模式
統一流程
需求管理
需求工程
CMMI
RUP
Requirements Management
Requirements Engineering
日期 2003
上傳時間 18-Sep-2009 14:27:18 (UTC+8)
摘要 在軟體開發的過程中，有效的需求管理能促成高品質的軟體及管理。在CMMI中與需求管理有關的議題包括需求發展(Requirements Development)流程領域-屬於CMMI成熟度第三級，提供一些目標、執行方法(practices)和相關資訊作為指引，協助開發團隊發展顧客需求和產品需求。另一個相關議題-需求管理(Requirements Management) 流程領域，屬於CMMI成熟度第二級，可用於幫助需求管理的規劃與控制，建立追蹤機制，以及評估改變衝擊。
本篇論文以達成CMMI中需求發展和需求管理流程領域目標為前提，利用概念形成(Concept Formulation)和系統展示(System Representation)研究方法，並調適RUP中的需求工作流程(workflow)，最後發展出一個整合的需求管理架構-稱為IREQM(Integrated Requirements Management)，用於處理需求面的問題。本研究亦根據IREQM架構進行實作，發展出一套可協助軟體需求發展與管理的支援系統。最後，我們利用自我評鑑表，評估IREQM及依據IREQM實作的雛型系統與CMMI目標和執行方法相符的程度。
Effective requirements management can help the software development process to ensure a high-quality software development and management process. In CMMI, the process area RD (Requirements Development) provides a set of goals, practices, and related features to develop customer and product requirements, and the process area REQM (Requirements Management) is to help establishing and appraising the quality of requirements management. Both issues are covered by the generic requirement management concerns.
This study is conducted by the Concept Formulation and System Representation method to develop a systematic process to deal with the requirements issues in the software development process, in order to meet the RD and REQM goals in CMMI. The study proposes an integrated requirement management framework, called IREQM, tailored from the requirements workflow in RUP. A CMMI support system, to implement IREQM is established to facilitate the REQM and RD activities during the software development process. Finally, a self-appraisal checklist is used to evaluate the compliance of the IREQM framework and its implementation to the CMMI model.
參考文獻 [1]. Andriole, S., “The politics of requirements management,” Software IEEE (15:6), Nov.-Dec. 1998, pp.82 -84.
[2]. Boggs, W. and Boggs, M., Mastering UML with Rational Rose 2002, Sybex Inc., 2002.
[3]. CHAOS, The Standish Group International, Inc., Dennis, MA, 1994, 1997.
[4]. Carnegie Mellon University Software Engineering Institute (CMU/SEI), “CMMI Version 1.1 Tutorial Materials,” Presentation by Mike Phillips at the European Software Engineering Process Group Conference April 2002, Revised April 2003, from the World Wild Web: http://www.sei.cmu.edu/cmmi/presentations/euro-sepg-tutorial/
[5]. Capability Maturity Model for Software (SW-CMM), 1993, from the World Wild Web: http://www.sei.cmu.edu/.
[6]. Carnegie Mellon University Software Engineering Institute, Capability Maturity Model Integration, Version 1.1, CMU/SEI-2002-TR-001.
[7]. Carnegie Mellon University Software Engineering Institute (CMU/SEI), Appraisal Requirements for CMMISM, Version 1.1(ARC, V1.1), 2001a, Technical Report, from the World Wild Web: http://www.sei.cmu.edu/publications/documents/01.reports/01tr034.html
[8]. Carnegie Mellon University Software Engineering Institute (CMU/SEI), Standard CMMISM Appraisal Method for Process Improvement (SCAMPISM), Version 1.1:Method Definition Document,” 2001b, Technical Report, from the World Wild Web: http://www.sei.cmu.edu/publications/documents/01.reports/01hb001.html
[9]. Eriksson, H. E. and Penker, M. Business Modeling with UML—Business Patterns at Work, John Wiley & Son, Inc., 2000.
[10]. Grady, R. B., Practical Software Metrics for Project Management and Process Improvement. Prentice-Hall, 1992.
[11]. Loucopoulos, P. and Karakostas V., System Requirements Engineering, McGraw-Hill, Inc., 1995.
[12]. IEEE Standard 729, IEEE Standard Glossary of Software Engineering Terminology, Institute of Electrical and Electronic Engineers (IEEE), New York, 1983.
[13]. Information System Laboratory (ISL), Capability Maturity Model Integration Adoption Guidelines, Institute For Information Industry, 2002.
[14]. Jalote, P., CMM in Practice: Processes for Executing Software Projects at Infosys, Addison-Wesley, Inc., 1999.
[15]. Manzoni, L.V. and Price, R.T., “Identifying Extensions Required by RUP(Rational Unified Processes) to Comply with CMM (Capability Maturity Model) Level 2 and Level 3”, IEEE Transactions on Software Engineering (29:2), Feb. 2003, pp.181- 192.
[16]. Object Dynamics, Ltd. Final Report of Project Consulting Case sponsored by Industrial Development Bureau Ministry of Economic Affairs, Taiwan, ROC, 2003.
[17]. Paulk, M. C., Curtis, B., Chrissis, M. B., and Weber, C. V., Capability Maturity Model for Software, Version1.1, Technical Report CMU/SEI-93-TR-024, Software Eng. Inst., Carnegie Mellon Univ., Pittsburgh, Penn., 1993, from the World Wild Web: http://www.sei.cmu.edu/pub/documents/93.reports/pdf/tr24.93.pdf
[18]. Paulk, M.C., Weber, C. V., Garcia S.M., Chrissis, M. B., and Bush, M., Key Practices of Capability Maturity Model for Software, Technical Report CMU/SEI-93-025, Software Eng. Inst., Carnegie Mellon Univ., Pittsburgh, Penn.,1993, from the World Wild Web: http://www.sei.cmu.edu/pub/documents/93.reports/pdf/tr25.93.pdf
[19]. Rational Software Corporation, “Rational Unified Process,” Version 2003, CD-ROM, Rational Software Product.
[20]. Rational Software Corporation, Applying Requirements Management with Use Case, White Paper, 2000a.
[21]. Rational Software Corporation, Reaching CMM Level 2 and 3 with the Rational Unified Process, White Paper, 2000b.
[22]. Rational Software Corporation, Traceability Strategies for Managing Requirements with Use Cases, White Paper, 1998.
[23]. Scott-Morton, M.S., “The State of the Art of Research”, The Information Systems Research, edited by W. McFarlan, Harvard Business School Press, Boston, 1984, pp.13-41.
[24]. Sommerville, I. and Sawyer, P., Requirements Engineering: A good Practice Guide, Wiley and Sons, 1997.
[25]. Wang, Q. and Lai, X., ”Requirements management for the incremental development model,” Proceedings of Second Asia-Pacific Conference on Quality Software,10-11 Dec. 2001, pp.295 -301.
[26]. The Zachman Institute for Framework Advancement (ZIFA), 2003, from the World Wild Web: http://www.zifa.com/
[27]. 梁定澎，1997，「資訊管理研究方法總論」，資訊管理學報，資訊管理實證研究方法討論會特刊，第四卷第一期：1 - 7頁。
[28]. 黃鈺峰、趙光正譯，Phillippe Kruchten著，2002，Rational統一流程入門，第二版，臺北縣：維科。
[29]. 方弘信，2003，水產飼料集團管理資訊需求規劃，國立台灣海洋大學水產養殖學系碩士論文。
[30]. 朱明強，2002，以企業樣版為基礎之需求分析架構，國立政治大學資訊管理學系碩士論文。
[31]. 宋珍儀，2001，資訊需求分析架構之研究—以網路基金下單應用為例，國立政治大學資訊管理學系碩士論文。
[32]. 資訊工業策進會資訊系統實驗室，2002，CMMI導入指引V1.0，臺北市：資策會資訊系統實驗室。
[33]. 資策會，2004-02-02，CMMI技術服務網 - http://www.cmmi.org.tw
描述 碩士
國立政治大學
資訊管理研究所
91356028
92
資料來源 http://thesis.lib.nccu.edu.tw/record/#G0091356028
資料類型 thesis
dc.contributor.advisor 曾淑峰zh_TW
dc.contributor.advisor Tseng, Shu-Fengen_US
dc.contributor.author (Authors) 蘇毓婷zh_TW
dc.contributor.author (Authors) Su, Yu-Tingen_US
dc.creator (作者) 蘇毓婷zh_TW
dc.creator (作者) Su, Yu-Tingen_US
dc.date (日期) 2003en_US
dc.date.accessioned 18-Sep-2009 14:27:18 (UTC+8)-
dc.date.available 18-Sep-2009 14:27:18 (UTC+8)-
dc.date.issued (上傳時間) 18-Sep-2009 14:27:18 (UTC+8)-
dc.identifier (Other Identifiers) G0091356028en_US
dc.identifier.uri (URI) https://nccur.lib.nccu.edu.tw/handle/140.119/35210-
dc.description (描述) 碩士zh_TW
dc.description (描述) 國立政治大學zh_TW
dc.description (描述) 資訊管理研究所zh_TW
dc.description (描述) 91356028zh_TW
dc.description (描述) 92zh_TW
dc.description.abstract (摘要) 在軟體開發的過程中，有效的需求管理能促成高品質的軟體及管理。在CMMI中與需求管理有關的議題包括需求發展(Requirements Development)流程領域-屬於CMMI成熟度第三級，提供一些目標、執行方法(practices)和相關資訊作為指引，協助開發團隊發展顧客需求和產品需求。另一個相關議題-需求管理(Requirements Management) 流程領域，屬於CMMI成熟度第二級，可用於幫助需求管理的規劃與控制，建立追蹤機制，以及評估改變衝擊。
本篇論文以達成CMMI中需求發展和需求管理流程領域目標為前提，利用概念形成(Concept Formulation)和系統展示(System Representation)研究方法，並調適RUP中的需求工作流程(workflow)，最後發展出一個整合的需求管理架構-稱為IREQM(Integrated Requirements Management)，用於處理需求面的問題。本研究亦根據IREQM架構進行實作，發展出一套可協助軟體需求發展與管理的支援系統。最後，我們利用自我評鑑表，評估IREQM及依據IREQM實作的雛型系統與CMMI目標和執行方法相符的程度。		zh_TW
dc.description.abstract (摘要) Effective requirements management can help the software development process to ensure a high-quality software development and management process. In CMMI, the process area RD (Requirements Development) provides a set of goals, practices, and related features to develop customer and product requirements, and the process area REQM (Requirements Management) is to help establishing and appraising the quality of requirements management. Both issues are covered by the generic requirement management concerns.
This study is conducted by the Concept Formulation and System Representation method to develop a systematic process to deal with the requirements issues in the software development process, in order to meet the RD and REQM goals in CMMI. The study proposes an integrated requirement management framework, called IREQM, tailored from the requirements workflow in RUP. A CMMI support system, to implement IREQM is established to facilitate the REQM and RD activities during the software development process. Finally, a self-appraisal checklist is used to evaluate the compliance of the IREQM framework and its implementation to the CMMI model.		en_US
dc.description.tableofcontents Chapter 1 Introduction 1
1.1 Research Background and Motivation 1
1.2 Research Method 2
1.3 Research Objectives 2
1.4 Thesis Organization 2
Chapter 2 Literature Review 4
2.1 Requirements issues 4
2.1.1 Requirements 4
2.1.2 Requirements Engineering 4
2.1.3 Requirements Management 7
2.2 CMMI (Capability Maturity Model Integration) and CMM (Capability Maturity Model) 8
2.2.1 CMMI (Capability Maturity Model Integration) 8
2.2.2 REQM in CMMI 8
2.2.3 RD in CMMI 9
2.2.4 The Interaction of RD and REQM in CMMI 10
2.2.5 CMM (Capability Maturity Model) 11
2.3 RUP (Rational Unified Process) 12
2.3.1 REQM in RUP 12
2.3.2 UML (Unified Modeling Language) 15
2.3.3 Other Key Items and Concepts in RUP 15
2.4 RUP and REQM/RD process area in CMMI 17
Chapter 3 The Integrated Requirements Management Framework (IREQM) 20
3.1 The Framework Description 20
3.1.1 Background Analysis and Requirements Management Planning (RMP) 22
3.1.2 Requirements Development (RD) 23
3.1.3 Requirements Change Management (RCM) 25
3.2 CMMI Goals and Practices Achieved by IREQM 27
Chapter 4 IREQM Framework Implementation - AutoREQM Prototype 28
4.1 Background Analysis 28
4.2 Requirements Management Planning via RMP 29
4.3 Requirements Development via RD 31
4.3.1 Develop Vision 31
4.3.2 Understand Stakeholder Needs and Elicit Stakeholder Requests 32
4.3.3 Analyze Functions (Features) 32
4.3.4 Analyze Operational Workflow 33
4.3.5 Find, Prioritize and Detail Use Cases 37
4.3.6 Analyze Supplementary Specification and Capture Common Vocabulary 40
4.3.7 Validate Requirements 40
4.4 Screen Display of AutoREQM with Internet-Banking Example 40
Chapter 5 CMMI Self-Appraisal 58
Chapter 6 Conclusions and Future Research 65
References 67

List of Figures
Figure 1 The Research Process 3
Figure 2 Requirements Engineering Process (Loucopoulos and Karakostas, 1995) 5
Figure 3 Zachman Framework (Zachman, 2003) 7
Figure 4 The Requirements Workflow in RUP (Rational Software Corporation, 2003) 14
Figure 5 Activities within Requirements Workflow in RUP and Roles Responsible for Them (Rational Software Corporation, 2003) 15
Figure 6 IREQM Framework 21
Figure 7 Insititutionalized RD Process 23
Figure 8 Insitutionalized RCM Process 25
Figure 9 Manage RD Artifacts 34
Figure 10 Manage Requirement Change 35
Figure 11 Support Management Change 36
Figure 12 AutoREQM Use Case Packages 37
Figure 13 Use Case Diagram Contained in RD Package 37
Figure 14 Use Case Diagram Contained in RCM Package 38
Figure 15 Use Case Diagram Contained in Management Support Package 38


List of Tables
Table 1 GGs, GPs, SGs and SPs of REQM in CMMI (CMU/SEI, 2002) 8
Table 2 GGs, GPs, SPs and SPs of RD in CMMI (CMU/SEI, 2002) 9
Table 3 Engineering Process Areas in CMMI 11
Table 4 REQM Goals in CMM 12
Table 5 Software Product Engineering Goals in CMM 12
Table 6 Requirements Workflow Details in RUP (Rational Software Corporation, 2003) 14
Table 7 key Requirements Management Items in RUP (Rational Software Corporation, 2003) 16
Table 8 The Missing or Incomplete CMM Key Practices Required in RUP 18
Table 9 The Corresponded CMMI Key Practices of REQM and RD 18
Table 10 5W1H Analysis for the IREQM Framework 22
Table 11 5W1H Analysis for the RD Process 24
Table 12 5W1H Analysis for the Institutionalized RCM 26
Table 13 Traceability Relationships and Complementary Documents 30
Table 14 Traceability Criteria 30
Table 15 Requirements Types and Attributes 30
Table 16 Problem Statements 31
Table 17 Stakeholder Descriptions 31
Table 18 Derived Features with Stakeholder Needs in AutoREQM 33
Table 19 Prioritized Use Cases 39
Table 20 Sample NEEDs, FEATs, UCs, and Traceability Relationships 41
Table 21 Sample Requests for Requirements Change 42
Table 22 Characteristics of CMMI Appraisal Method Classes 58
Table 23 Appraisal Checklist for Supporting REQM Process Area in CMMI Level 2 59
Table 24 Appraisal Checklist for Supporting RD Process Area in CMMI Level 3 61		zh_TW
dc.format.extent 121001 bytes-
dc.format.extent 123675 bytes-
dc.format.extent 129686 bytes-
dc.format.extent 62562 bytes-
dc.format.extent 126358 bytes-
dc.format.extent 345797 bytes-
dc.format.extent 78575 bytes-
dc.format.extent 447595 bytes-
dc.format.extent 81887 bytes-
dc.format.extent 55632 bytes-
dc.format.extent 128804 bytes-
dc.format.mimetype application/pdf-
dc.format.mimetype application/pdf-
dc.format.mimetype application/pdf-
dc.format.mimetype application/pdf-
dc.format.mimetype application/pdf-
dc.format.mimetype application/pdf-
dc.format.mimetype application/pdf-
dc.format.mimetype application/pdf-
dc.format.mimetype application/pdf-
dc.format.mimetype application/pdf-
dc.format.mimetype application/pdf-
dc.language.iso en_US-
dc.source.uri (資料來源) http://thesis.lib.nccu.edu.tw/record/#G0091356028en_US
dc.subject (關鍵詞) 能力成熟度整合模式zh_TW
dc.subject (關鍵詞) 統一流程zh_TW
dc.subject (關鍵詞) 需求管理zh_TW
dc.subject (關鍵詞) 需求工程zh_TW
dc.subject (關鍵詞) CMMIen_US
dc.subject (關鍵詞) RUPen_US
dc.subject (關鍵詞) Requirements Managementen_US
dc.subject (關鍵詞) Requirements Engineeringen_US
dc.title (題名) Requirements Management of Software Development in CMMIzh_TW
dc.title (題名) 以CMMI為基礎提升軟體開發需求管理zh_TW
dc.type (資料類型) thesisen
dc.relation.reference (參考文獻) [1]. Andriole, S., “The politics of requirements management,” Software IEEE (15:6), Nov.-Dec. 1998, pp.82 -84.zh_TW
dc.relation.reference (參考文獻) [2]. Boggs, W. and Boggs, M., Mastering UML with Rational Rose 2002, Sybex Inc., 2002.zh_TW
dc.relation.reference (參考文獻) [3]. CHAOS, The Standish Group International, Inc., Dennis, MA, 1994, 1997.zh_TW
dc.relation.reference (參考文獻) [4]. Carnegie Mellon University Software Engineering Institute (CMU/SEI), “CMMI Version 1.1 Tutorial Materials,” Presentation by Mike Phillips at the European Software Engineering Process Group Conference April 2002, Revised April 2003, from the World Wild Web: http://www.sei.cmu.edu/cmmi/presentations/euro-sepg-tutorial/zh_TW
dc.relation.reference (參考文獻) [5]. Capability Maturity Model for Software (SW-CMM), 1993, from the World Wild Web: http://www.sei.cmu.edu/.zh_TW
dc.relation.reference (參考文獻) [6]. Carnegie Mellon University Software Engineering Institute, Capability Maturity Model Integration, Version 1.1, CMU/SEI-2002-TR-001.zh_TW
dc.relation.reference (參考文獻) [7]. Carnegie Mellon University Software Engineering Institute (CMU/SEI), Appraisal Requirements for CMMISM, Version 1.1(ARC, V1.1), 2001a, Technical Report, from the World Wild Web: http://www.sei.cmu.edu/publications/documents/01.reports/01tr034.htmlzh_TW
dc.relation.reference (參考文獻) [8]. Carnegie Mellon University Software Engineering Institute (CMU/SEI), Standard CMMISM Appraisal Method for Process Improvement (SCAMPISM), Version 1.1:Method Definition Document,” 2001b, Technical Report, from the World Wild Web: http://www.sei.cmu.edu/publications/documents/01.reports/01hb001.htmlzh_TW
dc.relation.reference (參考文獻) [9]. Eriksson, H. E. and Penker, M. Business Modeling with UML—Business Patterns at Work, John Wiley & Son, Inc., 2000.zh_TW
dc.relation.reference (參考文獻) [10]. Grady, R. B., Practical Software Metrics for Project Management and Process Improvement. Prentice-Hall, 1992.zh_TW
dc.relation.reference (參考文獻) [11]. Loucopoulos, P. and Karakostas V., System Requirements Engineering, McGraw-Hill, Inc., 1995.zh_TW
dc.relation.reference (參考文獻) [12]. IEEE Standard 729, IEEE Standard Glossary of Software Engineering Terminology, Institute of Electrical and Electronic Engineers (IEEE), New York, 1983.zh_TW
dc.relation.reference (參考文獻) [13]. Information System Laboratory (ISL), Capability Maturity Model Integration Adoption Guidelines, Institute For Information Industry, 2002.zh_TW
dc.relation.reference (參考文獻) [14]. Jalote, P., CMM in Practice: Processes for Executing Software Projects at Infosys, Addison-Wesley, Inc., 1999.zh_TW
dc.relation.reference (參考文獻) [15]. Manzoni, L.V. and Price, R.T., “Identifying Extensions Required by RUP(Rational Unified Processes) to Comply with CMM (Capability Maturity Model) Level 2 and Level 3”, IEEE Transactions on Software Engineering (29:2), Feb. 2003, pp.181- 192.zh_TW
dc.relation.reference (參考文獻) [16]. Object Dynamics, Ltd. Final Report of Project Consulting Case sponsored by Industrial Development Bureau Ministry of Economic Affairs, Taiwan, ROC, 2003.zh_TW
dc.relation.reference (參考文獻) [17]. Paulk, M. C., Curtis, B., Chrissis, M. B., and Weber, C. V., Capability Maturity Model for Software, Version1.1, Technical Report CMU/SEI-93-TR-024, Software Eng. Inst., Carnegie Mellon Univ., Pittsburgh, Penn., 1993, from the World Wild Web: http://www.sei.cmu.edu/pub/documents/93.reports/pdf/tr24.93.pdfzh_TW
dc.relation.reference (參考文獻) [18]. Paulk, M.C., Weber, C. V., Garcia S.M., Chrissis, M. B., and Bush, M., Key Practices of Capability Maturity Model for Software, Technical Report CMU/SEI-93-025, Software Eng. Inst., Carnegie Mellon Univ., Pittsburgh, Penn.,1993, from the World Wild Web: http://www.sei.cmu.edu/pub/documents/93.reports/pdf/tr25.93.pdfzh_TW
dc.relation.reference (參考文獻) [19]. Rational Software Corporation, “Rational Unified Process,” Version 2003, CD-ROM, Rational Software Product.zh_TW
dc.relation.reference (參考文獻) [20]. Rational Software Corporation, Applying Requirements Management with Use Case, White Paper, 2000a.zh_TW
dc.relation.reference (參考文獻) [21]. Rational Software Corporation, Reaching CMM Level 2 and 3 with the Rational Unified Process, White Paper, 2000b.zh_TW
dc.relation.reference (參考文獻) [22]. Rational Software Corporation, Traceability Strategies for Managing Requirements with Use Cases, White Paper, 1998.zh_TW
dc.relation.reference (參考文獻) [23]. Scott-Morton, M.S., “The State of the Art of Research”, The Information Systems Research, edited by W. McFarlan, Harvard Business School Press, Boston, 1984, pp.13-41.zh_TW
dc.relation.reference (參考文獻) [24]. Sommerville, I. and Sawyer, P., Requirements Engineering: A good Practice Guide, Wiley and Sons, 1997.zh_TW
dc.relation.reference (參考文獻) [25]. Wang, Q. and Lai, X., ”Requirements management for the incremental development model,” Proceedings of Second Asia-Pacific Conference on Quality Software,10-11 Dec. 2001, pp.295 -301.zh_TW
dc.relation.reference (參考文獻) [26]. The Zachman Institute for Framework Advancement (ZIFA), 2003, from the World Wild Web: http://www.zifa.com/zh_TW
dc.relation.reference (參考文獻) [27]. 梁定澎，1997，「資訊管理研究方法總論」，資訊管理學報，資訊管理實證研究方法討論會特刊，第四卷第一期：1 - 7頁。zh_TW
dc.relation.reference (參考文獻) [28]. 黃鈺峰、趙光正譯，Phillippe Kruchten著，2002，Rational統一流程入門，第二版，臺北縣：維科。zh_TW
dc.relation.reference (參考文獻) [29]. 方弘信，2003，水產飼料集團管理資訊需求規劃，國立台灣海洋大學水產養殖學系碩士論文。zh_TW
dc.relation.reference (參考文獻) [30]. 朱明強，2002，以企業樣版為基礎之需求分析架構，國立政治大學資訊管理學系碩士論文。zh_TW
dc.relation.reference (參考文獻) [31]. 宋珍儀，2001，資訊需求分析架構之研究—以網路基金下單應用為例，國立政治大學資訊管理學系碩士論文。zh_TW
dc.relation.reference (參考文獻) [32]. 資訊工業策進會資訊系統實驗室，2002，CMMI導入指引V1.0，臺北市：資策會資訊系統實驗室。zh_TW
dc.relation.reference (參考文獻) [33]. 資策會，2004-02-02，CMMI技術服務網 - http://www.cmmi.org.twzh_TW