(3.238.96.184) 您好!臺灣時間:2021/05/08 04:32
字體大小: 字級放大   字級縮小   預設字形  
回查詢結果

詳目顯示:::

我願授權國圖
: 
twitterline
研究生:吳純慧
研究生(外文):Chuen-hwei Wu
論文名稱:軟體程序成熟度與專案績效
論文名稱(外文):Software Project Process Management Maturity and
指導教授:陳鴻基陳鴻基引用關係江俊毅江俊毅引用關係
指導教授(外文):Houn-Gee ChenJames J. Jiang
學位類別:碩士
校院名稱:國立中正大學
系所名稱:資訊管理學系
學門:電算機學門
學類:電算機一般學類
論文種類:學術論文
論文出版年:2001
畢業學年度:89
語文別:英文
論文頁數:76
中文關鍵詞:軟體程序成熟度專案績效專案風險軟體產能成熟度模式
外文關鍵詞:Software Project Process Management MaturityProject Performanceproject riskCapability Maturity Model
相關次數:
  • 被引用被引用:9
  • 點閱點閱:225
  • 評分評分:系統版面圖檔系統版面圖檔系統版面圖檔系統版面圖檔系統版面圖檔
  • 下載下載:0
  • 收藏至我的研究室書目清單書目收藏:7
