為提升國內軟體專案生產力和品質，建立度量與分析的機制，本研究參考能力成熟度整合模式(Capability Maturity Model Integration, CMMI)之度量與分析流程領域作為指引，結合GQM (Goal-Question-Metric)及PSM (Practical Software & Systems Measurement)的度量方法論，發展一套提問式驅動度量與分析流程規劃法，稱為QMAP (Questions driven- Measurement & Analysis Process Planning)—運用5W1H (Why, Who, When, What, Where & How) 提問方式，有系統地依據CMMI度量與分析流程的要求，找出軟體專案的成功因素，逐步建立組織內部的度量與分析流程的基準。首先，以某公司之個案情境為例進行背景分析、目標分析和流程分析，接著以使用分析—使用案例及其描述之資訊需求，建議整合運用PSM Insight, MS Project及IBM Rational ClearQuest等工具來支援軟體專案度量與分析流程之自動化。經工具系統之實作展示，再以自我評鑑來檢視QMAP於CMMI度量與分析流程之目標及執行方法的符合程度，而部分未達成的項目則作為未來研究之方向。

This research proposes a method called QMAP (Questions driven- Measurement and Analysis Process Planning) in order to meet goals and practices in Capability Maturity Model Integration (CMMI). QMAP is about 5W1H questions which begin with why, who, when, what, where and how. Before answering the 5W1H questions, we start with background analysis, goal analysis, and process analysis based on a sample company’s management context. Use Cases are then described as the formal information requirements of the MA process support system. In the implementation, we suggest to integrate some tools, such as MS Project, PSM Insight, and IBM Rational ClearQuest, to facilitate the measurement data collection and analysis activities during the software project development. After illustrating the implementation prototype, a checklist for self-appraisal is presented to identify the compliances of CMMI goals and practices, and the incomplete parts for future research extension.

[1]CNET Taiwan，2003-12-31，「政府推動服務水準委外模式」，新聞專區 : 企業軟體。http://taiwan.cnet.com/news/software/0,2000064574,20086728,00.htm
[2]工商時報，2002-08-08，「21家廠商與資策會簽技術合作協議書」。
[3]方弘信，2003，水產飼料集團管理資訊需求規劃，國立台灣海洋大學水產養殖學系碩士論文。
[4]朱明強，2002，以企業樣版為基礎之需求分析架構，國立政治大學資訊管理學系碩士論文。
[5]宋珍儀，2001，資訊需求分析架構之研究—以網路基金下單應用為例，國立政治大學資訊管理學系碩士論文。
[6]林信惠、黃明祥、王文良，2002，軟體專案管理，台北市：智勝文化。
[7]胡佑長，2000，「淺談軟體品保與國際品保標準」，軟體產業通訊，27期；軟體工業生產力提升特輯，台北市：中華民國資訊軟體協會：13~23頁。
[8]梁定澎，1997，「資訊管理研究方法總論」，資訊管理學報，資訊管理實證研究方法討論會特刊，第四卷第一期：1 - 7頁。
[9]黃世禛，2003，「軟體工程度量簡介」，軟體產業通訊，51期：50~58頁。
[10]黃鈺峰、趙光正譯，Phillippe Kruchten著，2002，Rational統一流程入門，第二版，台北縣：維科。
[11]曾淑峰審訂、黃建欣等校譯，Wendy Boggs & Michael Boggs著，2002，以Rational Rose 2002精通UML，台北縣：維科。
[12]資訊工業策進會資訊系統實驗室，2002，CMMI導入指引V1.0，台北市：資策會資系室。
[13]資訊工業策進會資訊系統實驗室譯，美國卡內基美隆大學軟體工程學院著，2002，能力成熟度整合模式，V1.02，台北市：資策會資系室。
[14]資策會，2004-02-02，CMMI技術服務網。http://www.cmmi.org.tw
[15]電子時報，2002-12-06，「CMMI 2003年全面取代CMM」。
[16]Abran, A. et al. edit. Guide to the software engineering body of knowledge, Angela Burgess, May 2001. http://www.swebok.org/
[17]Basili, V. R. and Rombach, H. D. "The TAME Project: Towards Improvement- Oriented Software Environments," IEEE Transactions on Software Engineering (14) 1988, pp: 758-773.
[18]Booch, G., Jacobson, I. and Rumbaugh, J. The Unified Software Development Process, Addison-Wesley, Inc., 1999.
[19]Booch, G., Rumbaugh, J. and Jacobson, I. The Unified Modeling Language, Addison-Wesley, Inc., 1999.
[20]Carnegie Mellon University Software Engineering Institute. Capability Maturity Model Integration, Version 1.1, CMU/SEI-2002-TR-001.
[21]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. http://www.sei.cmu.edu/cmmi/presentations/euro-sepg-tutorial/
[22]Chrissis, M. B., Konrad, M. and Shrum, S. CMMI: Guidelines for Process Integration and Product Improvement, Addison-Wesley, 2003.
[23]Grady, R. B. and Hewlett-Packard. "Successfully Applying Software Metrics," IEEE Computer (27:9) 1994, pp: 18-25.
[24]IBM Rational Software Corporation. Rational ClearQuest, CD-ROM, IBM Rational Software Product, 2003.
[25]IBM Rational Software Corporation. Rational Unified Process, CD-ROM, IBM Rational Software Product, 2003.
[26]Jalote, P. CMM in Practice: processes for executing software projects at Infosys, Addison-Wesley Longman, 2002.
[27]Jalote, P. Software Project Management in Practice, Addison-Wesley Longman, 2002.
[28]Jethani, K. "Continuous Process Improvement," SPIN-Taiwan Conference, Institute for Information Industry, Taiwan, R.O.C., 2003.
[29]Kuntzmann, A. and Kruchten, P. The IBM Rational Unified Process: An Enabler for Higher Process Maturity- White Papers, IBM Rational, 2001. http://www3.software.ibm.com/ibmdl/pub/software/rational/web/whitepapers/
[30]McGowan, C. L. and Bohner, S. "Model- based process assessment," in Proceedings of the 15th International Conference on Software Engineering, IEEE Computer Society, 1993.
[31]Offen, R. J. and Jeffery, R. "Establishing Software Measurement Program," IEEE Software (14:2) 1997, pp:45-53.
[32]Pfleeger, S. L. and McGowan, C. L. "Software Metrics in a Process Maturity Framework," The Journal of Systems and Software (12) 1990, pp: 255-261.
[33]Pfleeger, S. L. "Maturity, Models, and Goals: How to Build a Metrics Plan," The Journal of Systems and Software (31:2) 1995, pp: 143-155.
[34]Practical Software and Systems Measurements (PSM) Homepage 2003. http://www.psmsc.com
[35]Scott-Morton, M. S. "The State of the Art of Research," The Information Systems Research, Poston: Harvard Business School Press, 1984, pp.13-41。
[36]Software Engineering Institute (SEI) Homepage 2003. http://www.sei.cmu.edu/
[37]Tseng, Shu-Feng and Lin, Chien-Yu. "Information Requirement Planning for Measurement and Analysis in CMMI," The Asia SEPGSM 2003 Conference, Taipei.
[38]Whitney, R. M. "How to Implement Process Improvement to Reach CMMI Maturity Level 2," SPIN-Taiwan Conference, Institute for Information Industry, Taiwan, R.O.C., 2002.
[39]The Zachman Institute for Framework Advancement (ZIFA) Homepage 2003. http://www.zifa.com/