Decision support in requirements engineering

Engineering and Managing Software Requirements

Volumn , Issue , 2005, Pages 267-286

  Ngo The, An ^a   Ruhe, Günther ^a  

^a UNIVERSITY OF CALGARY   (Canada)

Author keywords

Classification scheme; Decision making; Decision support; Requirements engineering decision; Requirements engineering process; Research analysis

Indexed keywords

EID: 33846560896     PISSN: None     EISSN: None     Source Type: Book    
DOI: 10.1007/3-540-28244-0_12     Document Type: Chapter

References (63)

1. Amandeep A, Ruhe G, Stanford M (2004) Intelligent support for software release planning. In: Proceedings of PROFES'04, LN on Computer Science, Vol. 3009, 248-262.
2. Al-Karaghouli W, Al-Shawi S, Fitzgerald G (2000). Negotiating and understanding information systems requirements: The use of set diagrams. Requirements Engineering 5(2): 93-102.
3. Alves C, Finkelstein A (2002). Challenges in COTS decision making: A goal-driven requirements engineering perspective. In: Proceedings of 14th International Conference on Software Engineering and Knowledge Engineering, Ischia, pp.789-794.
4. Andreou AS (2003) Promoting software quality through a human, social and organizational requirements elicitation process. Requirements Engineering 8(2): 85-101.
5. Andriole S (1998) The politics of requirements management. IEEE Software, Nov-Dec: pp.82-84.
6. Anthony RN (1965) Planning and control systems: A framework for analysis. Harvard University, Boston, USA.
7. Aurum A, Martin E (1998) Requirements elicitation using solo brainstorming. In: Proceedings of 3rd Australian Conference on Requirements Engineering (ACRE'98), Melbourne, Australia, pp.29-37.
8. Aurum A, Martin E (1999) Managing both individual and collective participation in software requirements elicitation process. In: Proceedings of 14th International Symposium on Computer and Information Sciences (ISCIS'99), Kusadasi, Turkey, pp.124-131.
9. Aurum A, Wohlin C (2003) The fundamental nature of requirement engineering activities as a decision making process. Information and Software Technology 45(14): 945-954.
10. Bagnall AJ, Rayward-Smith VJ, Whittley IM (2001) The next release problem. Information and Software Technology 43(14): 883-890.
11. Bergman M, King JL, Lyytinen K (2002) Large-scale requirements analysis revisited: The need for understanding the political ecology of requirements engineering. Requirements Engineering 7(3): 152-171.
12. Boehm B, Egyed A, Port D, Shah A, Kwan J, Madachy R (1998) A stakeholder Win- Win approach to software engineering education. Annals of Software Engineering 6: 295-321.
13. Boehm B, Grunbacher P, Briggs RD (2001) Developing groupware for requirements negotiation: Lessons learned. IEEE Software, May-Jun pp.46-55.
14. Burgess CJ, Dattani I, Hughes G, May JHR, Rees K (2001) Using influence diagrams to aid the management of software change. Requirements Engineering 6(3): 173-182.
15. Carlshamre, P (2002) Release planning in market-driven software product development: Provoking an understanding. Requirements Engineering 7(3): 139-15.
16. Conradi R, Nguyen MN, Wang AI, Liu C (2000) Planning support to software process evolution. International Journal of Software Engineering and Knowledge Engineering 10: 31-47.
17. Coughlan J, Macredie RD (2002) Effective communication in requirements elicitation: A comparison of methodologies. Requirements Engineering 7(2): 47-60.
18. Davis AM (2003) The art of requirements triage. IEEE Computer 36(3): 42-49.
19. DeGregorio G (1999) Enterprise-wide requirements and decision management. In: Proceedings of 9th International Symposium of the International Council on System Engineering, Brighton.
20. Denne M, Cleland-Huang J (2004) The incremental funding method: Data-driven software development. IEEE Software, May-Jun, pp.39-47.
21. Evans R, Park S, Alberts H (1997) Decisions not requirements: Decision-centered engineering of computer-based Systems. In: Proceedings of International Conference on Engineering and Computer-Based Systems, pp.435-442.
22. Fakun D, Greenough RM (2004) An exploratory study into whether to or not to include users in the development of industrial hypermedia applications. Requirements Engineering 9(1): 57-66.
23. Feather MS, Cornford SL (2003) Quantitative risk-based requirements reasoning. Requirements Engineering 8(4): 248-265.
24. Galliers RD, Swan JA (2000) There's more to information systems development than structured approaches: Information requirements analysis as a socially mediated process. Requirements Engineering 5(2): 74-82.
25. Glass R, Vessay I, Ramesh V (2002) Research in software engineering: An analysis of the literature. Information and Software Technology 44(8): 491-506.
26. Greer D, Ruhe G (2003) Software releasing planning: An evolutionary and iterative approach. Information and Software Technology 46(4): 243-253.
27. Hickey AM, Davis AM (2003) Elicitation technique selection: How do experts do it? In: Proceedings of 11th IEEE International Conference Requirements Engineering (ICRE'03), pp.169-178.
28. Hsia P, Kung D (1997) Software requirements and acceptance testing. Annals of Software Engineering 3: 291-317.
29. In H, Roy S (2001) Visualization issues for software requirements negotiation. In: Proceedings of 25th International conference Computer Software and Applications Conference (COMPSAC), pp.10-15.
30. Jung HW (1998) Optimizing value and cost in requirements analysis. IEEE Software, Jul-Aug, pp.74-78.
31. Karlsson J (1996) Software requirements prioritizing. In: Proceedings 2nd IEEE International Conference Requirements Engineering (ICRE'96), pp.110-116.
32. Karlsson J, Ryan K (1997) A cost-value approach for prioritizing requirements. IEEE Software, Sept-Oct, pp.67-74.
33. Karlsson J, Wohlin C, Regnell B (1998) An evaluation of methods for prioritizing software requirements. Information and Software Technology 39: 939-947.
34. Karlsson L, Berander P, Regnell B, Wohlin C (2004) Requirements prioritization: An experiment on exhaustive pair-wise comparisons versus planning game partitioning. In: Proceedings of EASE 2004, pp.145-154.
35. Kotonya G, Sommerville I (1998) Requirements engineering processes and techniques. Wiley, Chichester, UK.
36. Macaulay LA (1996) Requirements engineering, Springer Series on Applied Computing, Springer, London, UK.
37. Maiden NA, Ncube C (1998) Acquiring COTS software selection requirements. IEEE Software, Mar-Apr, pp.46-56.
38. Mintzberg H, Raisinghani D, Theoret A (1976) The structure of unstructured decision process. Administrative Science Quarterly, June, pp.246-275.
39. Mumford E (2000) A socio-technical approach to systems design. Requirements Engineering 5 (2): 125-133.
40. Nejmeh BA, Thomas I (2002) Business-driven product planning using feature vectors and increments. IEEE Software, Nov-Dec, pp.34-42.
41. Ngo-The A, Ruhe G (2003) Requirements negotiation under incompleteness and uncertainty. In: Proceedings of 15th, International Conference on Software Engineering and Knowledge Engineering (SEKE'03), pp.586-593.
42. Penny D (2002) An estimation-based management framework for enhancive maintenance in commercial software products. In: Proceedings of International Conference on Software Maintenance, pp.122-130.
43. Pomerol JC (1998) Scenario development and practical decision making under uncertainty: Application to requirements engineering. Requirements Engineering 3(3-4): 174-181.
44. Regnell B, Paech B, Aurum A, Wohlin C, Dutoit A, Natt och Dag J (2001) Requirements mean decisions! - Research issues for understanding and supporting decision making in requirements engineering. In: Proceedings of First Swedish Conference on Software Engineering Research and Practice (SERP'01), Ronneby, Sweden, pp.49-52.
45. Regnell B, Höst M, Natt och Dag J, Beremark P, Hjelm T (2001) An industrial case study on distributed prioritization in market-driven requirements engineering for packaged software. Requirements Engineering 6(1): 51-62.
46. Regnell B, Karlsson L, Höst M (2003) An analytical model for requirements selection quality evaluation in product software development. In: Proceedings of 11th IEEE International Conference Requirements Engineering, pp.254-263.
47. Rittel H, Webber M (1984) Planning problems are wicked problems. In: Developments in Design Methodology, Cross N (Ed.), Wiley, Chichester, UK, pp.135-144.
48. Rolland C, Souveyet C, Moreno M (1995) An approach for defining ways-of-working. Information Systems 20(4): 337-359.
49. Rosca D, Greenspan S, Feblowitz M, Wild C (1997) A decision making methodology in support of the business rules lifecycle. In: Proceedings of 3rd IEEE International Symposium on Requirements Engineering, pp.236-246.
50. Roy B, Bouyssou D (1993) Aide multicritère à la décision: méthodes et Cas. Economica, Paris, France.
51. Roy B (1993) Decision science or decision aid science. European Journal of Operation Research 66(2): 184-203.
52. Ruhe G (2003) Software engineering decision support - Methodology and applications. In: Innovations in Decision Support Systems. Advanced Knowledge International, Tonfoni G, Jain L (Eds.) Adelaide, Australia, pp.144-171.
53. Ruhe G, Eberlein A, Pfahl D (2002) Quantitative WinWin - A quantitative method for decision support in requirements negotiation. In: Proceedings of 14th International Conference on Software Engineering and Knowledge Engineering, Ischia, Italy, pp.159-166.
54. Ruhe G (2003) Intelligent support for selection of COTS products. In: Web, Web- Services, and Database Systems, . Chaudhri A, Jeckle M, Rahm E, Unland R (Eds.). Lecture Notes in Computer Science, Springer, Heidelberg, Germany, 2593: 34-45.
55. Ruhe G, Ngo-The A (2004) Hybrid intelligence in software release planning. International Journal of Hybrid Intelligent System, 1: 99-110.
56. Saaty T (1980) The analytic hierarchy process: Planning, priority setting, resource Allocation. McGraw-Hill, NY, USA.
57. Schärlig A (1996) The case of the vanishing optimum. Journal of Multi-criteria Decision Analysis 5: 160-164.
58. Simon HA (1960) The new science of management decisions. Prentice Hall, NJ, USA.
59. Sharp H, Finkelstein A, Galal G (1999) Stakeholder identification in the requirements engineering process. In: Proceedings of 10th International Workshop on Database and Expert Systems Application, IEEE Computer Society, pp.387-391.
60. Sommerville I, Sawyer P (1997) Requirements engineering: A good practice guide. Wiley, New York, USA.
61. Strigini L (1996) Limiting the dangers of intuitive decision making. IEEE Software, Jan, pp.101-103.
62. Wild C, Maly K, Zhang C, Roberts C, Rosca D, Taylor T (1994) Software engineering life cycle support - Decision based systems development. In: Proceedings of IEEE Region 10's 9th International Conference on Computer Technology, pp.781-784.
63. Zave P (1997) Classification of research efforts in requirements engineering. ACM Computing Surveys 29(4): 315-321.