軟體開發工作量(Effort)、成本與時間預估值的精確性是影響軟體開發標案報價、資源分配與時程安排等重要專案管理工作項目的關鍵因素，亦會進一步影響到專案是否能準時交付、組織能否獲利，以及開發完成軟體品質的好壞。雖然國際上軟體工程專家們已經提出了許多軟體專案工作量、成本與時間的預估模式，而在軟體商業市場上也可以買到一些軟體專案預估的軟體工具，然而目前這些模式或所開發的軟體工具卻一直未被國內軟體產業所採用，探究其原因，主要是這些以國外歷史資料所建置的軟體專案預估模式，未經國內軟體歷史資料的調適是無法直接拿來使用的。
因此基於上述的問題，本研究的主要內容是提出適合國內軟體產業環境之軟體專案預估流程調適的原則，並藉以制訂『軟體專案預估流程標準作業程序』，並開發一軟體專案預估工具（Software Project Estimation Tool, SPET），配合所規劃之軟體度量資料儲藏所(Software Measurement Repository)內所收集的國內軟體歷史專案資料，以幫助國內軟體廠商建立正規的軟體專案預估流程與方法，以提升軟體工作量、成本與時間預估值的精確性。

The accuracy of the estimates of software effort, cost and duration is a key factor to affecting the efficiency of software project management activities such as software project bidding, resource allocation and scheduling. Moreover, it also affects whether the software product can be delivered on time, within budget and on schedule, and even the quality of the delivered software product. Many software engineering researchers worldwide have proposed numerous methods, techniques or models for estimating the software effort, cost and duration. Meanwhile, several software tools have also been developed and available on market. However, domestic software industries have never adopted these models or tools. The most important reason is that existing software project estimation models and tools are all based on the historical software project data overseas. Apparently, they can not meet the needs of the domestic software organizations if they are not calibrated based on the domestically historical software project data.
To address the above problem, this thesis first presents the tailoring principles of software project estimation and then defines the standard operation procedures for the software project estimation process. Accordingly an automatic tool called Software Project Estimation Tool (SPET) is developed. With the embedded domestic software measurement repository, SPET can help the software companies in Taiwan establish a formal software project estimation process and method, and thus improve the accuracies of the estimates of the software effort, cost and duration.

[1]張鴻林，「動態軟體工作量估算模式之研究」，碩士論文，國立臺灣科技大學資訊管理研究所，2001。
[2]楊連瑛，「台灣訂製型軟體成本估算模式之研究」，碩士論文，國立交通大學資訊管理研究所，1994。
[3]行政院主計處，機關委託資訊服務廠商評選及計費辦法，民國88年5月。
[4]田俊國(51CMM.COM原創)「應用PERT進行專案工期估計」，http://www.51cmm.com/ProjectManage/No025.htm
[5]林信惠、黃明祥、王文良，「軟體專案管理」，智勝文化，2002。
[6]許光華、何文榮，“專案管理－理論與實務”，華泰書局，民國87年。
[7]孫文祥，「談軟體專案失敗的六大關鍵」，民國八十九年。
[8]Alain Abran and Pierre N. Robillard, “Function Points Analysis: An Empirical Study of Its Measurement Processes”, IEEE Trans. Software Eng. vol. 22, no.12, Dec. 1996.
[9]Barry W. Boehm, “Software engineering economics”, Englewood cliff, NJ: Prentice-Hall, 1981.
[10]Barry W. Boehm, “Software engineering economics”, IEEE Transactions on Software Engineering, vol.SE-10, pp.4-21., Jan. 1984.
[11]Barry W. Boehm, Chris Abts, “Software Development Cost Estimation Approaches – A Survey”, University of Southern California, Los Angeles, Sunita Chulani , 1988.
[12]Barry W. Boehm, Ellis Horowitz, Ray Madachy, Donald Reifer, Bradford K. Clark, Bert Steece, A. Winsor Brown, Sunita Chulani, Chris Abts, “Software Cost Estimation with Cocomo II”, USC Center for Software Engineering , 2000.
[13]Barry W. Boehm, et al. “The COCOMO 2.0 Software Cost Estimation Model”, American Programmer, pp.2-17. , July. 1996.
[14]L. C. Briand, K. E. Eman, D. Surmann, I. Wieczorek, K. D. Maxwell, “An Assessment and Comparison of Common Software Cost Estimation Modeling Technique” ICSE ’99 Los Angeles CA, pp.313-322., 1999.
[15]S. D. Conte, et al. “Software Engineering Metrics and Models” ,Menlo Park, CA: Benjamin/Cummings, 1986.
[16]N. E. Fenton, Software Metrics: A Rigorous Approach. London: Chapman & Hall, 1991.
[17]J. R. Herd, et al., “Software Cost Estimation study-study results”, Final Technical Report, RADC-TR-77-220, Doty Associates INC., Rockvillem MD, Jun. 1977.
[18]Hareton Leung Zhang Fan, “Software Cost Estimation”, Department of Computing , The Hong Kong Polytechnic University, 2001.
[19]P. R. Hill, “Software Development Projects in government, performances, practices and predictions”, International Software Benchmarking Standard Group, 47 pages, 2004.
[20]John McGarry, David Card, Cheryl Jones, Beth Layman, Elizabeth Clark, Joseph Dean, Fred Hall, “Practical Software Measurement”, Addison-Wesley, pp. 85-112. , 2001.
[21]Kevin Strike, “Software Cost Estimation with Incomplete Data”, IEEE Transactions On Software Engineering, Vol. 27, No. 10, pp. 890 , 2001.
[22]E. A. Nelson, “Management Handbook for the Estimation of Computer Programming Costs”, AD-A648750, System Development Corp., Oct. 31. 1966.
[23]L. H. Putnam, “A General Empirical Solution to the Macro Software Sizing Problem”, IEEE Trans. Software Engineering, Vol. SE-4, pp. 345-361, Apr. 1978.
[24]Peters, K. Peters, “Software Project Estimation”, Software Productivity Center Inc, 15 pages, 1999.
[25]R. L. Glass, “Facts and Fallacies of Software Engineering”, Addison-Wesley, 2002.
[26]R. D. Stutzke, “Software Estimating Technology: A Survey”, Science Applications International Corp, 1996.
[27]Sarah Jane Delany, Dublin Pádraig Cunningham, “The Application of Case-Based Reasoning to Early Software Project Cost Estimation and Risk Assessment”, Department of Computer Science DIT Kevin Street, Department of Computer Science Trinity College Dublin, 2000.
[28]L. Sommerville, “Software Engineering”, Forth Edition, Addision – Wesley, 1995.
[29]R. W. Wolverton, “The Cost of Developing Large-Scale Software,” IEEE Transcations on Computers, C-23, pp.615-636., Jun. 1974.
[30]Xuemei Zhang, Hoang Pham, “An analysis of factors affecting software reliability”, The Journal of Systems and Software, Elsevier Science, pp. 263-272. , 2000.