工作量預估在軟體專案管理的領域中，是一個非常熱門的議題，各種相關的議題、方法及模式相繼被提出來。然而，在軟體流程改善的領域中，卻鮮少有研究探討導入過程中所需的工作量。如何精準地預估工作量對於軟體流程改善的規劃、監控與成功與否，是一個非常重要的關鍵因素。若是預估的工作量低於實際工作量，則會造成人力的短缺與專案延遲的情形；若是預估太多，則會造成資源的浪費。近年來，國內資訊服務產業追求改善軟體開發流程品質的意願漸漸昇高，再加上能力成熟度整合模式(Capability Maturity Model Integration, CMMI)已成為全球普及的流程改善模式，使得國內資訊服務組織相繼導入CMMI，期望能提昇達到改善軟體產品品質與組織的生產力與競爭力。為了幫助國內有意願導入CMMI的組織能客觀的預估整個導入過程所需要的工作量。本論文的主要目的是經由文獻探討提出較正規的工作量預估方法探討國內CMMI導入工作量。
本研究收集國內15家參與「經濟部工業局94年度提昇資訊軟體品質CMMI計畫」導入組織所撰寫的計畫書與工作報告書，並經由廣泛的文獻探討與分析所收集到的資料，提出了三個正規工作量預估的方法：比率預估方法、迴歸方法與模組化WBS方法。本論文亦使用所提出的三個工作量預估方法來探討國內這15家導入CMMI廠商之所預估工作量與實際投入工作量的合理性。

Effort estimation has been a hot issue in the software project management, so many topics, methods and theories were proposed to help project managers predict the required effort. However, to date there is no research work on estimating the implementation effort of the software process improvement activities. That how to accurately estimate the effort is a key factor to the success of the adoption of software process improvement program. If the estimated effort is much lower than the required effort, it will cause the shortage of human resources and the delay of the software delivery. If the estimated effort is much higher than the required effort, it will also waste the inputted resources. In recent years, domestic software service industry has more interests in improving its software development process. As Capability Maturity Model Integration (CMMI) has become a widely-adopted process improvement model worldwide, many domestic software service organizations are adopting CMMI for their software process improvement successively. In order to help these organizations objectively and precisely estimate the required effort for their CMMI adoption, this thesis aims to propose the formal effort estimation methods for the CMMI adoption program.
We collected the software process improvement plans and the working reports from domestic 15 companies which adopted CMMI for their software process improvement program in 2005. Based on the extensive literature study and the analysis of the collected data, this thesis proposes three formal effort estimation methods, namely ratio model, regression model and modularized WBS model. This thesis also applied these three effort estimation methods to analyze the reasonness of the estimated and actual efforts in domestic software organizations which adopted the CMMI software process improvement.

