您的位置:首页 > 其它

需求评审五个维度框架分析及其带来的启示-5-结束语

2016-06-09 10:31 323 查看
本文整理归纳了需求评审的各种类型,分析识别了需求评审的5大关键方面,提出了五维需求评审框架,并分析验证了此新需求评审框架的有效性。结合此新需求评审框架,对软件开发主要情境进行了分析,得到了15个高效需求评审的启示,得到了结合需求条目化管理的多级小瀑布模型,这新瀑布模型也许将为陷入困局的传统瀑布模型打开一条新路。软件需求评审还有一些其他重要的方面,比如检查表和度量等等,本文限于篇幅不再更多分析,但值得指出的是,在新的五维需求评审框架下能够更全局的优化考虑这些方面。

致谢 本文提及的多项启示和实践都是据于作者工作经历,最早在宝信软件中得到并开始实施,后来在多家公司实施时得到改进,在此向宝信软件董文生、滕逸龙、肖宁,中彩在线公司詹章彬、马元,快钱公司周泳韶、顾剑华表示诚挚的感谢。

参考文献:

[1] Curtis B, Krasner H, Iscoe N. A field study of the software design process for large systems[J]. Communications of the ACM, 1988,31(11): 1268-1287.

[2] Boehm B W. A spiral model of software development and enhancement[J]. Computer, 1988, 21(5): 61-72.

[3] Zhu XF, Jin Z. Managing the inconsistency of software requirements. Journal of Software, 2005,16(7):1221 ? 1231. DOI:10.1360/jos161221(in Chinese).

[4] Sauer C, Jeffery D R, Land L, et al. The effectiveness of software development technical reviews: A behaviorally motivated program of research[J]. Software Engineering, IEEE Transactions on, 2000, 26(1): 1-14.

[5] Freedman D P, Weinberg G M. Handbook of walkthroughs, inspections, and technical reviews: Evaluating programs, projects, and products[J]. 1990.

[6] Wang L, WU JM. The Research on the Management of Requirement Changes in Software Project, Computer Technology and Development,Vol.17 No.1, Jan.2007(in Chinese).

[7] Ghosh S, Ramaswamy S, Jetley R P. Towards Requirements Change Decision Support[C]//Software Engineering Conference (APSEC, 2013 20th Asia-Pacific. IEEE, 2013, 1: 148-155.

[8] Morkos B, Mathieson J, Summers J D. Comparative analysis of requirements change prediction models: manual, linguistic, and neural network[J]. Research in Engineering Design, 2014, 25(2): 139-156.

[9] Zheng RJ, Yin RK, Tao YL. Practical software engineering. 2nd ed., Beijing: Tsinghua University Press, 1997 (in Chinese).

[10] IEEE Std 1028-2008 Standard for Software Reviews and Audits, 2008.

[11] Ghosh S, Ramaswamy S, Jetley R P. Towards Requirements Change Decision Support[C]//Software Engineering Conference (APSEC, 2013 20th Asia-Pacific. IEEE, 2013, 1: 148-155.

[12] Paulk M. Capability maturity model for software[M]. John Wiley & Sons, Inc., 1993.

[13] Team C P. Capability maturity model? integration (CMMI SM), version 1.1[J]. Software Engineering Institute, Carnegie Mellon University, Pittsburg, PA, Tech. Rep. SEI-2002-TR-012, 2002.

[14] Pyster A B, Thayer R H. Software Engineering Project Management 20 Years Later[J]. IEEE SOFTWARE, 2005, 1: 9.

[15] Fowler M. The new methodology[J]. Wuhan University Journal of Natural Sciences, 2001, 6(1-2): 12-24.

[16] Fowler M, Highsmith J. The agile manifesto[J]. Software Development, 2001, 9(8): 28-35.

[17] Cao L, Ramesh B. Agile requirements engineering practices: An empirical study[J]. Software, IEEE, 2008, 25(1): 60-67.

[18] Beck K, Beedle M, Van Bennekum A, et al. Principles behind the agile manifesto[J]. Agile Alliance, 2001.

[19] Sharma S, Sarkar D, Gupta D. Agile Processes and Methodologies: A Conceptual Study[J]. International Journal on Computer Science & Engineering, 2012, 4(5).

[20] Kim, Lesley Pek Wee, Chris Sauer, and Ross Jeffery. “A framework for software development technical reviews.” Software Quality and Productivity. Springer US, 1995. 294-299.

[21] Paetsch F, Eberlein A, Maurer F. Requirements engineering and agile software development[C]//2012 IEEE 21st International Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises. IEEE Computer Society, 2003: 308-308.

[22] DiGiovanni E, Nagaswami G. Online peer review: an alternative to face-to-face?[J]. ELT journal, 2001, 55(3): 263-272.

[23] Team, SEI CMMI Production. CMMI for Development v1. 3. Lulu. com, 2010.

[24] Nielsen J. Usability inspection methods[C]//Conference companion on Human factors in computing systems. ACM, 1994: 413-414.

[25] Hollingsed, Tasha, and David G. Novick. “Usability inspection methods after 15 years of research and practice.” Proceedings of the 25th annual ACM international conference on Design of communication. ACM, 2007.

[26] Zhang XJ. The Research on the Requirements Changes Management in Software Project,[J]. China Science and Technology Information. 2006(01) 107-108(in Chinese).

[27] Team, SEI CMMI Production. CMMI for Development v1. 3. Simplified-Chinese Edition. cmmiinstitute.com, 2014.(in Chinese)

[28] Schwaber K, Sutherland J. The scrum guide[J]. Scrum. org, October, 2011.

[29] Zheng RJ. Practical software engineering[M]. Beijing: Tsinghua University Press, 1997 (in Chinese).

[3] 朱雪峰, 金芝. 关于软件需求中的不一致性管理[J]. 软件学报, 2005, 16(7).

[6] 王莉,吴洁明. 软件项目中的需求变更管理的研究[J]. 计算机技术与发展,2007,17(01):119-121.

[9] 郑人杰,殷人昆,陶永雷.实用软件工程.第2版,北京:清华大学出版社,1997.

[26] 张秀娟. 软件项目中的需求变更管理研究[J]. 中国科技信息. 2006(01) 107-108.

[27] 卡耐基梅隆大学软件工程研究院团队. CMMI开发模型,版本1.3,简体中文版. cmmiinstitute.com, 2014.

[29] 郑人杰. 实用软件工程[M]. 清华大学出版社, 1991.
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: