運用風險因子識別與分析在軟體發展流程選擇

Use Risk Factors Identification and Analysis for Selecting the Software Development Processes

10.6188/JEB.2011.13(2).07

陳榮靜(Rung-Ching Chen)；劉延純(Yen-Chun Liu)；楊政豐(Jeng-Feng Yang)

軟體發展流程 ； 軟體開發模型 ； 風險因子 ； 風險識別分析 ； 風險評估因應 ； Software Development Process ； Software Development Model ； Risk Factor ； Risk Identification and Analysis ； Risk Assessment and Response

電子商務學報

13卷2期（2011 / 06 / 01）

389 - 412

繁體中文

產官學界等機關組織在資訊系統委外開發的過程中，常會面臨到各式不同的軟體風險，因而導致開發進度嚴重延宕甚至失敗，這些問題都是資訊管理者最迫切亟待解決的議題。因此，規範風險識別分析準則，及制定因應的軟體發展流程就顯得十分重要。但至今少有中外文獻探討軟體風險識別因子與軟體發展流程暨開發模型之間的關係，本研究將試圖探討如何運用統一化工作分解結構特徵分類法則與Boehm的風險分析架構，於專案起始階段，辯識可能存在的專案風險，評估各類風險對專案的影響，並依據各類資訊系統專案特性，進而建議可選擇之軟體發展流程與軟體開發模型，以期能減緩或避免風險的影響，增加軟體專案的成功機率。

Organizations, government and academia in the process of information systems in the outsourcing, often face the risk of all kinds of different software. These risks will lead to serious delays in the development progress. These problems are among the most pressing issues to be solved by information management. Therefore, the specification of criteria for risk identification and development of the software development process are very important. However, many studies are rarely found in the literature on the relationships between soft-ware risk identification factors and software development process. This study attempts to explore how to use unified Work Breakdown Structure (WBS) feature classification rules and Boehm's risk analysis framework, in the initial phase of the project, to identify the possible project risks and to assess the impact of various risks on the project. We proposed and alternative software development processes and software development models for various types of information systems based on project characteristics. Expect to slow down or avoid risks, and increase the success rate of software projects.

1. Karl, E. W. (2008), "21 Project Management Success Tips," Retrieved Oct. 2010, from http://www.processimpact.com/webinars.shtml#21tips.
2. DOD(USA)(1998), Department of Defense Handbook Work Breakdown Structure..
3. IBM (1997), Project Management Fundamentals Handbook..
4. Boehm, B. W.(1991).Software risk management: Principles and practices.IEEE Software,8(1),32-41.
5. Brown, W. J.,Malveau, R. C.,McCormick, H. W.,Mowbray, T. J.(1998).Refactoring Software, Architectures and Projects in Crisis.New York:Wiley Computer Publishing.
6. Charette, R. N.(1996).Large-scale project management is risk management.IEEE Software,13(4),110-117.
7. Jorgensen, M.,Dyba, T.,Kitchenham, B.(2005).Teaching evidence-based software engineering to university students.Proceedings of Software Metrics, 11th IEEE International Symposium
8. Kitchenham, B.,Jorgensen, M.,Dyba, T.(2004).Evidence-based software engineering.Proceedings of International Conference on Software Engineering (ICSE),Edinburgh:
9. Linda, W.,Mark, K.,Arum, R.(2004).How software project risk affects project performance: An investigation of the dimensions of risk and an exploratory model.PMI-ISSIG,35(2),289-321.
10. Project Management Institute(2008).Guide to the Project Management Body of Knowledge (PMBOK® Guide).USA:Project Management Institute, Inc.
11. Reel, J.S.(1999).Critical success factors in software projects.IEEE Software,16(3),18-23.
12. Rob, B.(2005).Proper planning can help project managers avoid raging fires.Computing Canada,31(16)
13. Sackett, D. L.,Straus, S. E.,Richardson, W. S.,Rosenberg, W.,Haynes, R. B.(2000).Evidence-Based Medicine: How to Practice and Teach EBM.Edinburgh:Churchill Livingstone.
14. van Genuchten, M.(1991).Why is software late® An empirical study of reasons for delay in software development.IEEE Transactions on Software Engineering,17(6),581-590.
15. 牟登秀(2009)。碩士論文(碩士論文)。中原大學資訊管理研究所。
16. 林信惠、黃明祥、王文良(2002)。軟體專案管理。貝塔。
17. 洪茂峰(2009)。碩士論文(碩士論文)。國立中山大學資訊管理學系研究所。
18. 張文貴(2001)。軟體技術文件標準手冊之編訂。軟體產業通訊，40，28-34。
19. 曹正城(2008)。碩士論文(碩士論文)。世新大學資訊管理學研究所。
20. 陳玉波(2003)。碩士論文(碩士論文)。國立中山大學資訊管理學系。
21. 楊政豐(2008)。碩士論文(碩士論文)。東海大學資訊工程與科學研究所。
22. 藍元志(2003)。碩士論文(碩士論文)。國立中央大學工業管理研究所。