Requirements Prioritization Based on Benefit and Cost Prediction: A Method Classification Framework
暂无分享,去创建一个
[1] Camille Salinesi,et al. Choosing a Prioritization Method-Case of IS Security Improvement , 2006, CAiSE Forum.
[2] Ian Dey,et al. Qualitative Data Analysis: A User Friendly Guide for Social Scientists , 1993 .
[3] K. Beck,et al. Extreme Programming Explained , 2002 .
[4] Naresh R. Pandit. The creation of theory: A recent application of the grounded theory method , 1996 .
[5] L KumarRam,et al. A total quality management-based systems development process , 1997 .
[6] Joachim Karlsson,et al. Improved practical support for large-scale requirements prioritising , 1997, Requirements Engineering.
[7] Marjo Kauppinen,et al. Requirements Prioritization Challenges in Practice , 2004, PROFES.
[8] Joachim Karlsson,et al. Prioritizing Software Requirements In An Industrial Setting , 1997, Proceedings of the (19th) International Conference on Software Engineering.
[9] A. Herrmann,et al. Requirements Prioritization Based on Benefit and Cost Prediction: An Agenda for Future Research , 2008, 2008 16th IEEE International Requirements Engineering Conference.
[10] Martin Höst,et al. An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software , 2001, Requirements Engineering.
[11] Barbara Paech,et al. Quality Misuse , 2005 .
[12] Joachim Karlsson,et al. Software requirements prioritizing , 1996, Proceedings of the Second International Conference on Requirements Engineering.
[13] Claes Wohlin,et al. Criteria for Selecting Software Requirements to Create Product Value: An Industrial Empirical Study , 2006, Value-Based Software Engineering.
[14] Haiyan Zhao,et al. Feature-driven requirement dependency analysis and high-level software design , 2006, Requirements Engineering.
[15] A. Strauss,et al. Basics of qualitative research: Grounded theory procedures and techniques. , 1992 .
[16] Colette Rolland,et al. Payoff Analysis of Business Systems in Goal-Oriented Requirements Engineering , 2004 .
[17] Craig Boutilier,et al. Local Utility Elicitation in GAI Models , 2005, UAI.
[18] Karl E. Wiegers. First Things First: Prioritizing Requirements , 1999 .
[19] John B. Shoven,et al. I , Edinburgh Medical and Surgical Journal.
[20] Joseph M. Saur. Review of "Software by numbers: low-risk, high-return development" by Mark Denne and Jane Cleland-Huang. Prentice Hall 2004. , 2004, SOEN.
[21] Norman Schofield. Mathematical Methods in Economics and Social Choice , 1984 .
[22] Hakan Erdogmus,et al. Valuation of Software Initiatives Under Uncertainty: Concepts, Issues, and Techniques , 2006, Value-Based Software Engineering.
[23] A. Tversky,et al. Judgment under Uncertainty: Heuristics and Biases , 1974, Science.
[24] Pamela Jordan. Basics of qualitative research: Grounded theory procedures and techniques , 1994 .
[25] Claes Wohlin,et al. Engineering and Managing Software Requirements , 2005 .
[26] Beatrice Alenljung,et al. Supporting requirement-based decision-making in the software engineering process : A position paper , 2004 .
[27] B. Glaser. Basics of Grounded Theory Analysis: Emergence Vs. Forcing , 1992 .
[28] Jane Cleland-Huang,et al. Software by Numbers - Low-Risk, High-Return Development , 2003 .
[29] Claes Wohlin,et al. Pair-wise comparisons versus planning game partitioning—experiments on requirements prioritisation techniques , 2007, Empirical Software Engineering.
[30] Alan M. Davis,et al. The Art of Requirements Triage , 2003, Computer.
[31] C. Urquhart. An encounter with grounded theory: tackling the practical and philosophical issues , 2001 .
[32] K. Francis,et al. The Development of Constructivist Grounded Theory , 2006 .
[33] J. Carvalho,et al. Use of Grounded Theory in Information Systems Area: An Exploratory Analysis , 2002 .
[34] Barbara Kitchenham,et al. Procedures for Performing Systematic Reviews , 2004 .
[35] Antonis C. Stylianou,et al. A total quality management-based systems development process , 1997, DATB.
[36] Rahul Telang,et al. An ounce of prevention vs. a pound of cure: How can we measure the value of IT security solutions? , 2004 .
[37] Claes Wohlin,et al. An evaluation of methods for prioritizing software requirements , 1998, Inf. Softw. Technol..
[38] Ian Thomas,et al. Business-Driven Product Planning Using Feature Vectors and Increments , 2002, IEEE Softw..
[39] Julio Cesar Sampaio do Prado Leite,et al. On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.
[40] Peter H. N. de With,et al. Resolving requirement conflicts through non-functional decomposition , 2004, Proceedings. Fourth Working IEEE/IFIP Conference on Software Architecture (WICSA 2004).
[41] M. Bohanec,et al. The Analytic Hierarchy Process , 2004 .
[42] Dietmar Pfahl,et al. Trade-off Analysis for Requirements Selection , 2003, Int. J. Softw. Eng. Knowl. Eng..
[43] Dean Leffingwell,et al. Managing software requirements: a unified approach , 1999 .
[44] Claes Wohlin,et al. Requirements prioritisation: an experiment on exhaustive pair-wise comparisons versus planning game partitioning , 2004, ICSE 2004.
[45] Joachim Karlsson,et al. A Cost-Value Approach for Prioritizing Requirements , 1997, IEEE Softw..
[46] Barbara Paech,et al. MOQARE: misuse-oriented quality requirements engineering , 2008, Requirements Engineering.
[47] Suzanne Robertson,et al. Mastering the Requirements Process , 1999 .
[48] Nancy R. Mead,et al. SQUARE Project: Cost/Benefit Analysis Framework for Information Security Improvement Projects in Small Companies , 2004 .
[49] Magne Jørgensen,et al. A Systematic Review of Software Development Cost Estimation Studies , 2007, IEEE Transactions on Software Engineering.