Loading...
|
Please use this identifier to cite or link to this item:
https://nccur.lib.nccu.edu.tw/handle/140.119/35210
|
Title: | Requirements Management of Software Development in CMMI 以CMMI為基礎提升軟體開發需求管理 |
Authors: | 蘇毓婷 Su, Yu-Ting |
Contributors: | 曾淑峰 Tseng, Shu-Feng 蘇毓婷 Su, Yu-Ting |
Keywords: | 能力成熟度整合模式 統一流程 需求管理 需求工程 CMMI RUP Requirements Management Requirements Engineering |
Date: | 2003 |
Issue Date: | 2009-09-18 14:27:18 (UTC+8) |
Abstract: | 在軟體開發的過程中,有效的需求管理能促成高品質的軟體及管理。在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. |
Reference: | [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 |
Description: | 碩士 國立政治大學 資訊管理研究所 91356028 92 |
Source URI: | http://thesis.lib.nccu.edu.tw/record/#G0091356028 |
Data Type: | thesis |
Appears in Collections: | [資訊管理學系] 學位論文
|
All items in 政大典藏 are protected by copyright, with all rights reserved.
|