雖然在資訊系統開發中運用了許多的開發工具、軟體工程技術與管理方法, 資訊系統專案仍因無法達成專案目標並有效地控制時程與預算,而有相當高的失敗率。而缺乏適當地軟體發開程序規劃是資訊系統專案高失敗率的主要原因之一。為有效地管理資訊系統專案的開發程序,提升軟體品質,進而增加專案成功的機會,SEI制定了一套軟體發展程序架構,與衡量軟體程序成熟度的方法,稱為「軟體產能成熟度模式」(Capability Maturity Model)。CMM將一個組織的軟體程序成熟度界定為五個循序漸進的層級,每個層級代表著不同階段的軟體程序成熟度。
在相關文獻中說明專案風險降低了專案績效,也發現透過一些管理實務可降低專案風險對專案績效的負面影響。本研究的目的是檢驗軟體程序管理成熟度對專案風險與專案績效的關係。
本研究以台灣資訊經理人協會與資訊軟體協會的資訊部門經理為對象,採郵寄問卷方式來了解國內軟體程序成熟度的概況。經過問卷資料的分析與研究假設的檢定之後,具體的結果簡述如下:
1.驗證了專案風險對專案績效有著負面的顯著影響。
2.軟體程序管理成熟度對專案績效有顯著的影響。
3.組織的軟體程序管理如果愈成熟將會降低專案風險對專案績效的不利影響。
4.經過「軟體工業五年發展計畫」的執行,台灣地區的軟體產業之軟體成熟度,在整體上有逐步提升的趨勢。相較於1996年謝國棟之研究,軟體成熟度呈現了8%的成長。
Even after a wide variety of tools, technologies, and management methods are poured into information systems (IS) development, IS projects are still plagued by unmet user’s requirements, schedules, and budgets. Many researchers and practitioners have argued inadequate software development process planning is a critical factor accounting for this high IS project failure rates. The Capability Maturity Model (CMM) was introduced by Software Engineering Institute as a guideline for increasing project maturity in the software development process. CMM categorizes organization’s software development process into five maturity levels. Each level presents a different stage of software process management maturity.
The purpose of this study is to examine the implication of the software process management maturity on project risks and project performance. A survey was conducted to the corporate IS managers in Taiwan.
The primary results are as follows:
1. Project risk is negatively associated with project performance.
2. Maturity level is positively associated with project performance.
3. Maturity level is negatively associated with project risk.
4. This research was conducted right after the Software Industry Five-year Development Plan was completely implemented. The comparison of the software process management maturity profiles before and after the plan showed an 8% increase in maturity level.
Chapter 1 Introduction1
1.1 Background
1.2 Motivation
1.3 Purposes
1.4 Research Scope and Subjects
1.5 Proposal Contents and Organization
Chapter 2 Literature review
2.1 Software Process Management Maturity
2.2 Project Performance
2.3 Project Risk
2.4 The Process Management Theory
Chapter 3 Research Model and Methodology
3.1 Research Model
3.2 Definition of Constructs
3.3 Research Hypotheses
3.4 Research Methodology
Chapter 4 Data Analysis
4.1 External Validity
4.2 Measures for Constructs
4.3 Intercorrelation Among Constructs
4.4 Results
Chapter 5 Conclusion
5.1 Discussion
5.2 Current Status in Taiwan
5.3 Management Implications
5.4 Research Limitations
5.5 Contributions
References
Appendices
Alter, E. “Implementation Risk Analysis,” TIMS Studies in Management Sciences (13:2), 1979, pp. 103-119.
Anderson, J.C. and Gerbing, D.W. “Structural equation modeling in practice: A review and recommended two-step approach,” Psychological Bulletin (103: 3), 1988, pp. 411-423.
Apte, U., Sankar, S.C., Takur, M. and Turner, E.J. “Reusability-based Strategy for Development of Information Systems,” MIS Quarterly (14:4), 1990, pp. 421-433.
Avritzer, A. and Weyuker, E.J. “Investigating Metric for Architectural Assessment,” Proc. Fifth International Symposium on Software Metric, Bethesda, Md., Nov. 1998, pp.4-10.
Bandinelli, S. and Fuggetta, A. “Modeling and Improving an Industrial Software Process,” IEEE Transaction on Software Engineering (21:5), 1995, pp. 440-454.
Barki, H., Rivard, S., and Talbot, J., “Toward an assessment of software development risk,” Journal of Management Information Systems (10: 2), 1993, pp. 203-223.
Beath, C.M. “Managing the User Relationship in Management Information Systems Projects: A Transaction Governance Approach,” unpublished Ph.D. dissertation, Graduate School of Management, UCLA, Los Angeles, CA, Summer 1986.
Bedeian, A.G. “Management,” Dryden Press, 1993, pp.41-43.
Boehm, B.W. “Software Risk Management: Principles and Practices,” IEEE Software, Jan. 1991, pp.32-41.
Boehm, B.W. “Tutorial Volume: Software Risk Management,” IEEE Computer Society, 1989.
Brown, K.A., Klastorin, T.D. and Valluzzi, J.L. “Project Performance and the Liability of Group Harmony,” IEEE Transactions on Engineering Management (37:2), 1990, pp.117-125.
Butler, K.L. “The economic benefits of software process improvement,” Cross Talk, July 1995, pp. 14-17.
Charette, R.N. “Software Engineering Risk Analysis and Management,” Inter-text, New York, 1989.
Cheiarie, A. M. “Simulation in Support of CMM-based Process Improvement,” The Journal of Systems and Software (46), 1999, pp. 107-112.
Chen Y.S. “The Relationships Between Organizational Characteristics, Information System Maturity, IS Department Characteristics and Software Process Maturity,” unpublished Master dissertation, Dept. of MIS, National Chung Cheng University, 1999.
Chen, S.H. “The relationship of TQM-based Organizational Culture and Software Process Maturity,” unpublished Master dissertation, Dept. of MIS, National Chung Cheng University, 2000.
Couillard, J. “The Role of Project Risk in Determining Project Management Approach,” Project Management Journal, 1995, pp. 3-15.
Cronbach, L.J. “Coefficient Alpha and the Internal Structure of Tests,” Psychometrika (16:3), 1951, pp. 273-334.
Deephouse, C., Mukhopadhyay, T. D., Goldenson, R. and Kellner, M. I. “Software Processes and Project Performance,” Journal of Management Information Systems (12:3), Winter 1995-96, pp. 187-205.
Delkleva, S. and Drehmer, D. “Measuring Software Engineering Evolution: A Rash Calibration,” Information Systems Research (8:1), 1997, pp. 95-104.
Deutsch, M.S. “An Exploratory Analysis Relating the Software Project Management Process to Project Success,” IEEE Transaction on Engineering Management (38:4), 1991, pp. 365-375.
Dion, R. “Process Improvement and The Corporate Balance Sheet,” IEEE Software (10), 1993, pp. 28-35.
Fltzgerald, B. and O’Kane, T. “A Longitudinal Study of Software Process Improvement,” IEEE Software (16:3), 1999, pp.37-45.
Frankl, P.G. and Weyuker, E.J. “Testing software to detect and reduce risk,” The Journal of Systems and Software (53), 2000, pp.275-286.
Hair, J.F., Anderson, R.E., Tatham, R.L., and Black, W.C. “Multivariate Data Analysis,” Prentice Hall, 1998, pp. 87-140.
Herbsleb, J. D. and Goldenson, D. R. “A System Survey of CMM Experience and Results,” Proceedings of ICSE-18, 1996, pp. 323-330.
Herbsleb, J. D., Zubrow, D., Goldenson, D. R., Hayes, W. and Paulk, M. “Software Quality and the Capability Maturity Model,” Communication of the ACM (40:6), June 1997, pp.30-40.
Hsieh, K.D. “Software Process Maturity and Its Related Factors of Large Companies in Taiwan,” unpublished Master dissertation, Dept. of MIS, National Chung Cheng University, 1996.
Humphrey, W. S., Snyder, T. R., and Willis, R. R. “Software Process Improvement at Hughes Aircraft.” IEEE Software (8:4), 1991, pp. 11-23.
Humphrey, W.S. “Managing the Software Process,” Software Eng. Inst., The SEI Series in Software Eng., Addison-Wesley, 1989.
Ibbs, C. W. and Kwak, Y. H. “Assessing Project Management maturity,” Project management Journal (31:1), 2000, pp. 32-43.
Jiang, J. and Klein, G. “Risks to different aspects of system success,” Information & Management (36), 1999, pp.263-272.
Jiang, J. and Klein, G. “Software Development Risks to Project Effectiveness,” The Journal of Systems and Software (52), 2000, pp. 3-10.
Jiang, J., Klein, G. and Balloun, J. “Ranking of System Implementation Success Factors,” Project Management Journal (27:4), 1996, pp. 50-55.
Johnson, J. “Turning CHAOS into Success,” http://softwaremag.com/ (2000 viewed)
Kaiser, H.F. and Rice, J. “Little Jiffy Mark IV,” Educational and Psychological Measurement (34:2), 1974, pp. 111-117.
Keil,M., Cule, P.E., Lyytinen, K. and Schmidt, R.C. “A Framework for Identifying Software Project Risks,” Communication of the ACM (41:11), 1998, pp. 76-83.
Kuilboer, J.P. and Ashrafi, N. “Software Process and Product Improvement: an Empirical Assessment,” Information and Software Technology (42), 2000, pp. 27-34.
Lipke, W. H. and Rosenbaum, S. “Software Improvements in an International Company,” Proceedings of 15th International Conference on Software Engineering, 1993, pp. 212-220.
Lyytinen, K. and Hirshheim, R. “Information Systems Failures — a Survey and Classification of the Empirical Literature,” Oxford Surveys in Information Technology (4), 1987, pp.257-309.
Lyytinen, K., Mathiassen, L. and Ropponen, J. “An Organizational Analysis of Software Risk Management Approaches,” Working Paper, University of Jyvaskyla, Jyvaskyla, Finland, 1993.
Mathiassen, K. L. and Ropponen, J. “A Framework for Software Risk Management,” Information Systems Research (9:3) , 1998, pp. 233-255.
McFarlan, F.W., “Portfolio approach to information systems,” Harvard Business Review (59: 5), 1981, pp.142-150.
Nidumolu, S.R. “Standardization, Requirements Uncertainty and Software Project Performance,” Information and Management (31), 1996, pp. 135-150.
Nidumolu, S.R. “The Effect of Coordination and Uncertainty on Software Project Performance: Residual Performance Risk as an Intervening Variable,” Information Systems Research (6:3), 1995, pp. 191-219.
Nunnally, J.C. “Psychometric Theory,” McGraw-Hill, New York, N.Y., 1978.
Paulk, M., Curtis, B., Chrissis, M.B. and Weber, C.V. “Capability Maturity Model for Software, version 1.1,” IEEE Software, July 1993, pp. 18-27.
Paulk, M., Weber, C.V., Garcia, S.M., Chrissis, M.B. and Bush, M. “Key Practices of The Capability Maturity Model, Version 1.1,” CMU/SEI-93-TR-25, Software Engineering Institute Pittsburgh, PA Feb., 1993.
Raffo, D. M., Vandeville, J. V. and Martin, R.H. “Software Process Simulation to Achieve Higher CMM levels,” The Journal of Systems and Software (46), 1999, pp. 163-172.
Rai, A. and Al-Hindi, H. “The Effects of Development Process Modeling and Task Uncertainty on Development Quality Performance,” Information & Management (37), 2000, pp.335-346.
Rivard, H.S. and Talbot, J. “Toward an Assessment of Software Development Risk,” Journal of Management Information System (10:2), 1993, pp. 203-255.
Rojas, T. and Perez, M. “The Capabilities and Maturity Model (CMM): A Case Study,” IEEE, 1997, pp.1285-1290.
Simon, P., Hillson, D., and Newland, K. “Project Risk Analysis and Management Guide,” High Wycombe, UK: The Association for Project Management.g
The Standish Group, CHAOS Report , 1998
The Standish Group, Chaos, Standish Group Report, 1995.
The Standish Group, Unfinished Voyages, Standish Group Report, 1996.
Thomson, H.E. and Mayhew, P. ”The Software Process: a Perspective on Improvement,” The Computer Journal (37:8), 1994, pp. 683-690.
Vitale, M.R. “The Growing Risks of Information Systems Success,” MIS Quarterly (10:4), 1986, pp. 327-334.
Ward, S. “Requirement for an Effective Project Risk Management Process,” Project Management Journal (30:7), 1999, pp.37-43.
Weill, P. and Broadbent, M. “Leveraging the New Infrastructure — How Market Leaders Capitalize on Information Technology,” Harvard Business School Press, Boston, MA, 1998.
QRCODE
 
 
 
 
 
                                                                                                                                                                                                                                                                                                                                                                                                               
第一頁 上一頁 下一頁 最後一頁 top
系統版面圖檔 系統版面圖檔