Introduction of a process maturity model for market-driven product management and requirements engineering

Journal of software: Evolution and Process

Volumn 24, Issue 1, 2012, Pages 83-113

  Gorschek, Tony ^a   Gomes, Andrigo ^b   Pettersson, Andreas ^c   Torkar, Richard ^a  

^a BLEKINGE INSTITUTE OF TECHNOLOGY   (Sweden)

^b Spidexa Technologies AB   (Sweden)

^c Anoto AB   (Sweden)

Author keywords

Market driven; Maturity model; Process assessment; Process improvement; Requirements engineering; Software product management; Technology product management

Indexed keywords

MARKET DRIVEN; MATURITY MODEL; PROCESS ASSESSMENTS; PROCESS IMPROVEMENT; PRODUCT MANAGEMENT; SOFTWARE PRODUCT MANAGEMENT;

COMMERCE; PRODUCT DEVELOPMENT; RATING; SOCIETIES AND INSTITUTIONS;

REQUIREMENTS ENGINEERING;

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

References (91)

1. Ruhe G, Greer D. Quantitative studies in software release planning under risk and resource constraints. Proceedings International Symposium on Empirical Software Engineering (ISESE). IEEE: Los Alamitos CA, 2003; 262-271.
2. Butscher SA, Laker M. Market-driven product development. Marketing Management 2000; 9(2):48-53.
3. Sommerville I. Software Engineering. Addison-Wesley: Essex, 2001.
4. Gorschek T, Wohlin C. Requirements abstraction model. Requirements Engineering Journal 2006; 11(1):79-101. (Pubitemid 43118936)
5. Fricker S, Gorschek T, Myllyperkiö P. Handshaking between software projects and stakeholders using implementation proposals. International Workshop on Requirements Engineering: Foundation for Software Quality, (Lecture Notes in Computer Science, vol. 4542), 2007; 144-159.
6. Regnell B, Brinkkemper S. Market-driven requirements engineering for software products. Engineering and Managing Software Requirements. Springer: New York NY, 2005.
7. Kotonya G, Sommerville I. Requirements Engineering: Processes and Techniques. Wiley: New York NY, 1998.
8. Wieringa R, Ebert C. Guest Editors' Introduction. Re'03: Practical requirements engineering solutions. IEEE Software 2004; 21(2):16-18.
9. Karlsson L, Dahlstedt Å, Natt och Dag J, Regnell B, Persson A. Challenges in market-driven requirements engineering-An industrial interview study. Proceedings of the Eighth International Workshop on Requirements Engineering: Foundation for Software Quality (REFSQ'02), 2003.
10. Kotler P, Armstrong G. Principles of Marketing. Prentice Hall: Upper Saddle River NJ, 2001.
11. Gorschek T, Davis A. Assessing the quality of requirements process changes. Proceedings of the 11th International Workshop on Requirements Engineering: Foundation for Software Quality (REFSQ'05), 2005; 101-112. Available at: http://gorschek.com/doc/publications.html [10 January 2011].
12. Lehmann DR, Winer RS. Product Management. McGraw-Hill: Boston MA, 2002.
13. Mintzberg H, Ahlstrand BW, Lampel J. Strategy Safari: A Guided Tour through the Wilds of Strategic Management. Free Press: New York NY, 1998.
14. Carlshamre P. Release planning in market-driven software product development: Provoking an understanding. Requirements Engineering 2002; 7(3):139-151.
15. Bray IK. An Introduction to Requirements Engineering. Addison-Wesley: Dorset, 2002.
16. Glass RL. Software Runaways. Prentice Hall: Upper Saddle River NJ, 1998.
17. Connolly TM, Begg CE. Database Systems: A Practical Approach to Design, Implementation and Management. Addison-Wesley: Harlow, 1998.
18. Jirotka M, Goguen JA. Requirements Engineering Social and Technical Issues. Academic Press: London, 1994.
19. van Buren J, Cook DA. Experiences in the adoption of requirements engineering technologies. Crosstalk-The Journal of Defense Software Engineering 1998; 11(12):3-10.
20. Sommerville I, Sawyer P. Requirements Engineering: A Good Practice Guide. Wiley: Chichester, 1999.
21. Davis AM. Software Requirements: Objects, Functions, and States. Prentice Hall: Englewood Cliffs NJ, 1993.
22. Weber M, Weisbrod J. Requirements engineering in automotive development: Experiences and challenges. IEEE Software 2003; 20(1):16-24.
23. Simmons E. Requirements triage: What can we learn from a 'Medical' approach? IEEE Software 2004; 21(4):86-88.
24. Davis AM. The art of requirements triage. IEEE Computer 2003; 36(3):42-49.
25. Wohlin C, Aurum A. Aligning requirements with business objectives: A framework for requirements engineering decisions. Proceedings of Requirements Engineering Decision Support Workshop, 2005.
26. Gorschek T, Davis A. Requirements engineering: In search of the dependent variables. Information and Software Technology 2008; 50(1-2):67-75. (Pubitemid 350192225)
27. Teece DJ. Managing Intellectual Capital: Organizational, Strategic, and Policy Dimensions. Oxford University Press: Oxford, 2000.
28. Sasaki T, Nagata A, Toyama R, Hirata T, Hasegawa K. Coevolution of patent strategy and product strategy. Portland International Conference on Management of Engineering and Technology (PICMET'01). IEEE: Los Alamitos CA, 2001; 481-484.
29. Ross SA, Westerfield R, Jordan BD. Essentials of Corporate Finance. McGraw-Hill: Boston MA, 2001.
30. CMMI-PDT, Capability Maturity Model Integration (CMMI-Dev), Version 1.3. CMMI for Development-Version 1.3 (CMU/SEI-2010-TR-033). Carnegie Mellon: Pittsburgh PA, 2010.
31. http://www.tickit.org/ [1 October 2002].
32. IEEE, Recommended Practice for Software Requirements Specifications (Standard 830-1984). IEEE Press: New York NY, 1984.
33. Sawyer P, Kotonya G. Software Requirements. Guide to the Software Engineering Body of Knowledge Swebok, Trial Version 1.0. IEEE: Los Alamitos CA, 2001.
34. Kautz K, Hansen HW, Thaysen K. Applying and adjusting a software process improvement model in practice: The use of the ideal model in a small software enterprise. Proceedings International Conference on Software Engineering. IEEE: Los Alamitos CA, 2000; 626-633.
35. Beecham S, Hall T, Rainer A. Defining a requirements process improvement model. Software Quality Journal 2005; 13(3):247-279. (Pubitemid 41126274)
36. Gorschek T, Wohlin C. Packaging software process improvement issues-A method and a case study. Software: Practice & Experience 2004; 34(14):1311-1344.
37. Pettersson F, Ivarsson MTG. A practitioner's guide to light weight software process assessment and improvement planning. Journal of Systems and Software 2008; 81(6):972-995. (Pubitemid 351540828)
38. Wohlin C, Aurum A. (editors). Engineering and Managing Software Requirements. Springer: New York NY, 2005.
39. Potts C. Invented requirements and imagined customers: Requirements engineering for off-the-shelf software. Proceedings Second IEEE International Symposium on Requirements Engineering. IEEE: Los Alamitos CA, 1995; 128-130.
40. Regnell B, Beremark P, Eklundh O. A market-driven requirements engineering process-Results from an industrial process improvement programme. Requirements Engineering 1998; 3(2):121-129.
41. Balm GJ. Benchmarking and gap analysis: What is the next milestone? Benchmarking for Quality Management and Technology 1996; 3(4):28-33.
42. Loucopoulos P, Karakostas V. System Requirements Engineering. McGraw-Hill: New York NY, 1995.
43. Soffer P, Goldin L, Kuflik T. A unified reapproach for software product evolution: Challenges and research agenda. International Workshop (SREP'05) in conjunction with the IEEE 2005 International Requirements Engineering Conference. IEEE: Los Alamitos CA, 2005.
44. Dahlstedt A, Karlsson L, Persson A, NattochDag J, Regnell B. Market-driven requirements engineering processes for software products-A report on current practices. International Workshop on COTS and Product Software (RECOTS) in Conjunction with the 11th IEEE International Requirements Engineering Conference. IEEE: Los Alamitos CA, 2003.
45. Regnell B, Host M, Natt och Dag J, Hjelm T. An industrial case study on distributed prioritisation in market-driven requirements engineering for packaged software. Requirements Engineering 2001; 6(1):51-62.
46. Albrecht AJ, Gaffney JE. Software function, source lines of code, and development effort prediction. IEEE Transactions on Software Engineering 1983; SE-9(6):639-647.
47. Hihn J, Habib-agahi H. Cost estimation of software intensive projects: A survey of current practices. Proceedings 13th International Conference on Software Engineering. IEEE: Los Alamitos CA, 1991; 276-287. (Pubitemid 21689971)
48. Carlshamre P, Sandahl K, Lindvall M, Regnell B, Natt och Dag J. An industrial survey of requirements interdependencies in software product release planning. Proceedings Fifth IEEE International Symposium on Requirements Engineering. IEEE: Los Alamitos CA, 2001; 84-92.
49. Saaty TL, Vargas LG. Models, Methods, Concepts and Applications of the Analytic Hierarchy Process. Kluwer Academic Publishers: Boston MA, 2001.
50. Leffingwell D, Widrig D. Managing Software Requirements: A Unified Approach. Addison-Wesley: Reading MA, 2000.
51. Feather MS, Menzies T. Converging on the optimal attainment of requirements. IEEE Joint International Conference on Requirements Engineering. IEEE: Los Alamitos CA, 2002; 263-270.
52. Karlsson L, Berander P, Regnell B, Wohlin C. Requirements prioritisation: An experiment on exhaustive pairwise comparisons versus planning game partitioning. Proceedings Eighth International Conference on Empirical Assessment in Software Engineering (EASE 2004) (Proceedings ICSE 2004). IEEE: Los Alamitos, 2004; 145-154.
53. Wiegers KE. Software Requirements. Microsoft Press: Redmond WA, 1999.
54. Kostoff RN, Schaller RR. Science and technology roadmaps. IEEE Transactions on Engineering Management 2001; 48(2):132-143. (Pubitemid 32512482)
55. Kappel TA. Perspectives on roadmaps: How organizations talk about the future. Journal of Product Innovation Management 2001; 18(1):39-50. (Pubitemid 32092785)
56. Gorchels L. The Product Manager's Handbook: The Complete Product Management Resource. NTC Business Books: Lincolnwood IL, 2000.
57. Gorschek T, Svahnberg M, Borg A, Börstler J, Eriksson M, Lonconsole A, Sandahl K. A controlled empirical evaluation of a requirements abstraction model. Information and Software Technology 2007; 49:790-805. (Pubitemid 46754846)
58. Wohlin C, Aurum A. What is important when deciding to include a software requirement in a project or release? International Symposium on Empirical Software Engineering, 2005; 237-246.
59. Vähäniitty J, Lassenius C, Rautiainen K. An approach to product roadmapping in small software product businesses. Seventh European Conference on Software Quality, Conference Notes, 2002; 12-13.
60. Carlshamre P, Regnell B. Requirements lifecycle management and release planning in market-driven requirements engineering processes. Proceedings 11th International Workshop on Database and Expert Systems Applications. IEEE: Los Alamitos CA, 2000; 961-965.
61. Greer D, Ruhe G. Software release planning: An evolutionary and iterative approach. Information and Software Technology 2004; 46(4):243-253.
62. Regnell B, Karlsson L, Host M. An analytical model for requirements selection quality evaluation in product software development. Proceedings 11th International Conference on Requirements Engineering. IEEE: Los Alamitos CA, 2003; 254-263.
63. Karlsson L, Regnell B, Karlsson J, Olsson S. Post-release analysis of requirements selection quality-An industrial case study. Proceedings of the Ninth International Workshop on Requirements Engineering: Foundation for Software Quality (REFSQ'03), 2003; 47-56.
64. Redling TJ. A methodology for developing new product line requirements through gap analysis. Proceedings 22nd Digital Avionics Systems Conference. IEEE: Indianapolis, 2003; 10.A.1-101-11.
65. Zairi M. Best Practice: Process Innovation Management. Butterworth-Heinemann: Boston MA, 1999.
66. Hill N, Brierley J, MacDougall R. How to Measure Customer Satisfaction. Gower, Aldershot: Brookfield, 1999.
67. Kotler P, Armstrong G, Saunders J, Wong V. Principles of Marketing. Prentice Hall: New York NY, 2002.
68. Davis A, Bersoff E, Comer E. A strategy for comparing alternative software development life cycle models. IEEE Transactions on Software Engineering 1998; 14(10):1453-1461.
69. Deifel B. A process model for requirements engineering of ccots. 10th International Workshop on Database and Expert Systems Applications. IEEE: Los Alamitos, 1999; 316-321.
70. Hass AMJ. Configuration Management Principles and Practice. Addison-Wesley: Reading MA, 2003.
71. Höst M, Regnell B, Nattoch Dag J, Nedstam J, Nyberg C. Exploring bottlenecks in market-driven requirements management processes with discrete event simulation. Proceedings of PROSIM'00, 2000.
72. Yeh AC. Requirements engineering support technique (Request): A market driven requirements management process. Proceedings Second Symposium on Assessment of Quality Software Development Tools. IEEE: Los Alamitos CA, 1992; 211-223.
73. Dahlstedt Å, Persson A. Requirements interdependencies-Molding the state of research into a research agenda. Ninth International Workshop on Requirements Engineering: Foundation for Software Quality (REFSQ'03), 2003; 71-80.
74. Davis AM. Just Enough Requirements Management: Where Software Development Meets Marketing. Dorset House Publications: New York NY, 2005.
75. Rautiainen K, Lassenius C, Pyhajarvi MA, Vanhanen JA. A tentative framework for managing software product development in small companies. Proceedings of the 35th Annual Hawaii International Conference on System Sciences, 2002; 3409-3417.
76. http://www.sqi.gu.edu.au/spice/ [11 September 2003].
77. Berry M. Strategic planning in small high tech companies. Long Range Planning 1998; 31(3):455-466. (Pubitemid 128550919)
78. Gorschek T. Requirements Engineering Supporting Technical Product Management. Blekinge Institute of Technology: Karlskrona, 2006.
79. Gorschek T, Garre P, Larsson L, Wohlin C. A model for technology transfer in practice. IEEE Software 2006; 23(6):88-95. (Pubitemid 44824162)
80. Gorschek T, Svahnberg M, Tejle K. Introduction and application of a lightweight requirements engineering process evaluation method. Proceedings of the Ninth International Workshop on Requirements Engineering: Foundation for Software Quality (REFSQ'03), 2003; 101-112. Available at: http://gorschek.com/ doc/publications.html [10 January 2011].
81. Gorschek T, Svahnberg M. Requirements Experience in Practice: Studies of Six Companies. Engineering and Managing Software Requirements. Springer: New York NY, 2005.
82. Calvo-Manzano Villalón JA, Cuevas Agustín G, San Feliu Gilabert T, De Amescua Seco A, García Sánchez L, Pérez Cota M. Experiences in the application of software process improvement in Smes. Software Quality Journal 2002; 10(3):261-273.
83. Kuilboer JP, Ashrafi N. Software process and product improvement: An empirical assessment. Information and Software Technology 2000; 42(1):27-34. (Pubitemid 30530284)
84. Reifer DJ. The CMMI: It's formidable. Journal of Systems and Software 2000; 50(2):97-98.
85. Zahran S. Software Process Improvement: Practical Guidelines for Business Success. Addison-Wesley: Reading MA, 1998.
86. Robson C. Real World Research: A Resource for Social Scientists and Practitioner-Researchers. Blackwell Publishers: Oxford, 2002.
87. Gomes A, Pettersson A. Market-driven requirements engineering process model-MDREPM. Master Thesis in Software Engineering, Blekinge Institute of Technology, Ronneby, 2007. Available at: http://www.bth.se/fou/cuppsats.nsf/ [10 January 2011].
88. Johnson G, Scholes K. Exploring Corporate Strategy: Text and Cases. Prentice Hall: New York, 1993.
89. CMMI-PDT. Capability Maturity Model Integration (CMMI), Version 1.1. CMMI for Systems Engineering, Software Engineering, Integrated Product and Process Development, and Supplier Sourcing Version 1.1 (CMMISE/ SW/IPPD/SS, V1.1), Pittsburgh PA, 2002.
90. Gorschek T, Fricker S, Palm K, Kunsman S. Star search-A light-weight innovation process for software intensive product development. IEEE Software 2010; 27(2):72-80.
91. Gorschek T, Garre P, Larsson S, Wohlin C. Industry evaluation of the requirements abstraction model. Requirements Engineering Journal 2007; 12(3):163-190. (Pubitemid 351802339)