跳到主要內容

臺灣博碩士論文加值系統

(44.211.34.178) 您好!臺灣時間:2024/11/03 09:22
字體大小: 字級放大   字級縮小   預設字形  
回查詢結果 :::

詳目顯示

: 
twitterline
研究生:邊建國
研究生(外文):Cheng-Kou Bien
論文名稱:一個軟體專案管理的監督學習系統
論文名稱(外文):A Supervised Learning System for Software Project Management
指導教授:黃秋煌黃秋煌引用關係
指導教授(外文):Chua-Huang Huang
學位類別:碩士
校院名稱:逢甲大學
系所名稱:資訊工程所
學門:工程學門
學類:電資工程學類
論文種類:學術論文
論文出版年:2006
畢業學年度:94
語文別:英文
論文頁數:35
中文關鍵詞:軟體專案管理自動學習軟體能力成熟模式軟體成本估算軟體評量軟體工程
外文關鍵詞:Software MeasurementSoftware EngineeringSoftware Project ManagementCMMISupervise LearningSoftware Cost Estimation
相關次數:
  • 被引用被引用:1
  • 點閱點閱:555
  • 評分評分:
  • 下載下載:163
  • 收藏至我的研究室書目清單書目收藏:3
隨著時代的進步,凡事均講求效率,在人力成本越來越高的現代,如何有效率的掌控開發成本,是所有企業的一大課題,即便是軟體開發亦是如此。在早期,除了較具規模的軟體公司,軟體開發基本上是屬於單打獨鬥類型的,也就是說,開發專案並不能有效的被掌控及稽核,導致專案無法照預定規劃時間進行。雖然目前有許多專案預估的模式,可提供專案進行時之時程預估,但是,這些模式並不能一體適用於各個不同的企業,因為不同的事業體系,其所應該強調的事項均有所不同,若是勉強套用一樣的預估模式,將造成預估誤差率提高,因而增加企業成本。所以在我們的研究中,我們提出一個軟體專案管理的監督學習系統,此架構可經由學習、累積企業開發專案之過程經驗,進而在預估新專案時,提供實用之建議,提高專案預估之準確率,進而達到軟體專案管理的監督。其主要是利用企業所累積的經驗,將其經驗利用分析結果,而達到對將要進行之專案進行預估,以達到經驗傳承,並且可以依照預估結果進行監測,最終目標是達成精準的軟體開發專案監督及管理。
Efficiency has gained tremendous attention since technology started to develop. With the continuously increased costs on manpower, effective control of development costs has become an essential lesson that all enterprises have to learn, and software development is not excluded. In early times, software development projects were mostly carried out by individuals, if not by organized software companies; that is, those projects were not managed and estimated properly so that they could not follow the schedules planned. Nowadays there are diverse methods to preset schedules for projects, but they do not always appropriately meet the enterprises’ needs due to different focuses of companies. Estimating projects with one single approach will lead to marked inaccuracy and consequent increase of costs. Therefore, a supervised learning system for software project management is proposed in the study. Based on previous experiences on learning and developments, the system could provide practical suggestions and valid estimation for new projects so as to precisely secure the progress and accomplishment. In general, the system aims to foster more precise estimation and efficient management for software projects by means of accumulating experiences and analyzing collected results.
1 Introduction . . . . . . . . . . . . . . . . . . . 1
2 Related Works . . . . . . . . . . . . . . . . . . . 3
2.1 Software Project Management . . . . . . . . . . 3
2.2 Software Estimation . . . . . . . . . . . . . . 5
3 Supervised Learning of Software Project Management .8
3.1 Estimation of Project Schedule . . . . . . . . 8
3.1.1 Adequate Programming Methods . . . . . . . 9
3.1.2 Learning from Historic Data . . . . . . . . 10
3.2 Software Measurement . . . . . . . . . . . . . 11
3.3 Integration with Management Mechanisms . . . . 12
4 System Implementation . . . . . . . . . . . . . . . 15
4.1 Creating a Project . . . . . . . . . . . . . . 15
4.2 Estimation of Working Hours . . . . . . . . . . 17
4.3 Progress Monitoring . . . . . . . . . . . . . . 17
5 Experimental Results . . . . . . . . . . . . . . . 21
5.1 Ideal Condition . . . . . . . . . . . . . . . . 21
5.2 Actual Condition . . . . . . . . . . . . . . . 22
5.3 Special Condition . . . . . . . . . . . . . . . 23
6 Conclusions . . . . . . . . . . . . . . . . . . . . 25
[1] Managing Successful Projects with PRINCE2 (PRINCE Guidance), The Stationery Office Books, 2002.
[2] A. Albrecht. Measuring application development productivity. 1979.
[3] A. Albrecht and J. Gaffney. Software function, source lines of code, and development effort predication: a software science validation. IEEE Transactions on
Software Engineering, SE-9(6):639–648, 1983.
[4] E. Horowitz C. Westland R. Madachy B. Boehm, B. Clark and R. Selby. Cost models for future software life cycle processes: Cocomo 2.0. Software Process and Product Measurement, Annals of software Engineering Special Volume,
1995.
[5] J. W. Bailey and V. R. Basili. A meta-model for software development resource expenditures. In Proceedings of 5th International Conference Software Engineering, pages 107–116, 1981.
[6] R. Betteridge. Successful experience of using function point to estimate project costs early in the life cycle. Information and Software Technology, pages 655–658, 1992.
[7] B.W. Boehm. Software Engineering Economics. Prentice-Hall, 1981.
[8] T. Crowther. PRINCE2 Process Model: A Comprehensive Graphical View of All the Standard PRINCE2 Products and Processes, Key Skills Ltd, 2004.
[9] A. Clouse D. Ahern and R. Turner. CMMI Distilled, AddisonWesley, 2001.
[10] R. B. Gurner D. V. Ferens. An evaluation of three function point models for estimation of software effort. IEEE National Aerospace and Electronics Conference, pages 625–642, 1992.
[11] J.L.F. Dekerf. APL and Halstead’s theory of software metrics. APL 81 Conf. Proc. ACM, 12:89–93, 1981.
[12] N. B. Ebrahimi. How to improve the calibration of cost models. IEEE Transactions on Software Engineering, 25(1):136–140, 1999.
[13] The Standish Group. Chaos report, 2004. http://www.standish.com.
[14] M. H. Halstead. Elements of Software Science. Elsevier North-Holland, 1977.
[15] IEEE/EIA 12207.0-1996. IEEE/EIA Standard: Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology– Software Life Cycle Processes, 1996.
[16] IEEE/EIA 12207.1-1997. IEEE/EIA Standard: Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology–Software Life Cycle Processes–Life cycle data, 1997.
[17] IEEE/EIA 12207.2-1997. IEEE/EIA Standard: Industry Implementation of International Standard ISO/IEC 12207:1995 Standard for Information Technology–Software Life Cycle Processes–Implementation considerations, 1997.
[18] Project Management Institute. A Guide to the Project Management Body of Knowledge, third edition, Project Management Institute, 2004.
[19] ISO 9000:2000. Quality Management Systems Fundamentals and Vocabulary Installation and Servicing, 2000.
[20] ISO 9001:2000. Quality Management Systems Requirements, 2000.
[21] ISO 9004:2000. Quality Management Systems Guidelines for Performance Improvement, 2000.
[22] D. R. Jeffery and G. Low. Function point in the estimation and evaluation of the software process. IEEE Transactions on Software Engineering, 16(1):64–71, 1990.
[23] Jones and Capers. Programming Productivity. McGraw-Hill, 1986.
[24] H. Kerzner. Project Management: A Systems Approach to Planning, Scheduling, and Controlling, Eighth Edition. Wiley, 2003.
[25] J. E. Matson, B. E. Barrett, and J. M. Mellichamp. Software development cost estimation using function point. IEEE Transactions on Software Engineering, 20(4):275–287, 1994.
[26] L. H. Putnam. A general empirical solution to the macro software sizing problem. IEEE Transactions on Software Engineering, SE-4:345–361, 1978.
[27] H. A. Rubin. Macro-estimation of software development parameters: the estimacs system. SOFTFAIR Software Development: Tools, Techniques, and Alternatives, New York: IEEE, pages 109–118, 1983.
[28] H.E. Dunsmore S.D. Conte and V.Y. Shen. Software engineering metrics and models. Benjamin/Cummings, Menlo Park, CA, 1986.
[29] C. P. Smith. A software science analysis of programming size. In Proceedings of the ACM National Computer Conference, pages 179–185, 1980.
[30] CMMI Product Team. CMMI-SE/SW/IPPD/SS,V1.1, Carnegie Mellon-Software Engineering Institute, Pittsburgh, PA, 2002.
QRCODE
 
 
 
 
 
                                                                                                                                                                                                                                                                                                                                                                                                               
第一頁 上一頁 下一頁 最後一頁 top