Exploring factors affecting decision outcome and lead time in large-scale requirements engineering

Journal of Software: Evolution and Process

Volumn 27, Issue 9, 2015, Pages 647-673

  Wnuk, Krzysztof ^a,b   Kabbedijk, Jaap ^c   Brinkkemper, Sjaak ^c   Regnell, Björn ^b   Callele, David ^d  

^a BLEKINGE INSTITUTE OF TECHNOLOGY   (Sweden)

^b LUND UNIVERSITY   (Sweden)

^c UTRECHT UNIVERSITY   (Netherlands)

^d Experience First Design Inc   (Canada)

Author keywords

decision making; market driven requirements engineering; requirements engineering; software product lines

Indexed keywords

COMMERCE; REQUIREMENTS ENGINEERING; SALES; SURVEYS;

DECISION MAKING PROCESS; DECISION OUTCOME; LARGE-SCALE REQUIREMENTS ENGINEERINGS; MARKET DRIVEN; PRODUCT MANAGEMENT; SOFTWARE COMPONENT; SOFTWARE MARKETS; SOFTWARE PRODUCT LINE;

DECISION MAKING;

EID: 84941654310     PISSN: None     EISSN: 20477481     Source Type: Journal    
DOI: 10.1002/smr.1721     Document Type: Article

References (68)