中文部分
[1] 林信惠、黃明祥、王文良，「軟體專案管理」，智勝文化，2005。
[2] 許兆榕，「多因子資料分群對軟體工作量預估值精確性影響之研究」，碩士論文，國立台灣科技大學，民國九十四年。
[3] 楊玟惠，「國內軟體專案預估流程之調適與軟體工具開發」，碩士論文，國立台灣科技大學，民國九十三年。
[4] 「94年度提升資訊軟體品質(CMMI)計畫—技術導入作業要點與規範」，http://210.71.186.144/big5/cmmi/htm/doc-cmmi/01-0906.doc。
[5] 涂順章，「企業建立QS9000品質保證制度之實證研究(以汽車零組件業為例)」，碩士論文，私立原智大學工業工程研究所，民國八十六年。
[6] 胡佑長，「CMMI評鑑導入進入實作期」，軟體產業通訊，NOV. 2003 Vol.54
[7] 邱皓政，「量化研究法(一)：研究設計與資料處理」，雙葉書廊，2005
[8] 邱皓政，「量化研究法(二)：統計原理與分析技術 修訂版」，雙葉書廊，2005
[9] 郭怡岑，「組織特性與投入資源對CMMI流程改善效益影響之研究」，碩士論文，國立台灣科技大學，民國九十五年。
英文部分
[10] Boehm, W. (1976). Software Engineering. IEEE Transactions on Computers 25 (12), 1226-1241.
[11] Boehm, B. W. (1981). Software Engineering Economics. Englewood Cliffs, N.J, Prentice-Hall
[12] Boehm, B. W. (2000). Software Cost Estimation with COCOMO Ⅱ, Prentice Hall PTR
[13] Boehm, B. W., Abts, C. & Chulani, S.(2000). Software development cost estimation approaches-a survey. Annals of software Engineering 10(1), 177-205
[14] Butler, k. (1995). The economics benefits of software process improvement. CrossTalk(July), 14-17
[15] Conte, S.D., Dunsmore, H.E. and Shen, V.Y. (1986) Software engineering metrics and models Benjamin/Cummings., Menlo Park, Calif
[16] DeMarcro, T. (1982) Controlling software Projects: management, measurement & estimation. Foreword by Barry w. Boehm. Yourdon Press, New York
[17] El-Eman. K., Fusaro, P., Smith,B, (1999). Success factor and barriers for software process improvement. Better software practice for business benefit:principles and experience. IEEE Computer Society.
[18] Fairley, R.E. (1992) Recent advances in software estimation techniques, International Conference on Software Engineering , Software Eng. Manage. Associates Woodland Park CO USA, ACM New York NY USA
[19] Goldenson, D.R. & Herbsleb, J. (1995). After the Appraisal: A Systematic Survey of Process Improvement, its Benefits, and Factors that Influence Success. Technical Report, CMU/SEI-95-TR-009.
[20] Ian Sommerville (1996) Software Engineering Addison-Wesley Pub. Co.
[21] J. Hill, L.C. Thomas, D.E. Allen. (2000). Experts’ estimates of task duration in software develop projects International Journal of Project Management,18,2000
[22] K. Moløkken-Østvold and M. Jørgensen (2003). A Review of Surveys on Software Effort Estimation. Proc. 2003 ACE-IEEE Int’l Symp. Empirical Software Eng.(ISESE 2003), 220-230
[23] Kitchenham, B.A. (1996). Software metrics : measurement for software process improvement. NCC Blackwell, Oxford
[24] M. Jørgensen (2004). A Review of Studies on Expert Estimation of software Development Effort. J. Systems and Software 70(1-2), 37-60
[25] Steve McConnell (2006). Software Estimation: Demystifying the Black Art. Microsoft Press
[26] Mahmood Niazi, David Wilson, Didar Zowghi (2005). A maturity model for the implementation of software process improvement: an empirical study. J. Systems and Software 74, 155-172
[27] Pitterman, B. (2000). Telcordia Technologies: the journey to high maturity. IEEE Software 17(4), 89-96.
[28] Rainer, A., Hall, T., (2002). Key success factors for implementing software process improvement: a maturity-based analysis. Journal of Systems and Software(62), 71-84
[29] SEI. (1993). Capability Maturity Model for software, V1.1, CMU/SEI-93-TR-24.
[30] SEI. (2002). Capability Maturity Model Integration (CMMI-SE/SW/IPPD, V1.1, Staged). CMU/SEI-2002-TR-004.
[31] SEI. (2004). Process Maturity Profile. SCAMPI Appraisal Results, SEI, CMU.
[32] SEI. (2005).Process Maturity Profile. SCAMPI v1.1 Class A Appraisal Results.
[33] Shepperd, M. and Schofield, C. (1997) Estimating software project effort using ananlogies. IEEE Transactions on Software Engineering(23:11) ,PP736-743
[34] Shepperd, M. & Cartwright Michelle (2001) Predict with sparse Data. IEEE Transactions on software engineering, vol.27 No11 ,NOVEMBER.
[35] Symons and C. R. (1988) Function point analysis: Difficulties and improvements. IEEE Transactions On Software Engineering, Vo1. 14 pp.2-11
[36] Stelzer, D., Werner, M. (1999) Success factors of organizational change in software process improvement. Software Process Improvement and practice 4(4).
[37] Steve McConnell, (2006), Software Estimation:Demystifying the Black Art, Microsoft Press
[38] Yamamura, G. (1999). Process improvement satisfies employees. IEEE Software 16(5), 83-85.