![]() |
|
以作者查詢圖書館館藏 、以作者查詢臺灣博碩士 、以作者查詢全國書目 、勘誤回報 、線上人數:18 、訪客IP:3.149.238.49
姓名 榮思哲(SZU-CHE JUNG) 查詢紙本館藏 畢業系所 資訊工程學系 論文名稱 以WBS為基礎之人力估算模型與功能點分析服務
(Function Point Analysis Services with a WBS-based Effort Estimation Model)相關論文 檔案 [Endnote RIS 格式]
[Bibtex 格式]
[相關文章]
[文章引用]
[完整記錄]
[館藏目錄]
[檢視]
[下載]
- 本電子論文使用權限為同意立即開放。
- 已達開放權限電子全文僅授權使用者為學術研究之目的,進行個人非營利性質之檢索、閱讀、列印。
- 請遵守中華民國著作權法之相關規定,切勿任意重製、散佈、改作、轉貼、播送,以免觸法。
摘要(中) 軟體專案人力的估算為專案管理中一項重要的活動。為了要在軟體專案的早期預測出所需要的人力,本研究提出從高階分工結構圖(WBS)估算人力的流程與方法以及一個結合WBS人力規劃因子與專案工作配置(Project Configuration)的基本因子之預估模型。專案可根據人力估算的流程分析專案的WBS,並使用預估模型更準確的估算出專案的人力。
本研究實做之專案配置人力估算服務和使用者案例功能點分析服務,可自動化使用者案例功能點計算與WBS人力的估算的過程,並可結合迴歸分析服務,有效的以專案的歷史資料來估算專案的人力。摘要(英) Software effort estimation is an important activity for effective project management. To predict the required effort in the early phase of the software project, this paper proposes(1)a WBS analysis process and method to estimate project effort from high level WBS and(2)an modified effort estimation model by utilizing four task assignment factors, team size, concurrency, intensity, fragmentation and one new factor, the WBS effort.
In the present study, these five factors are shown to improve the predictive ability of the original task assignment effort estimation model. For the data examined, our model is shown to have goodness of fit and quality of estimation superior to that of the original one.關鍵字(中) ★ 功能點
★ 軟體人力估算關鍵字(英) ★ project task assignment.function point
★ Software effort estimation論文目次 第一章、緒論 ............................................. 1
1.1 背景 ............................................. 1
1.2 動機 ............................................. 1
1.3 論文架構 ......................................... 2
第二章、背景知識介紹 ..................................... 3
2.1 分工結構圖(Work Breakdown Structure, WBS) ..... 3
2.2 軟體專案管理基礎 ................................. 4
2.3 軟體複雜度估算的方法 ............................. 5
2.4 傳統功能點分析 ................................... 7
2.5 MKII 功能點分析 .................................. 9
2.6 使用者案例功能點分析 ............................ 10
2.6.1 使用者案例的介紹 ........................... 10
2.6.2 UML 中的使用者案例圖介紹 ................... 11
2.6.3 使用者案例功能點分析方法介紹 ............... 12
2.7 建構成本預估模型(COCOMO) ...................... 17
2.8 專案配置人力估算介紹 ............................ 18
2.8.1 團隊人數(TEAM) ........................... 19
2.8.2 時程緊密度(INST) ......................... 19
2.8.3 人員併行程度介紹 (CONS) .................. 19
2.8.4 時程離散度介紹 (FRAG) .................... 20
2.8.5 估算模型介紹 ............................... 20
2.9 迴歸分析模型(Regression Model)................ 21
2.9.1 線性回歸分析模型(Linear Regression Model) 21
2.9.2 複迴歸分析模型(Multiple Regression Model) 22
第三章、人力估算模型與方法 .............................. 24
3.1 力估算模型 ...................................... 24
3.2 專案人力估算之流程與方法 ........................ 25
3.2.1 流程介紹 .................................... 26
3.2.2 MS Project 專案配置分析方法 ................. 28
第四章、系統設計與實做 .................................. 31
4.1 系統架構 ......................................... 31
4.1.1 使用者案例功能點分析服務子系統 ............. 33
4.1.2 專案配置人力估算服務子系統 ................. 34
第五章、案例分析 ........................................ 36
5.1 案例介紹 ........................................ 36
5.2 方法面案例分析 .................................. 37
5.2.1 定義專案主要工作項目 ....................... 37
5.2.2 確認全部主要工作項目是否都經過估算 ......... 38
5.2.3 計算時程單位個數 ........................... 38
5.2.4 計算團隊人數 ............................... 39
5.2.5 計算時程緊密度與人員並行度 ................. 39
5.2.6 計算時間離散度 ............................. 40
5.2.7 取得功能點與成員平均年資 ................... 41
5.2.8 估算工作項目人力 ........................... 42
5.2.9 計算軟體專案的人力 ......................... 43
5.3 系統面案例分析 .................................. 44
5.3.1 計算使用者案例功能點 ....................... 44
5.3.2 計算專案配置因子 ........................... 45
5.3.2 估算專案的人力 ............................. 46
5.3.3 蒐集專案歷史資料 ........................... 47
第六章、研究結果 ........................................ 48
6.1 線性迴歸模式契合度測試 .......................... 48
6.2 估算品質測試 .................................... 50
6.3 因子影響程度分析 ................................ 51
第七章、結論 ............................................ 53
7.1 貢獻 ............................................ 53
7.2 未來研究 ........................................ 54
參考文獻 ................................................ 55參考文獻 [1] DOD(USA), ” Department of Defense Handbook Work Breakdown Structure”, Chapter 1, page 4, 1998.
[2] K. Vinsen, D. Jamieson and P.G. Callender, “Use Case Estimation – The Devil is in the Detail”, 2004.
[3] Benediktsson and D. Dalcher, “Estimating size in incremental software development projects”, 2005.
[4] Richard E. Fairley, “Software Engineering Concepts”, New York: McGraw-hill, 1985.
[5] Stephen R. Schach, “Software Engineering”, Illinois: IRWIN, 1993.
[6] Roger S. Pressman, “Software Engineering”,New York: McGraw-hill, 2001.
[7] Halstead M. H., “Elements of Software Science”, Elsevier North-Holland, New York, 1977.
[8] 邱添枝, “需求導向軟體成本估計模式”, 1994.
[9] 林信惠等, “軟體專案管理”,台北: 智勝文化, 2002
[10] Steve McConnell, “微軟開發快速秘笈”, 台北: 華彩,1999.
[11] Ray Boehm, “Frequently Asked Questions”, IFPUG, 2002.
[12] N.E. Fenton and S.L. Peger, “Software Metrics. A Rigorous and Practical Approach”, Cambridge University Press, 1997.
[13] Capers Jones, “What are function points?”, www.spr.com.
[14] P.Grant Rule, “Using measures to understand requirements”, Software Measurement Services Ltd, 2001.
[15] Kirsten Ribu, “Estimating Object-Oriented Software Projects with Use Cases”, 2001.
[16] Alistair Cockburn, “Writing Eective Use Cases”, Addison-Wesley,2000.
[17] Charles Richter, “Designing Flexible Object-Oriented Systems with UML”, Macmillan Technical Publishing, 2001.
[18] Jacobsen, Christerson, and Overgaard, “Object-oriented Software Engineering: A Use Case-driven Approach”, Addison-Wesley, 1992.
[19] B. Boehm, “Software Engineering Economics”, Prentice-Hall, Inc., 1981.
[20] Q. Hu, R. Plant, and D. Hertz, “Software Cost Estimation Using Economic Production Models”, J. Management Information Systems, vol. 15, no. 1, pp. 143-163, 1998.
[21] Randy K. Smith, “An Empirical Study Using Task Assignment Patterns to Improve the Accuracy of Software Effort Estimation”, 2001.
[22] Watts S . Humphrey, “A Discipline for Software Engineering”, Addison-Wesley, 1995.
[23] T. DeMarco and T. Lister, “Peopleware: Productive Projects and Teams”, Dorset House, 1987.
[24] A. J. Albrecht, “Measuring application development productivity”, In Proc. Of the Join SHARE/GUIDE/IBM Application Development System, October 1979.
[25] Norman E. Fenton, “Software metrics: theory, tools and validation”, Software Engineering Journal, January 1990.
[26] Anandasivam Gopal, M.S. Krishnan, Tridas Mukhopadhyay, and Dennis R, “Goldenson. Mearurement Programs in Software Development: Determinants of Success”, IEEE Transactions on Software Engineering, Vol. 28, No. 9, September 2002.
[27] Norman E. Fenton, Shari Lawrence Pfleeger, “Software Metrics Second Edition”, PWS Publishing Company, 1997.
[28] C.R Symons, John Wiley and Sons, “Software Sizing and Estimating, MKII FPA”, 1991.
[29] Randy K. Smith , “An Empirical Study Using Task Assignment Patterns to Improve the Accuracy of Software Effort Estimation”, 2001.
[30] V. Basili and R. Reiter, “An Investigation of Human Factors in Software Development”, Computer, vol. 12, no. 12, pp. 21-38, 1979.
[31] F. Brooks, “The Mythical Man-Month”, Addison-Wesley, 1975.
[32] T. DeMarco and T. Lister, “Peopleware: Productive Projects and Teams”, Dorset House, 1987.
[33] L. Fried “Team Size and Productivity in Systems Development”, Information Systems Management, vol. 8, no. 3, pp. 27-41, 1991.
[34] V. Basili and R. Reiter, “An Investigation of Human Factors in Software Development”, Computer, vol. 12, no. 12, pp. 21-38, 1979.
[35] J. Cougar and H. Adelsberger, “Comparing Motivation of Programmers and Analysts in Different Socio/Political Environments: Austria Compared to the United States”, ComputerPersonnel, vol. 11, no. 4, pp. 13-17, 1988.指導教授 李允中(Yeun-Chung Lee) 審核日期 2007-7-16 推文 plurk
funp
live
udn
HD
myshare
netvibes
friend
youpush
delicious
baidu
網路書籤 Google bookmarks
del.icio.us
hemidemi
myshare