软件项目风险管理信息系统开发研究
|
摘要
软件开发历来普遍存在着项目延期、费用超支甚至软件难以交付的严重问题，这些问题被业内人士统称为“软件危机”。针对这一问题，软件工程领域在软件设计、工具及开发方法的等方面均进行了改良以试图降低开发中的项目风险，然而收效甚微。随着软件工程研究的进展，上世纪80年代Boehm将风险管理的概念首次引入了软件界，并引起了广泛的关注。研究者们开始意识到软件项目与其他项目一样需要进行风险管理，而导致软件危机的根源正是由于软件项目和产品没有对风险实施有效的管理——软件项目风险管理的研究自此展开。
软件工程领域对于风险管理的研究主要集中在其过程、工具和方法上。实现风险管理理论设计上的过程和方法需要一定的管理工具的支持，然而目前大多数软件项目风险管理工具的应用面相对都比较狭窄，如各种类型的风险分析工具和仅供风险咨询的交流平台，即使是功能完善的风险管理软件也存在着无法实现风险交流的缺陷，相对来说，对于全面的风险管理系统的研究比较少。而软件项目风险管理活动的实际情况是：存在着大量需要存储和处理的不同类型的风险数据，这些不同类型的风险数据之间又存在着许多的逻辑关系，不可能仅靠一张风险列表就可以完成所有的管理操作；与此同时，软件项目风险管理过程也是一个有组织的过程，需要软件开发组织内部进行有序的风险交流；另外，软件企业也需要对风险管理经验进行积累以实现风险学习活动，从而提高风险管理能力。因此，有必要建立基于风险数据库并在WEB上分布的软件项目风险管理信息系统以实现软件项目开发中全面有效的风险管理。基于此，本文将在以往研究成果和实际调查研究的基础上，设计出一套完善的风险管理过程机制并配以合适的软件项目风险管理方法和工具，在此基础上将其软件化，设计出一个集风险识别、分析、计划和控制等软件项目风险管理基本功能为一体的，同时可以实现风险交流和风险学习的基于网络的软件项目风险管理信息系统，并在软件项目风险管理活动流程和系统功能分析的基础上利用统一建模语言(UML)对该系统进行建模。
Software engineers have always been facing the problems of schedule, budget or the quality of the software product, those problems are called "software crisis". Though many considerable improvements have been made in terms of design, tools and development process endeavoring to decrease those risks, but the situation was not changed much. With the development of software engineering, in 1980s Boehm introduced the theory of risk management into software development area. After that, researchers gradually realized the importance of applying risk management into software projects. Having been aware that none risk management was the root cause of software crisis, people started to conduct risk management research in software industry.
Current research of risk management in software industry basically focuses on process, tools and methodology. And the realization of the designed process and methodology of software risk management more or less relies on the support of related management tools. However, the current management tools of software risk management could only fulfill some basic functions, such as all kinds of risk analysis tools, information platform for risk consulting, or even some outstanding risk management software could not perform risk communication. Little research of comprehensive risk management system has been conducted. The fact is that during the software risk management process there is numerous different types of risk data that has a great deal of logic relations with each other having to be stored and managed. And the management operations cannot be completed by a single list of risk factors. Meanwhile, carrying out the software-project risk management is also a systematic process, which demands an ordered risk communication channel within the software development team. Also, the software companies need to accumulate risk management experience to improve their risk management capabilities. Therefore, it is necessary to build a software project risk management system based on risk database and WEB distributing, in order to fulfill the comprehensive risk management in software development projects. According to that, based on the previous papers and practical investigation, the author has designed and softwarizaed a set of effective process mechanism for risk management working with appropriate software risk management methodology and tools. The research result of this paper is a risk management system for software projects based on WEB, with the functions of risk identification, analysis, planning and controlling and the capabilities to realize risk communication and risk learning. Based on the software risk management process and system function analysis, the system has been modeled in UML.
软件工程领域对于风险管理的研究主要集中在其过程、工具和方法上。实现风险管理理论设计上的过程和方法需要一定的管理工具的支持，然而目前大多数软件项目风险管理工具的应用面相对都比较狭窄，如各种类型的风险分析工具和仅供风险咨询的交流平台，即使是功能完善的风险管理软件也存在着无法实现风险交流的缺陷，相对来说，对于全面的风险管理系统的研究比较少。而软件项目风险管理活动的实际情况是：存在着大量需要存储和处理的不同类型的风险数据，这些不同类型的风险数据之间又存在着许多的逻辑关系，不可能仅靠一张风险列表就可以完成所有的管理操作；与此同时，软件项目风险管理过程也是一个有组织的过程，需要软件开发组织内部进行有序的风险交流；另外，软件企业也需要对风险管理经验进行积累以实现风险学习活动，从而提高风险管理能力。因此，有必要建立基于风险数据库并在WEB上分布的软件项目风险管理信息系统以实现软件项目开发中全面有效的风险管理。基于此，本文将在以往研究成果和实际调查研究的基础上，设计出一套完善的风险管理过程机制并配以合适的软件项目风险管理方法和工具，在此基础上将其软件化，设计出一个集风险识别、分析、计划和控制等软件项目风险管理基本功能为一体的，同时可以实现风险交流和风险学习的基于网络的软件项目风险管理信息系统，并在软件项目风险管理活动流程和系统功能分析的基础上利用统一建模语言(UML)对该系统进行建模。
Software engineers have always been facing the problems of schedule, budget or the quality of the software product, those problems are called "software crisis". Though many considerable improvements have been made in terms of design, tools and development process endeavoring to decrease those risks, but the situation was not changed much. With the development of software engineering, in 1980s Boehm introduced the theory of risk management into software development area. After that, researchers gradually realized the importance of applying risk management into software projects. Having been aware that none risk management was the root cause of software crisis, people started to conduct risk management research in software industry.
Current research of risk management in software industry basically focuses on process, tools and methodology. And the realization of the designed process and methodology of software risk management more or less relies on the support of related management tools. However, the current management tools of software risk management could only fulfill some basic functions, such as all kinds of risk analysis tools, information platform for risk consulting, or even some outstanding risk management software could not perform risk communication. Little research of comprehensive risk management system has been conducted. The fact is that during the software risk management process there is numerous different types of risk data that has a great deal of logic relations with each other having to be stored and managed. And the management operations cannot be completed by a single list of risk factors. Meanwhile, carrying out the software-project risk management is also a systematic process, which demands an ordered risk communication channel within the software development team. Also, the software companies need to accumulate risk management experience to improve their risk management capabilities. Therefore, it is necessary to build a software project risk management system based on risk database and WEB distributing, in order to fulfill the comprehensive risk management in software development projects. According to that, based on the previous papers and practical investigation, the author has designed and softwarizaed a set of effective process mechanism for risk management working with appropriate software risk management methodology and tools. The research result of this paper is a risk management system for software projects based on WEB, with the functions of risk identification, analysis, planning and controlling and the capabilities to realize risk communication and risk learning. Based on the software risk management process and system function analysis, the system has been modeled in UML.
引文
[1] Bahill, A. T. & Chapman, W. L. Case studies in system design[A]. Proceedings of the 1995 International Symposium and Workshop on systems Engineering of Computer Based Systems[C]. 1995:43-50
[2] Barron, F. H., von Winterfeldt, D. & Fischer, G M. Empirical and theoretical relationships between value and utility functions[J]. Acta Psychologica, 1984, 56:233-244
[3] Boehm, B. W. Software risk management: Principles and practices[J]. IEEE Software, 1991 (1): 32-41
[4] De Klerk, A. M. The value of project risk management[A]. Management of Engineering and Technology, 2001. PICMET'01. Portland International Conference on Management of Engineering and Technology[C]. 2001:570-576
[5] DeMarco, T. & Lister, T. Risk Management during Requirements[J]. Software, 2003 (5): 99-101
[6] Fussell, L. & Field, S. The Role of the Risk Management Database in the Risk Management Process[A]. International Conference on Systems Engineering[C]. 2005:364-369
[7] Garvey, P. R, Phair, D.J & Wilson, J.A. An information architecture for risk assessment and management[J].Software IEEE,1997,14(2):25-34
[8] Gemmer, A. Risk management: moving beyond process[J]. Computer, 1997 (5): 33-43
[9] Haimes, Y. Y. Risk analysis, systems analysis, and covey's seven habits[J]. Risk Analysis, 2001 (2): 217-224
[10] Haimes, Y. Y. & Jiang, P. Leontief based model of risk in complex interconnected infrastructures[J]. Journal of Infrastructure Systems, 2001 (1): 1-12
[11] Hantos, P. & Gisbert, M. Identifying Software Productivity Improvement Approaches and Risks: Construction Industry Case Study[J]. IEEE Software, 2000 (1): 48-56
[12] Heller, M. Life-cycle infrastructure risk management R&D needs[EB/OL], http://www.Ideo.columbia.edu/CHRR/Roundtable/Heller.Miriam.Note.pdf, 2002-04-12
[13] IEEE Standard for Software Life Cycle Processes-Risk Management[S]. 2001
[14] Jiamthubthugsin, W. & Sutivong, D. Resource Decisions in Software Development Using Risk Assessment Model[A]. System Sciences, 2006. HICSS'06. Proceedings of the 39th Annual Hawaii International conferecnce on System Sciences[C]. 2006: 229a-229a
[15] Jiang, J. J. Risks to different aspects of system success[J]. Information & Management, 1999, 36:263-272
[16] Juan, C. N., Luqi, & Valdis, B. et al. A Formal Risk Assessment Model for Software Evolution. Naval Postgraduate School 2, University Circle. Monterey, CA93943, USA
[17] Kaplan, S. & Garrick, B. J. On the quantitative definition of risk[J]. Risk Analysis, 1981 (1): 11-27
[18] Keshlaf, A. A. & Hashim, K. A. Model and Prototype Tool to Manage Software Risks[A]. First Asia-Pacific Conference on Quality Software[C]. 2000:297-305
[19] Kirsch, L. J. Deploying Common Systems Globally: The Dynamics of Control[J]. Information Systems Journal, 2004 (15): 374-395
[20] Klein, S. A. Putting methodology in perspective from a project risk viewpoint[J]. IEEE Power Engineering Society, 1999 (2): 362-365
[21] Kontio, J. The Riskit Method for Software Risk Management, Version 1.00. Compute Science Technical Reprots[R]. University of Maryland, College Park. MD. 1996
[22] Lee, H. M. Generalization of the group decision making using fuzzy sets theory for evaluating the rate of aggregative risk in software development[J]. Information Sciences, 1999, 113:301-311
[23] Microsoft Corp. MSF risk management process[DB/OL], http://www.Mierosoft.com, 1996-06
[24] Minato, T. & Ashley, D. B. Data-driven analysis of "corporate risk" using historical cost-control data[J]. Journal of Construction Engineering and Management, 1998 (1-2): 42-47
[25] Moynihan, T. An Inventory of Personal Constructs for Risk Researchers[J]. Information Technology, 1996 (11): 359-371
[26] Moynihan, T. How Experienced Project Managers Assess Risk[J]. Software, 1997 (3): 35-41
[27] Murthi, S. Preventive Risk Management for Software Projects[J]. IT Professional, 2002 (5): 9-15
[28] Nogueria, J.C., Luqi, & Bhattacharya, S. A risk assessment model for software prototyping projects[A]. Proceedings 11th International Workshop on Rapid System Prototyping[C]. 2000: 28-33
[29] NASA SATC. Continuous risk management at NASA[EB/OL]. http://satc.gsfc.nasa.gov/support/ASM. FEB99/crm.at.nasa.html, 1999-02-01
[30] Nogueira, L. J. A Risk Assessment Model for Evolutionary Software Projects. Naval PostGraduate School, Monterey, CA 93943, USA
[31] Pennock, M. J. & Haimes, Y. Y. Principles and guidelines for Project risk management[J]. Systems Engineering, 2002 (2): 89-108
[32] Powell, P. L. & Klein, J. H. Risk management for information systems development[J]. Journal of Information Technology, 1996 (4): 307-317
[33] Ren, H. Risk lifecycle and risk relationships on construction project[J]. International Journal of Project Management, 1994 (2): 68-74
[34] Robert, C. N. Software engineering risk analysis and management[M]. McGraw-Hill Software Engineering Series, New York Intertext Publications: McGraw-Hill Book, 1989
[35] Ronald, P. H. & Yacov, Y. H. Software Risk Management[R]. Carnegie Mellon University, Pittsburgh, Pennysylvania, 1996
[36] Say, W. E & Muruganantham, Software risk assessment model[A]. Proceedings of the 2000 IEEE international Conference on Management of Innovation and Technology[C]. 2000: 539-544
[37] Stephen, D., Mark, K. & Lars, M. et al. The Role of Perceived Control, Attention-Shaping, And Expertise in IT Project Risk Assessment[A]. Proceedings of the 39thHawaii International Conference on System Sciences[C]. 2006
[38] Treasury Board Canada. Integrated risk management framework[EB/OL], http://www.tbs-sct.gc.ca/pubs.pol/dcgpubs/, 2001-04-01
[39] Tummala, V. M., Leung, H. M. & Mok, C. K. et al. Practice, barriers and benefits of using risk management approaches in selected Hong Kong industries[J]. International Journal of Project Management, 1997 (5): 297-312
[40] Walsh, K. R. & Schneider, H. The role of motivation and risk behavior in software development success[J]. Information Research, 7 (3): 27-36
[41] Ward, S. & Chapman, C. Transforming project risk management into project uncertainty management[J]. International Journal of Project Management, 2003, 21:97-105
[42] Wiegers, Kal E. Know Your Enemy: Software Risk Management[EB/OL].http://www.processimpact.com/articles/risk_mgrnt.html
[43] Williams, R. C., Walker, J. A. & Dorofee, A. J. et al. Putting Risk Management into Practice[J]. Software, 1997 (3): 75-82
[44] 卞莹，张玉清和孙铁等．系统安全风险评估数据库[J]．计算机工程，2003(29)：：97-99
[45] 蔡敏，徐慧慧和黄炳强编著．UML基础与ROSE建模教程[M]．北京：人民邮电出版社，2006
[46] 曹光忠．软件项目的风险管理[J]．计算机时代，2005(6)：：35-37
[47] 陈和兰，龚少文。大型软件项目中的组织环境[J]_项目管理技术，2004(12)：65-71
[48] 陈亮，黄宏伟和胡群芳．盾构隧道施工风险管理数据库系统开发[J]．地下空间与工程学报，2005(1)：964-967
[49] 陈蔚力．估算软件项目周期[J]．中国计算机用户，2003(4)：19
[50] 陈忠．软件项目的风险管理[J]．经济与社会发展，2004(2)：67-68，142
[51] 方德英．IT项目风险管理理论与方法研究[D]．博士学位论文，天津大学，2003
[52] 方德英，李敏强和寇纪淞．软件项目风险管理方法的比较与分析[J]．运筹与管理，2004 (13)：81-85
[53] 冯积社．软件项目管理与一般项目管理的比较分析[J]_陇东学院学报：自然科学版，2005(15)：11-13
[54] 谷烽，姜云飞和毛明志．软件过程模型回顾与分析[J]．现代计算机，下半月刊：28-30
[55] 鞠彦兵，冯允成和姚李刚．基于证据理论的软件开发风险评估方法[J]．系统工程理论方法应用，2003(12)：218-223
[56] 关忠诚和程刚．基于敏捷方法的软件项目管理研究[J]．重庆大学学报：社会科学版，2005(11)：46-49
[57] 韩珂，孙忠林和赵卫东等．中小型MIS系统开发过程的管理[J]．福建电脑，2005(2)：16-17
[58] 胡首，陈定方和陶德馨．基于J2EE和PDM的企业应用集成研究与应用[J]．武汉理工大学学报：交通科学与工程版，2004，28(3)：395-398
[59] 黄国言，沈秀敏．网络协同工作的应用共享机制[J]．计算机工程与设计，2006，27(18)：3356-3359
[60] 侯红，郝克刚．基于EVA的软件测量[J]_西北大学学报：自然科学版，2005，35(2)：159-162
[61] 黄宏伟，曾明和陈亮等．基于风险数据库的盾构隧道施工风险管理软(TRM1.0)开发[J]．地下空间与工程学报，2006(2)：36-41
[62] 蒋国萍和陈英武．基于证据推理的软件项目复杂性评估[J]．计算机工程与应用，2005(41)：4-6，10
[63] 李美华和付宏．软件项目风险评估模型的建立[J]．吉林大学学报：信息科学版，2005(23)：696-701
[64] 李云辉．软件开发风险管理技术及其支持环境的研究与实现[D]．硕士学位论文，北京航空航天大学，2004
[65] 廖跃华和吴毅军．跨国公司风险管理新视野——战略风险管理模型[J]．上海理工大学学报：社会科学版，2004(26)：10-13
[66] 陆伟．软件项目管理及其在中小规模开发中的实施[J]．电脑知识与技术：学术交流，2005(3)：62-66
[67] 罗铁清，王莹和王如龙．软件项目管理流程分析与设计[J]_计算机技术与现代化，2005(24)：106-108
[68] 麦强盛．项目风险管理的实施与优化[J]．商业时代，2005(27)：31-32
[69] 毛明志和葛晓炜．有效的软件开发项目风险管理模型[J]．科技管理研究，2005(25)：247-250
[70] 梅宏译．软件工程——实践者的研究方法[M]．第二版，北京：机械工业出版社，2005
[71] 孟祥睿．软件项目风险管理研究[J]．经济论坛，2005(7)：98-99
[72] 潘陈勇．基于生命周期的软件开发动态风险管理[D]．硕士学位论文，浙江大学，2002
[73] 彭晓红和涂宏春．软件开发中的项目风险管理[J]．项目管理技术，2004(8)：60-64
[74] 齐跃斗．基于Agent技术的Web-Based Training应用研究[J]．微计算机信息，2006(05Z)：295-297
[75] 钱昊和马维珍．层次分析法在项目风险管理中的应用[J]．兰州交通大学学报，2005(24)：53-56
[76] 邱嘉文．软件项目的系统基模初探[J]．科技管理研究，2003(2)：42-46
[77] 邱莞华．现代项目分险管理方法与实践[M]．北京：科学出版社，2003
[78] 王海鹏，周靖译，风险管理——软件系统开发方法[M]．北京：清华大学出版社，2002
[79] 王新宇和张仲义．基于关系的MIS软件项目管理的组织模式及应用[J]．现代计算机：下半月刊，2001(3)：38-40
[80] 王晓毅．软件项目成功的要素[J]．程序员，2005(8)：51-53
[81] 谢杨编译．J2EE究竟是什么?[EB／OL]．http://www.ccw.com.cn/htm/center/tech/02672.asp
[82] 熊节，马珊珊译．与熊共舞——软件项目风险管理[M]．北京：清华大学出版社，2004
[83] 胥玲和黄洪．软件项目的风险评价模型[J]．计算机工程与应用，2004(13)：227-229
[84] 尹明杨，胡志勇．软件风险管理的数据库模型[J]．电脑知识与技术：学术交流，2006(11)：28-29
[85] 于进．软件项目风险管理中风险分析方法的研究[J]，计算机与现代化，2005(8)：11-13
[86] 张芬琦，李仰东和崔丽萍．浅析EAI技术[J]．山西通信科技，2004，25(2)：3-7
[87] 张慧和段万春．如何实行有效的软件项目管理[J]．商业研究，2004(8)：81-82
[88] 张珞玲和李师贤．软件项目风险管理方法比较和研究[J]．计算机工程，2003(29)：91-94
[89] 张雯，马力和关昕．软件项目进度风险的定量分析[J]．计算机工程与设计，2006，27(18)：3439-3441
[90] 张亚莉，杨乃定和杨朝君．一种项目风险问题的集成化研究框架[J]．预测，2005(24)：26-31
[91] 郑劲松，陈江和陈冰冰．小型软件项目开发的方法[J]．浙江工业大学学报，2003(2)：71-74
[92] 郑淑艳．MIS项目实施中的风险管理[J]．软件工程师，2004(1)：58-59
[93] 中国工业可持续发展网．项目管理知识体系(PMBOOK2000)[EB／OL]．http://www.csid.com.cn/NewsInfo.asp?Newsld=1342
[94] 中华报告网．2005-2006中国软件产业研究年度报告[EB／OL]．http://www.ccmnet.com/B7/200603/B72301200603081105070000.asp, 2006.03.08
[95] 周浩宇．走出软件项目的死亡之旅——软件项目的管理现状和出路[J]．程序员，2005(8)：47-51
[96] http://www.americansystems.com
[97] http://www.risktrak.com
[2] Barron, F. H., von Winterfeldt, D. & Fischer, G M. Empirical and theoretical relationships between value and utility functions[J]. Acta Psychologica, 1984, 56:233-244
[3] Boehm, B. W. Software risk management: Principles and practices[J]. IEEE Software, 1991 (1): 32-41
[4] De Klerk, A. M. The value of project risk management[A]. Management of Engineering and Technology, 2001. PICMET'01. Portland International Conference on Management of Engineering and Technology[C]. 2001:570-576
[5] DeMarco, T. & Lister, T. Risk Management during Requirements[J]. Software, 2003 (5): 99-101
[6] Fussell, L. & Field, S. The Role of the Risk Management Database in the Risk Management Process[A]. International Conference on Systems Engineering[C]. 2005:364-369
[7] Garvey, P. R, Phair, D.J & Wilson, J.A. An information architecture for risk assessment and management[J].Software IEEE,1997,14(2):25-34
[8] Gemmer, A. Risk management: moving beyond process[J]. Computer, 1997 (5): 33-43
[9] Haimes, Y. Y. Risk analysis, systems analysis, and covey's seven habits[J]. Risk Analysis, 2001 (2): 217-224
[10] Haimes, Y. Y. & Jiang, P. Leontief based model of risk in complex interconnected infrastructures[J]. Journal of Infrastructure Systems, 2001 (1): 1-12
[11] Hantos, P. & Gisbert, M. Identifying Software Productivity Improvement Approaches and Risks: Construction Industry Case Study[J]. IEEE Software, 2000 (1): 48-56
[12] Heller, M. Life-cycle infrastructure risk management R&D needs[EB/OL], http://www.Ideo.columbia.edu/CHRR/Roundtable/Heller.Miriam.Note.pdf, 2002-04-12
[13] IEEE Standard for Software Life Cycle Processes-Risk Management[S]. 2001
[14] Jiamthubthugsin, W. & Sutivong, D. Resource Decisions in Software Development Using Risk Assessment Model[A]. System Sciences, 2006. HICSS'06. Proceedings of the 39th Annual Hawaii International conferecnce on System Sciences[C]. 2006: 229a-229a
[15] Jiang, J. J. Risks to different aspects of system success[J]. Information & Management, 1999, 36:263-272
[16] Juan, C. N., Luqi, & Valdis, B. et al. A Formal Risk Assessment Model for Software Evolution. Naval Postgraduate School 2, University Circle. Monterey, CA93943, USA
[17] Kaplan, S. & Garrick, B. J. On the quantitative definition of risk[J]. Risk Analysis, 1981 (1): 11-27
[18] Keshlaf, A. A. & Hashim, K. A. Model and Prototype Tool to Manage Software Risks[A]. First Asia-Pacific Conference on Quality Software[C]. 2000:297-305
[19] Kirsch, L. J. Deploying Common Systems Globally: The Dynamics of Control[J]. Information Systems Journal, 2004 (15): 374-395
[20] Klein, S. A. Putting methodology in perspective from a project risk viewpoint[J]. IEEE Power Engineering Society, 1999 (2): 362-365
[21] Kontio, J. The Riskit Method for Software Risk Management, Version 1.00. Compute Science Technical Reprots[R]. University of Maryland, College Park. MD. 1996
[22] Lee, H. M. Generalization of the group decision making using fuzzy sets theory for evaluating the rate of aggregative risk in software development[J]. Information Sciences, 1999, 113:301-311
[23] Microsoft Corp. MSF risk management process[DB/OL], http://www.Mierosoft.com, 1996-06
[24] Minato, T. & Ashley, D. B. Data-driven analysis of "corporate risk" using historical cost-control data[J]. Journal of Construction Engineering and Management, 1998 (1-2): 42-47
[25] Moynihan, T. An Inventory of Personal Constructs for Risk Researchers[J]. Information Technology, 1996 (11): 359-371
[26] Moynihan, T. How Experienced Project Managers Assess Risk[J]. Software, 1997 (3): 35-41
[27] Murthi, S. Preventive Risk Management for Software Projects[J]. IT Professional, 2002 (5): 9-15
[28] Nogueria, J.C., Luqi, & Bhattacharya, S. A risk assessment model for software prototyping projects[A]. Proceedings 11th International Workshop on Rapid System Prototyping[C]. 2000: 28-33
[29] NASA SATC. Continuous risk management at NASA[EB/OL]. http://satc.gsfc.nasa.gov/support/ASM. FEB99/crm.at.nasa.html, 1999-02-01
[30] Nogueira, L. J. A Risk Assessment Model for Evolutionary Software Projects. Naval PostGraduate School, Monterey, CA 93943, USA
[31] Pennock, M. J. & Haimes, Y. Y. Principles and guidelines for Project risk management[J]. Systems Engineering, 2002 (2): 89-108
[32] Powell, P. L. & Klein, J. H. Risk management for information systems development[J]. Journal of Information Technology, 1996 (4): 307-317
[33] Ren, H. Risk lifecycle and risk relationships on construction project[J]. International Journal of Project Management, 1994 (2): 68-74
[34] Robert, C. N. Software engineering risk analysis and management[M]. McGraw-Hill Software Engineering Series, New York Intertext Publications: McGraw-Hill Book, 1989
[35] Ronald, P. H. & Yacov, Y. H. Software Risk Management[R]. Carnegie Mellon University, Pittsburgh, Pennysylvania, 1996
[36] Say, W. E & Muruganantham, Software risk assessment model[A]. Proceedings of the 2000 IEEE international Conference on Management of Innovation and Technology[C]. 2000: 539-544
[37] Stephen, D., Mark, K. & Lars, M. et al. The Role of Perceived Control, Attention-Shaping, And Expertise in IT Project Risk Assessment[A]. Proceedings of the 39thHawaii International Conference on System Sciences[C]. 2006
[38] Treasury Board Canada. Integrated risk management framework[EB/OL], http://www.tbs-sct.gc.ca/pubs.pol/dcgpubs/, 2001-04-01
[39] Tummala, V. M., Leung, H. M. & Mok, C. K. et al. Practice, barriers and benefits of using risk management approaches in selected Hong Kong industries[J]. International Journal of Project Management, 1997 (5): 297-312
[40] Walsh, K. R. & Schneider, H. The role of motivation and risk behavior in software development success[J]. Information Research, 7 (3): 27-36
[41] Ward, S. & Chapman, C. Transforming project risk management into project uncertainty management[J]. International Journal of Project Management, 2003, 21:97-105
[42] Wiegers, Kal E. Know Your Enemy: Software Risk Management[EB/OL].http://www.processimpact.com/articles/risk_mgrnt.html
[43] Williams, R. C., Walker, J. A. & Dorofee, A. J. et al. Putting Risk Management into Practice[J]. Software, 1997 (3): 75-82
[44] 卞莹，张玉清和孙铁等．系统安全风险评估数据库[J]．计算机工程，2003(29)：：97-99
[45] 蔡敏，徐慧慧和黄炳强编著．UML基础与ROSE建模教程[M]．北京：人民邮电出版社，2006
[46] 曹光忠．软件项目的风险管理[J]．计算机时代，2005(6)：：35-37
[47] 陈和兰，龚少文。大型软件项目中的组织环境[J]_项目管理技术，2004(12)：65-71
[48] 陈亮，黄宏伟和胡群芳．盾构隧道施工风险管理数据库系统开发[J]．地下空间与工程学报，2005(1)：964-967
[49] 陈蔚力．估算软件项目周期[J]．中国计算机用户，2003(4)：19
[50] 陈忠．软件项目的风险管理[J]．经济与社会发展，2004(2)：67-68，142
[51] 方德英．IT项目风险管理理论与方法研究[D]．博士学位论文，天津大学，2003
[52] 方德英，李敏强和寇纪淞．软件项目风险管理方法的比较与分析[J]．运筹与管理，2004 (13)：81-85
[53] 冯积社．软件项目管理与一般项目管理的比较分析[J]_陇东学院学报：自然科学版，2005(15)：11-13
[54] 谷烽，姜云飞和毛明志．软件过程模型回顾与分析[J]．现代计算机，下半月刊：28-30
[55] 鞠彦兵，冯允成和姚李刚．基于证据理论的软件开发风险评估方法[J]．系统工程理论方法应用，2003(12)：218-223
[56] 关忠诚和程刚．基于敏捷方法的软件项目管理研究[J]．重庆大学学报：社会科学版，2005(11)：46-49
[57] 韩珂，孙忠林和赵卫东等．中小型MIS系统开发过程的管理[J]．福建电脑，2005(2)：16-17
[58] 胡首，陈定方和陶德馨．基于J2EE和PDM的企业应用集成研究与应用[J]．武汉理工大学学报：交通科学与工程版，2004，28(3)：395-398
[59] 黄国言，沈秀敏．网络协同工作的应用共享机制[J]．计算机工程与设计，2006，27(18)：3356-3359
[60] 侯红，郝克刚．基于EVA的软件测量[J]_西北大学学报：自然科学版，2005，35(2)：159-162
[61] 黄宏伟，曾明和陈亮等．基于风险数据库的盾构隧道施工风险管理软(TRM1.0)开发[J]．地下空间与工程学报，2006(2)：36-41
[62] 蒋国萍和陈英武．基于证据推理的软件项目复杂性评估[J]．计算机工程与应用，2005(41)：4-6，10
[63] 李美华和付宏．软件项目风险评估模型的建立[J]．吉林大学学报：信息科学版，2005(23)：696-701
[64] 李云辉．软件开发风险管理技术及其支持环境的研究与实现[D]．硕士学位论文，北京航空航天大学，2004
[65] 廖跃华和吴毅军．跨国公司风险管理新视野——战略风险管理模型[J]．上海理工大学学报：社会科学版，2004(26)：10-13
[66] 陆伟．软件项目管理及其在中小规模开发中的实施[J]．电脑知识与技术：学术交流，2005(3)：62-66
[67] 罗铁清，王莹和王如龙．软件项目管理流程分析与设计[J]_计算机技术与现代化，2005(24)：106-108
[68] 麦强盛．项目风险管理的实施与优化[J]．商业时代，2005(27)：31-32
[69] 毛明志和葛晓炜．有效的软件开发项目风险管理模型[J]．科技管理研究，2005(25)：247-250
[70] 梅宏译．软件工程——实践者的研究方法[M]．第二版，北京：机械工业出版社，2005
[71] 孟祥睿．软件项目风险管理研究[J]．经济论坛，2005(7)：98-99
[72] 潘陈勇．基于生命周期的软件开发动态风险管理[D]．硕士学位论文，浙江大学，2002
[73] 彭晓红和涂宏春．软件开发中的项目风险管理[J]．项目管理技术，2004(8)：60-64
[74] 齐跃斗．基于Agent技术的Web-Based Training应用研究[J]．微计算机信息，2006(05Z)：295-297
[75] 钱昊和马维珍．层次分析法在项目风险管理中的应用[J]．兰州交通大学学报，2005(24)：53-56
[76] 邱嘉文．软件项目的系统基模初探[J]．科技管理研究，2003(2)：42-46
[77] 邱莞华．现代项目分险管理方法与实践[M]．北京：科学出版社，2003
[78] 王海鹏，周靖译，风险管理——软件系统开发方法[M]．北京：清华大学出版社，2002
[79] 王新宇和张仲义．基于关系的MIS软件项目管理的组织模式及应用[J]．现代计算机：下半月刊，2001(3)：38-40
[80] 王晓毅．软件项目成功的要素[J]．程序员，2005(8)：51-53
[81] 谢杨编译．J2EE究竟是什么?[EB／OL]．http://www.ccw.com.cn/htm/center/tech/02672.asp
[82] 熊节，马珊珊译．与熊共舞——软件项目风险管理[M]．北京：清华大学出版社，2004
[83] 胥玲和黄洪．软件项目的风险评价模型[J]．计算机工程与应用，2004(13)：227-229
[84] 尹明杨，胡志勇．软件风险管理的数据库模型[J]．电脑知识与技术：学术交流，2006(11)：28-29
[85] 于进．软件项目风险管理中风险分析方法的研究[J]，计算机与现代化，2005(8)：11-13
[86] 张芬琦，李仰东和崔丽萍．浅析EAI技术[J]．山西通信科技，2004，25(2)：3-7
[87] 张慧和段万春．如何实行有效的软件项目管理[J]．商业研究，2004(8)：81-82
[88] 张珞玲和李师贤．软件项目风险管理方法比较和研究[J]．计算机工程，2003(29)：91-94
[89] 张雯，马力和关昕．软件项目进度风险的定量分析[J]．计算机工程与设计，2006，27(18)：3439-3441
[90] 张亚莉，杨乃定和杨朝君．一种项目风险问题的集成化研究框架[J]．预测，2005(24)：26-31
[91] 郑劲松，陈江和陈冰冰．小型软件项目开发的方法[J]．浙江工业大学学报，2003(2)：71-74
[92] 郑淑艳．MIS项目实施中的风险管理[J]．软件工程师，2004(1)：58-59
[93] 中国工业可持续发展网．项目管理知识体系(PMBOOK2000)[EB／OL]．http://www.csid.com.cn/NewsInfo.asp?Newsld=1342
[94] 中华报告网．2005-2006中国软件产业研究年度报告[EB／OL]．http://www.ccmnet.com/B7/200603/B72301200603081105070000.asp, 2006.03.08
[95] 周浩宇．走出软件项目的死亡之旅——软件项目的管理现状和出路[J]．程序员，2005(8)：47-51
[96] http://www.americansystems.com
[97] http://www.risktrak.com