1. Aurum A, Wohlin C,. Engineering and Managing Software Requirements. Springer-Verlag: Berlin Heidelberg, 2005.
2. Regnell B, Brinkkemper S,. Market-driven requirements engineering for software products. Engineering and Managing Software Requirements, Aurum A, Wohlin C, (eds.). Springer: Berlin, 2005; 287-308.
3. Karlsson L, Dahlstedt A, Regnell B, Natt och Dag J, Persson A,. Requirements engineering challenges in market-driven software development-an interview study with practitioners. Information and Software Technology 2007; 49 (6): 588-604.
4. Jonsson P, Lindvall M,. Impact analysis. Engineering and Managing Software Requirements, Aurum A, Wohlin C, (eds.). Springer: Berlin, 2005; 117-142.
5. Regnell B, Svensson RB, Wnuk K,. Can we beat the complexity of very large-scale requirements engineering? In: Proceedings of the 14th International Conference on Requirements Engineering: Foundation for Software Quality, Springer-Verlag, Berlin, REFSQ'08, 2008, pp. 123-128, DOI 10.1007/978-3-540-69062-7-11
6. Pohl K, Böckle G, Van Der Linden F,. Software Product Line Engineering: Foundations, Principles, and Techniques. Springer-Verlag: New York, 2005.
7. Khurum M, Khurum A, Gorschek T,. When product managers gamble with requirements: attitudes to value and risk. In: 11th International Software Product Line Conference, Berlin, Germany, 2007, pp. 97-104.
8. Alenljung B, Persson A,. Portraying the practice of decision-making in requirements engineering: a case of large scale bespoke development. Requirements Engineering 2008; 13 (4): 257-279.
9. Khurum M, Gorschek T, Wilson M,. The software value map-an exhaustive collection of value aspects for the development of software intensive products. Journal of Software: Evolution and Process 2012; 25: 711-741.
10. Karlsson J, Ryan K,. A cost-value approach for prioritizing requirements. IEEE Software 1997; 14 (5): 67-74.
11. Natt och Dag J, Regnell B, Gervasi V,. A linguistic-engineering approach to large-scale requirements management. IEEE Software 2005; 3: 32-39.
12. Gorschek T, Gomes A, Pettersson A, Torkar R, (2012) Introduction of a process maturity model for market-driven product management and requirements engineering. Journal of Software: Evolution and Process 24 (1): 83-113, DOI 10.1002/smr.535, URL 10.1002/smr.535
13. Kabbedijk J, Wnuk K, Regnell B, Brinkkemper S,. What decision characteristics influence decision making in market-driven large-scale software product line development? In: 16th International Working Conference on Requirements Engineering: Foundation for Software Quality, Duisburg, Germany, Proceedings of the Product Line Requirements Engineering and Quality Workshop, 2010, pp. 42-53.
14. Aurum A, Wohlin C,. The fundamental nature of requirements engineering activities as a decision-making process. Information and Software Technology 2003; 45 (14): 945-954.
15. Evans R, Park S, Alberts H,. Decisions not requirements decision-centered engineering of computer-based systems. In: The 1997 IEEE Conference and Workshop on Engineering of Computer-based Systems, 1997, pp. 435-442.
16. DeGregorio G,. Enterprise-wide requirements and decision management. In: Proceedings of 9th International Symposium of the International Council on System Engineering, 1999, pp. 92-107.
17. Ngo-The A, Ruhe G,. Decision support in requirements engineering. Engineering and Managing Software Requirements, Aurum A, Wohlin C, (eds.). Springer: Berlin, 2005; 267-286.
18. Klein G, Orasanu J, Calderwood R, Zsambok C, (eds). Decision Making in Action: Models and Methods. Norwood: New Jersey; 1995.
19. Veerappa V, Letier E,. Understanding clusters of optimal solutions in multi-objective decision problems. In: Proceedings of the 2011 IEEE 19th International Requirements Engineering Conference. IEEE Computer Society: Washington, DC, USA, RE'11, 2011; 89-98.
20. Milne A, Maiden N,. Power and politics in requirements engineering: embracing the dark side? Requirements Engineering 2012; 17 (2): 83-98.
21. Strigini L,. Limiting the dangers of intuitive decision making. IEEE Software 1996; 13 (1): 101-103.
22. Fogelstrom N, Barney S, Aurum A, Hederstierna A,. When product managers gamble with requirements: attitudes to value and risk. In: Requirements Engineering: Foundation for Software Quality. Proceedings 15th International Working Conference, REFSQ 2009, Berlin, Germany, 2009, pp 1-15.
23. Berander P, Andrews A,. Requirements prioritization. Engineering and Managing Software Requirements, Aurum A, Wohlin C, (eds.). Springer: Berlin Heidelberg, 2005; 69-94.
24. Cleland-Huang J, Settimi R, BenKhadra O, Berezhanskaya E, Christina S,. Goal-centric traceability for managing non-functional requirements. In: Proceedings of the 27th International Conference on Software Engineering, 2005, ACM, New York, NY, USA, ICSE'05, pp. 362-371.
25. McAvoy J, Butler T,. The role of project management in ineffective decision making within agile software development projects. EJIS 2009; 18 (4): 372-383.
26. Wohlin C, Aurum A,. What is important when deciding to include a software requirements in a project or release? In: Proceedings of the International Symposium on Empirical Software Engineering (ISESE 2005), 2005, pp. 246-255
27. Wnuk K, Regnell B, Karlsson L,. What happened to our features? Visualization and understanding of scope change dynamics in a large-scale industrial setting. In: Proceedings of the 17th IEEE International Requirements Engineering Conference (RE 2009), 2009a, pp. 89-98.
28. Barney S, Aurum A, Wohlin C,. A product management challenge: creating software product value through requirements selection. Journal of Systems Architecture-Embedded Systems Design 2008; 54 (6): 576-593.
29. Khatri N,. The role of intuition in strategic decision making. Human Relations 2000; 53 (1): 57-86.
30. Messerschmitt D,. Marketplace issues in software planning and design. IEEE Software 2004; 21 (3): 62-70.
31. Ruhe G, Saliu MO,. The art and science of software release planning. IEEE Software 2005; 22 (6): 47-53.
32. Bagnall AJ, Rayward-Smith VJ, Whittley IM,. The next release problem. Information and Software Technology 2001; 43 (14): 883-890.
33. Zur H, Breznitz S,. The effect of time pressure on risky choice behavior. Acta Psychologica 1981; 47 (2): 89-104.
34. Hallowell R,. The relationships of customer satisfaction, customer loyalty, and profitability: an empirical study. International Journal of Service Industry Management 1996; 7 (4): 27-42.
35. Lethbridge TC, Sim SE, Singer J,. Studying software engineers: data collection techniques for software field studies. Empirical Software Engineering 2005; 10: 311-341.
36. Cooper R,. Stage-gate systems: a new tool for managing new products. Business Horizons 1990; 33 (3): 44-54.
37. Leffingwell D, Widrig D,. Managing Software Requirements: A Use Case Approach (2nd edn). Pearson Education: Boston, USA, 2003.
38. Kitchenham BA, Travassos GH, von Mayrhauser A, Niessink F, Schneidewind NF, Singer J, Takada S, Vehvilainen R, Yang H,. Towards an ontology of software maintenance. Journal of Software Maintenance 1999; 11 (6): 365-389.
39. Natt och Dag J, Regnell B, Carlshamre P, Andersson M, Karlsson J,. Evaluating automated support for requirements similarity analysis in market-driven development. In: Proceeding of the 7th International Workshop on Requirements Engineering: Foundation for Software Quality (REFSQ'01), 2001, pp. 22-31.
40. Kotonya G, Sommerville I,. Requirements Engineering. John Wiley and Sons: New York, NY, USA, 1998.
41. Wnuk K, Regnell B, Schrewelius C,. Architecting and coordinating thousands of requirements-an industrial case study. In: Proceedings of the 15th International Working Conference on Requirements Engineering: Foundation for Software Quality, Springer-Verlag, Berlin, Heidelberg, REFSQ'09, 2009b, pp. 118-123.
42. Samalikova J, Trienekens J, Kusters R, Weijters A,. Discovering changes of the change control board process during a software development project using process mining. Software Process Improvement, Communications in Computer and Information Science, vol. 42, O'Connor R, Baddoo N, Cuadrago Gallego J, Rejas Muslera R, Smolander K, Messnarz R, (eds.). Springer: Berlin, 2009; 128-136.
43. Easterbrook S, Singer J, Storey MA, Damian D,. Selecting empirical methods for software engineering research. Guide to Advanced Empirical Software Engineering, Shull F, Singer J, Sjøberg D, (eds.). Springer: London, 2008; 285-311.
44. Hogarth R,. Decision time as a function of task complexity. Utility, probability, and human decision making. Selected Proceedings of an Interdisciplinary Research Conference, Rome, 3-6 September, 1973, 1975, pp. 321-338.
45. Saliu O, Ruhe G,. Supporting software release planning decisions for evolving systems. Proceedings of the 29th Annual IEEE/NASA Software Engineering Workshop, 2005, pp. 14-26.
46. Rajlich VT, Bennett KH,. A staged model for the software life cycle. Computer 2000; 33 (7): 66-71.
47. Runeson P, Höst M,. Guidelines for conducting and reporting case study research in software engineering. Empirical Software Engineering 2009; 14 (2): 131-164.
48. Yin R,. Case Study Research: Design and Methods. Sage Publications, Inc: New York, NY, USA, 2008.
49. Kitchenham B, Pfleeger S,. Principles of survey research part 2: designing a survey. ACM SIGSOFT Software Engineering Notes 2002; 27 (1): 18-20.
50. Paech B, Koenig T, Borner L, Aurum A,. An analysis of empirical requirements engineering survey data. Engineering and Managing Software Requirements, Aurum A, Wohlin C, (eds.). Springer: Berlin, 2005; 427-452.
51. Jacoby J, Matell M,. Three-point Likert scales are good enough. Journal of Marketing Research 1971; 8 (4): 495-500.
52. Wnuk K,. The survey questions can be
53. Wohlin C, Höst M, Runeson P, Ohlsson M, Regnell B, Wesslén A,. Experimentation in Software Engineering: An Introduction. Kluwer Academic Pub: Norwell, MA, USA, 2000.
54. Ott R, Longnecker M,. An Introduction to Statistical Methods and Data Analysis. Cengage Learning: Belmont, CA, USA, 2008.
55. Sheskin D,. Handbook of Parametric and Nonparametric Statistical Procedures. CRC Pr I Llc: London, UK, 2004.
56. Field A,. Discovering Statistics Using SPSS. Sage Publications Ltd: London, UK, 2009.
57. 1. Biometrika 1973; 60 (3): 613.
58. DeCarlo L,. On the meaning and use of kurtosis. Psychological Methods 1997; 2 (3): 292-307.
59. Stevens S,. On the theory of scales of measurement. Science 1946; 103 (2684): 677-680.
60. Spearman C,. General intelligence: objectively determined and measured. The American Journal of Psychology 1904; 15 (2): 201-292.
61. Wnuk K, Regnell B, Berenbach B,. Scaling up requirements engineering-exploring the challenges of increasing size and complexity in market-driven software development. In: Proceedings of the 17th International Working Conference on Requirements Engineering: Foundation for Software Quality, Springer-Verlag, Berlin, REFSQ'11, 2011, pp. 54-59.
62. Garcia-Retamero R, Hoffrage U,. How causal knowledge simplifies decision-making. Minds and Machines 2006; 16 (3): 365-80.
63. Student B,. The probable error of a mean. Biometrika 1908; 6 (1): 1-25.
64. Cramér H,. Mathematical methods of statistics. Princeton Landmarks in Mathematics and Physics. Princeton University Press: Princeton, USA, 1945.
65. Taylor CA, Miransky AV, Madhavji NH,. Request-implementation ratio as an indicator for requirements prioritisation imbalance. In: 2011 5th International Workshop on Software Product Management, IWSPM 2011-Part of the 19th IEEE International Requirements Engineering Conference, Trento, Italy, 2011, pp. 3-6.
66. Smirnov N,. On the estimation of the discrepancy between empirical curves of distribution for two independent samples. Bulletin Mathematics University Moscow 1939; 2: 3-14.
67. Sharp B, Dawes J,. What is differentiation and how does it work ? Journal of Marketing Management 2001; 17 (7-8): 739-759.
68. Brooks FP Jr,. The Mythical Man-month (anniversary edn). Addison-Wesley Longman Publishing Co., Inc: Boston, MA, USA, 1995.