請用此 Handle URI 來引用此文件：
http://tdr.lib.ntu.edu.tw/jspui/handle/123456789/26656完整後設資料紀錄
| DC 欄位 | 值 | 語言 |
|---|---|---|
| dc.contributor.advisor | 翁崇雄(Chorng-Shyong Ong) | |
| dc.contributor.author | Tsung-Yuan Luo | en |
| dc.contributor.author | 駱聰元 | zh_TW |
| dc.date.accessioned | 2021-06-08T07:19:27Z | - |
| dc.date.copyright | 2008-08-05 | |
| dc.date.issued | 2008 | |
| dc.date.submitted | 2008-07-24 | |
| dc.identifier.citation | [1] 經濟部工業局提升資訊軟體品質(Capability Maturity Model - Integrated, CMMI)計畫網站http://www.cmmi-taiwan.org.tw/cgi-bin/big5/cmmi。
[2] 經濟日報，2004/10/22。 [3] 黃世禎，「軟體工程度量簡介」，軟體產業通訊，第51 期：50-58 頁，中華民國資訊軟體協會,民國92 年6月。 [4] 黃世禎與呂欣樺，「如何評估軟體產品品質」，軟體產業通訊，第55 期：42-55 頁，中華民國資訊軟體協會，民國92 年12 月。 [5] 黃世禎，「軟體品質工程師手冊—軟體度量與分析」，中華民國品質協會，2005/5。 [6] 沈尚賢，「動態多層式軟體度量與分析模式之研究與工具實作」，國立台灣科技大學資訊管理系，碩士學位論文，2006/6。 [7] 林信惠、黃明祥與王文良，「軟體專案管理」，智勝文化事業有限公司，2002。 [8] 林永松，「支援CMMI 需求管理流程領域之系統開發與實證研究」，朝陽科技大學工業工程與管理系，碩士學位論文，2006/6。 [9] 林靜蘭，「CMMI與軟體工程；論PSM 與 CMMI 的度量流程模式」，電腦科技雜誌128 期，凌群電腦，2008/05， http://dbmaker.syscom.com.tw/mag/128/se-cmmi_01.htm。 [10] 葉顯榮，「全球CMMI導入經驗」，財金資訊056期，2008/3， http://www.fisc.com.tw/FISCWeb/FISCBimonthly/BimonthlyInSideMain.aspx?Volume=56&TNo=264。 [11] 謝明峰，「運用能力成熟度模式改善軟體專案管理品質績效之探討 --- 以國內某電信公司為例」，國立政治大學資訊管理研究所，碩士學位論文， 2004/1。 [12] 姚俊羽「能力成熟度整合模式之導入–以文件管理系統為例」，銘傳大學 資訊管理研究所，碩士論文，2004/5。 [13] 陳莉莉，「CMMI度量與分析流程領域」，資訊工業策進會，資訊工程研究所。 [14] 陳俊彥，「以量化軟體度量指標支援CMMI模式的導入與評鑑」，國立台灣科技大學資訊管理系，碩士論文，2003。 [15] 資訊工程研究所，「適用於發展的能力成熟度整合模式(CMMI-DEV) 」 ，V1.2 版，2006/8，資訊工業策進會。 [16] 韓文銘，「軟體流程領域改善優先順序決策模式」， 國立台灣科技大學資訊管理系，碩士論文，2003。 [17] Alejandro Jose Bianchi , “ Management Indicators Model to Evaluate Performance of IT Organizations ' ,Management of Engineering and Technology, 2001. [18] Chery Jones, 'Using PSM to Fulfill the Measurement Requirements”. [19] Chrissis, M.B., Konrad, M., and Shrum, S. CMMI® Guidelines for Process Integration and Product Improvement, Addison Wesley, Carnegie Mellon Software Engineering Institute (June 2005). [20] CMMI Product Team. “CMMI-SE/SW/IPPD/SS Version 1.1 Stage Representation CMU/SEI-2002-TR-011', Technology Report, Pittsburgh, U.S.A. (2002). [21] CMMI Product Team. “CMMI-SE/SW/IPPD/SS Version 1.1 Continuous Representation CMU/SEI-2002-TR-012', Technology Report, Pittsburgh, U.S.A. (2002). [22] CMMI Product Development Team. CMMI for Systems Engineering/Software Engineering/Integrated Product and Process Development, Version 1.1 Continuous Representation, Carnegie Mellon University, December 2001. [23] CMMI Product Development Team. CMMI for Systems Engineering/Software Engineering/Integrated Product and Process Development, Version 1.1 Staged Representation, Carnegie Mellon University, December 2001. [24] CMMI Product Team. CMMI for Development, Version 1.2 , Carnegie Mellon University, August 2006. [25] Crosby, P.B. Quality is Free, McGraw-Hill, New York. (1997). [26] David Card ,“Integrating Practical Software Measurement and the Balanced Scorecard ' ,27th Annual International Computer Software and Applications Conference ,2003. [27] David Card and Robert Maclver ,“Applying PSM to Enterprise Measurement”,March 2003. [28] Hall , T . and N . Feuton , ' Implementing Effective Software Metrics Program , 'IEEE Software , Mar . / Apr . 1997 , pp . 55 -64． [29] Halstead , M . H . ，Elements of software Science , Elsevier , New York , 1977 . [30] ISO/IEC 15504-5:2006.“Information Technology-Software Process Assessment-Part 5: An Exemplar Process Assessment Model”, March 2006. [31] ISO/IEC 15939,“Software engineering–Software measurement process',2002. [32] ISO/IEC 9126,“ Software and System Engineering – Product quality” ,2003. [33] J. McGary et al.,“Practical Software Measurement-Objective Information for Decision Maker”, Addison Wesley, 2002. [34] John Murdoch , Graham Clark , Antony Powell , Paul Caseley,“Measuring Safety: Applying PSM to the System Safety Domain” , 8th Australian Workshop on Safety Critical Systems and Software (SCS’03), 2003. [35] John Roche, Mike Jackson and Martin Shepperd ,“ Software Measurement Methods: An Evaluation and Perspective ',Assessment of Quality Software Development Tools, 1994. [36] Offen , R . J . and R . Jeffery “Establishing Software Measurement Program ', IEEE Software , Mar . / Apr . 1997 , pp. 45-53 . [37] Margaret Kulpa, Kent A. Johnson, Interpreting the CMMI: A Process Improvement Approach, April 2003. Margaret Kulpa, Kent A. Johnson, Interpreting the CMMI: A Process Improvement Approach, April 2003. [38] McGarry,John; Card, David; Jones, Cheryl; Layman,Beth; Clark, Elizabeth; Dean, Joseph; and Hall, Fred. Practical Software Measurement: Objective Information for Decision Makers. Boston: Addison-Wesley, 2002. [39] Roger S. Pressman. “Software Engineering: a practitioner’s approach”, 6th edition, McGRAW-HILL, 2005. [40] SEI 2001 Paulk, Mark C.; and Chrissis, Mary Beth. The 2001 High Maturity Workshop (CMU/SEI-2001-SR-014). Pittsburgh, PA: Software Engineering Institute, Carnegie Mellon University, January 2002; www.sei.cmu.edu/publications/documents/01.reports/01sr014.html. [41] Shue-Feng Tseng & Chien-Yu Lin, “Requirement Planning for Measurement and Analysis in CMMI', Asia SEPG(SM) 2003 Conference , October 2003. [42] T. DeMarco , Controlling Software Projects: Management,Measurement, and Estimates, June 1986. [43] V. R. Basili , D. M. Weiss, “A methodology for collecting valid software engineering data,” IEEE Trans. Software Eng., vol. 10(3), pp. 728-738, Nov. 1984. [44] V. R. Basili, Rombach, H. Dieter. “The TAME Project: Towards Improvement-Oriented Software Environments'IEEE Transactions on Software Engineering, Vol. 14, No. 6 ,758-773. June 1988. [45] West, M. Real Process Improvement Using the CMMI®, Auerbach (2004). | |
| dc.identifier.uri | http://tdr.lib.ntu.edu.tw/jspui/handle/123456789/26656 | - |
| dc.description.abstract | 能力成熟度整合模式CMMI是用來評估及改善軟體開發過程及開發能力，並且協助軟體開發者持續改善軟體流程架構及品質，進而提昇軟體專案組織之軟體開發管理整合能力，達成軟體發展之功能正確、時程縮短、成本降低及確保品質等目標。CMMI將度量與分析（MA）訂定在組織成熟度第二級以上必備的能力，其目的是發展與維持度量能力，以支援與管理資訊需求，由此可見度量與分析是組織流程邁向高成熟度等級所必需之基礎。藉由度量與分析機制，可以蒐集到專案開發過程中的各項相關資料，經過各種分析方法所得出的資訊，便可作為流程改善及品質管理的依據，並作為管理者在決策制定時的參考。
本研究主要是以CMMI之度量與分析（MA）流程領域為主軸，來研究其模式如何實現，首先針對與本研究相關之主題的文獻資料、國際標準相關之度量方法與流程、各種度量與分析模式進行廣泛地蒐集與彙整。建構一個CMMI度量與分析流程元件的模式，並針對此模式之各項細節進行定義與說明。藉由一個案例進行導入示範說明，以協助其他軟體組織在未來導入CMMI度量與分析流程元件時，能提昇工作效率並有效累積各種度量資訊。 | zh_TW |
| dc.description.abstract | The purpose of CMMI is not only to appraise and improve the software development processes and development skills, but also help individuals improve the software process structure and its quality continuously. Henceforth, promote the organization’s capability to integrate and manage software development, and eventually, meet the functional requirement precisely, condensing the schedule, cost curtailment and quality assurance. The purpose of measurement and analysis being set at CMMI maturity level 2 is to develop and sustain the measurement capability that is used to support and manage information needs. This proves the necessity and importance of measurement and analysis the base for the organization to migrate to a higher level of maturity. By means of this facility, the relevant data produced during the development process can be gathered and the analyzed results be used as the base of process improvement and quality management. Furthermore, serve as the reference for policymaker to make policy.
This study centers on measurement and analysis of CMMI and tries to develop a concrete model. To broadly collect and compile any documentation, any kind of measurement and analysis model and international criteria for measurement method and process that’s related to this study. Build up a model of CMMI measurement and analysis process template and proceed to definitions and descriptions in detail. Demonstrate the implementation by means of a case study. This is to assist other organizations while implementing a process template of measurement and analysis of CMMI to boost work efficiency and to accumulate the organizations’ measurement reserves effectively. | en |
| dc.description.provenance | Made available in DSpace on 2021-06-08T07:19:27Z (GMT). No. of bitstreams: 1 ntu-97-P94747017-1.pdf: 1034557 bytes, checksum: e40f53680c0f1a46490e4cecdc79cf13 (MD5) Previous issue date: 2008 | en |
| dc.description.tableofcontents | 口試委員審定書 i
誌謝 ii 中文摘要 iii 英文摘要 iv 目 錄 vi 圖目錄 viii 表目錄 ix 第一章 緒 論 1 第一節、研究背景與動機 1 第二節、研究目的 3 第三節、研究流程 3 第四節、研究範圍與限制 5 第二章 文 獻 探 討 7 第一節、軟體度量與分析 7 第二節、CMMI度量與分析流程領域 20 第三節、實務軟體和系統度量(PSM) 48 第三章 建構CMMI度量與分析流程領域的模式 60 第一節、建構CMMI度量與分析流程的活動 60 第二節、建構CMMI度量與分析流程元件的模式 64 第四章 個案企業導入實例研究 75 第一節、個案之簡介 75 第二節、導入CMMI成熟度第二級之作業項目與組織 76 第三節、度量與分析之落差分析與改善活動 79 第四節、導入CMMI的度量與分析規劃流程元件 86 第五節、導入CMMI的度量與分析結果流程元件 97 第六節、度量與分析流程全面推展及監督執行 99 第五章 結 論 與 建 議 102 第一節、結論 102 第二節、後續研究建議 103 參考文獻 104 | |
| dc.language.iso | zh-TW | |
| dc.subject | 成熟度 | zh_TW |
| dc.subject | 與分析 | zh_TW |
| dc.subject | 能力成熟度整合模式 | zh_TW |
| dc.subject | maturity level | en |
| dc.subject | Measurement an Analysis | en |
| dc.subject | CMMI | en |
| dc.title | 軟體組織之度量與分析流程模式研究--以A公司為例 | zh_TW |
| dc.title | The Study of Measurement and Analysis Process Model for Software Organization -- A Case Study on A Company | en |
| dc.type | Thesis | |
| dc.date.schoolyear | 96-2 | |
| dc.description.degree | 碩士 | |
| dc.contributor.oralexamcommittee | 黃世禎,孫雅麗 | |
| dc.subject.keyword | 能力成熟度整合模式,度,量,與分析,成熟度, | zh_TW |
| dc.subject.keyword | CMMI,Measurement an Analysis,maturity level, | en |
| dc.relation.page | 107 | |
| dc.rights.note | 未授權 | |
| dc.date.accepted | 2008-07-26 | |
| dc.contributor.author-college | 管理學院 | zh_TW |
| dc.contributor.author-dept | 資訊管理學研究所 | zh_TW |
| 顯示於系所單位： | 資訊管理學系 | |
文件中的檔案：
| 檔案 | 大小 | 格式 | |
|---|---|---|---|
| ntu-97-1.pdf 未授權公開取用 | 1.01 MB | Adobe PDF |
系統中的文件，除了特別指名其著作權條款之外，均受到著作權保護，並且保留所有的權利。