The software value map - An exhaustive collection of value aspects for the development of software intensive products

Journal of software: Evolution and Process

Volumn 25, Issue 7, 2013, Pages 711-741

  Khurum, Mahvish ^a   Gorschek, Tony ^a   Wilson, Magnus ^b  

^a BLEKINGE INSTITUTE OF TECHNOLOGY   (Sweden)

^b NONE   (Sweden)

Author keywords

Decision support; Product customization; Requirements engineering; Software engineering management; Software value; Software value analysis; Software value map; Technology and software product management; Value taxonomy; Value based software engineering

Indexed keywords

COMPETITION; DECISION SUPPORT SYSTEMS; PRODUCT DEVELOPMENT; REQUIREMENTS ENGINEERING;

DECISION SUPPORTS; PRODUCT CUSTOMIZATION; SOFTWARE ENGINEERING MANAGEMENT; SOFTWARE PRODUCT MANAGEMENT; VALUE BASED SOFTWARE ENGINEERING;

SOFTWARE DESIGN;

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

References (61)

1. Biffl S, Aurum A, Boehm B, Erdogmus H, Grunbacher P. Value-Based Software Engineering. Springer: Germany, 2006.
2. Jeffery R. Value-Based Software Engineering. Springer: Germany, 2006.
3. Halling M, Biffl S, Grünbacher P. The Role of Valuation in Value-Based Software Engineering. 6th International Workshop on Economics-Driven Software Engineering Research - Proceedings of 26th International Conference on Software Engineering Edinburgh, Scotland, 2004, 7-10.
4. Barry B. Value-based software engineering: reinventing. SIGSOFT Software Engineering Notes 2003; 28:3.
5. Gorschek T, Fricker S, Palm K, Kunsman S. A Lightweight Innovation Process for Software-Intensive Product Development. Software, IEEE 2010; 27:37-45.
6. Aurum A, Wohlin C, Porter A. Aligning Software Project Decisions: A Case Study. International Journal of Software Engineering and Knowledge Engineering 2006; 16:795-818. (Pubitemid 46181433)
7. Khurum M, Aslam K, Gorschek T. MERTS - A method for early requirements triage and selection utilizing product strategies. Asian Pacific Software Engineering Conference (APSEC) Nagoya Japan, 2007; 97-104.
8. Kontio J, Warsta J, Makela MM, Ahokas M, Tyrvainen P, Poyry P. Software business education for software engineers: Towards an integrated curriculum. Proceedings of Software Engineering Education Conference, Oahu, HI, United states, 2006.
9. Rönkkö M, Frühwirth C, Biffl S. Integrating Value and Utility Concepts into a Value Decomposition Model for Value-Based Software Engineering. Product-Focused Software Process Improvement. Lecture Notes in Business Information Processing: Springer, Berlin Heidelberg, 2009; 32:362-374.
10. Sward D. Measuring the Business Value of Information Technology. Practical Strategies for IT and Business Managers. Intel Press: Santa Clara, 2006.
11. Lei Z, Ren S, Garcia FP, Zuzhao L. Multiple-value decision supporting application in software production facing global market. IEEE International Conference on Systems, Man and Cybernetics, Piscataway, NJ, USA, 2000; 346-51.
12. Song M, Parry ME, Kawakami T. Incorporating network externalities into the technology acceptance model. Journal of Product Innovation Management 2009; 26:291-307.
13. Harmon RR, Laird G. Linking marketing strategy to customer value: implications for technology marketers. Portland International Conference on Management and Technology, Portland, OR, USA, 1997; 896-900.
14. Yongtae P, Gwangman P. A new method for technology valuation in monetary value: Procedure and application. Technovation 2004; 24:387-394.
15. ISO. ISO/IEC 9126-1, ISO/IEC 9126-2, ISO/IEC 9126-3. ISO, 2001.
16. Kim C-K, Lee D-H, Ko I-Y, Baik J. A lightweight value-based software architecture evaluation. Proceedings of Eighth ACIS International Conference on Software Engineering, Artificial Intelligence, Networking, and Parallel/Distributed Computing, 2007; 646-649.
17. Kazman R, Asundi J, Klein M.Making Architecture Design Decisions: An Economic Approach. Software Engineering Institute, Pittsburg, USA 2002.
18. Rappaport A. Creating shareholder value: A guide for Managers and Investors (2nd edn). The Free Press: New York, 1998.
19. Pasi O. Experiences of implementing a value-based approach to software process and product assessment. Proceedings of the 2nd WSEAS International Conference on Computer Engineering and Applications Acapulco, Mexico: World Scientific and Engineering Academy and Society (WSEAS), 2008.
20. Boehm B, Sullivan K. Software economics: status and prospects. Information and Software Technology 1999; 41:937-46. (Pubitemid 30544834)
21. Dakin K. Establishing a fair price for software. IEEE Software 1995; 12:105-6.
22. Finkelstein L, Leaning MS. A review of the fundamental concepts of measurement. Measurement 1984; 2:25-34.
23. Melton AC, Gustafson DA, Bieman JM, Baker AL. A mathematical perspective for software measures research. Software Engineering Journal 1990; 5:246-54.
24. Fenton N Software Metrics: A Rigorous Approach. London: Chapman-Hall, 1991.
25. Fenton N. Software measurement: a necessary scientific basis. IEEE Transactions on Software Engineering 1994; 20:199-206.
26. Bauer H, Hammerschmidt M, Braehler M. The Customer Lifetime Value Concept And Its Contribution To Corporate Valuation. EconWPA, 2004.
27. Hassenzahl M, Tractinsky N. User experiencea research agenda. Behaviour and Information Technology 2006; 25:91-97.
28. Wohlin C, Aurum A (eds). Engineering and managing software requirements. (1st edn) Springer: New York, NY, 2005.
29. Potts C. Invented Requirements and Imagined Customers: Requirements Engineering for Off-the-Shelf Software. Proceedings of the Second IEEE International Symposium on Requirements Engineering Los Alamitos, 1995; 128-130.
30. 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), Essen, Germany, 2003; 101-112.
31. Gorschek T, Wohlin C. Requirements Abstraction Model. Requirements Engineering journal 2006; 11:79-101.
32. Khurum M, Aslam K, Gorschek T. MERTS - A method for early requirements triage and selection utilizing product strategies. APSEC 2007 Nagoya Japan, 2007.
33. van de Weerd I, Brinkkemper S, Nieuwenhuis R, Versendaal J, Bijlsma L. Towards a reference framework for software product management. Los Alamitos, CA, USA, 2006; 312-15.
34. Seacord RC, Elm J, Goethert W, Lewis GA, Plakosh D, Robert J, Wrage L, Lindvall M. Measuring Software Sustainability. Proceedings of the International Conference on Software Maintenance: IEEE Computer Society, 2003.
35. Carlshamre P, Regnell B. Requirements Lifecycle Management and Release Planning in Market-Driven Requirements Engineering Processes. Proceedings of the 11th International Workshop on Database and Expert Systems Applications: IEEE Computer Society, 2000.
36. Potts C. Invented requirements and imagined customers: requirements engineering for off-the-shelf software. Proceedings of the Second IEEE International Symposium on Requirements Engineering: IEEE Computer Society, 1995.
37. Regnell B, Beremark P, Eklundh O. A market-driven requirements engineering process: Results from an industrial process improvement programme. Requirements Engineering 1998; 3:121-129.
38. Petticrew M, Roberts H. Systematic Reviews in the Social Sciences: A practical guide. Blackwell Publishing: Oxford, 2006.
39. Petersen K, Feldt R, Mujtaba S, Mattsson M. Systematic Mapping Studies in Software Engineering. 12th International Conference on Evaluation and Assessment in Software Engineering (EASE) University of Bari, Italy, 2008.
40. Khurum M, Gorschek T. The Software Value Map. http://www.bth.se/tek/aps/ mkm.nsf/pages/softaware-value-map. 2011.
41. Fleiss J. Measuring nominal scale agreement among many raters. Psychological Bulletin 1971; 76:378-382.
42. Robson C Real World Research. Blackwell Publishing: Cornwall, 1993.
43. Greenhalgh T, Peacock R. Effectiveness and efficiency of search methods in systematic reviews of complex evidence: audit of primary sources. BMJ - Information in Practice 2005.
44. Wohlin C, Runeson P, Höst M, Ohlson MC, Regnell B, Wesslén A. Experimentation in Software Engineering: An Introduction. Kluwer Academic: Boston MA, 2000.
45. Wohlin C, Runeson P, Host M, Ohlson MC, Regnell B, Wesslen A. Experimentation in Software Engineering: An Introduction. (6th edn) International Series in Software Engineering, Kluwer Academic, 2000.
46. Kitchenham BA. Guidelines for performing Systematic Literature Reviews in Software Engineering. Technical Report EBSE-2007-01, 2007.
47. Dieste O, Grimán A, Juristo N. Developing Search Strategies for Detecting Relevant Experiments for Systematic Reviews. Empirical Software Engineering 2009; 513-539.
48. Brereton P, Kitchenham BA, Budgen D, Turner M, Khalil M. Lessons from applying the systematic literature review process within the software engineering domain. Journal of Systems and Software 2007; 80:571-83. (Pubitemid 46329126)
49. Aurum A, Wohlin C. A Value-Based Approach in Requirements Engineering: Explaining Some of the Fundamental Concepts. 13th International Working Conference on Requirements Engineering: Foundation for Software Quality, Trondheim, Norway, 2007; 109-115.
50. Kaplan RS, Norton DP. The Balanced Scorecard - Measures that Drive Performance. Harvard Business Review, 1992.
51. Kaplan AS, Norton DP. The balanced scorecard: translating strategy into action. Business School Press: Boston, Harvard. United States of America, 1996.
52. Steven BD. Using the balanced scorecard process to compute the value of software applications. Proceedings of the 28th international conference on Software engineering Shanghai, ACM: China, 2006.
53. Liebowitz J, Suen CY. Developing knowledge management metrics for measuring intellectual capital. Journal of Intellectual Capital 2000; 1:54-67. (Pubitemid 33239256)
54. Webster J, Watson RT. Analyzing the Past to Prepare for the Future: Writing a Literature Review. MIS Quarterly 2002; 26.
55. Gamma E, Helm R, Johnson R, Vlissides JM. Design Patterns: Elements of Reusable Object-Oriented Software. Addison-Wesley, 1994.
56. Pettersson F, Ivarsson M, Gorschek T, Ohman P. A practitioner's guide to light weight software process assessment and improvement planning. Journal of Systems and Software 2008; 81:972-995. (Pubitemid 351540828)
57. Gorschek T, Davis AM. Requirements engineering: In search of the dependent variables. Information and Software Technology 2008; 50:67-75. (Pubitemid 350192225)
58. Gorschek T, Garre P, Larsson S, Wohlin C. Industry evaluation of the Requirements Abstraction Model. Requirements Engineering journal 2007; 12:163-190.
59. Simmons E. Requirements Triage: What Can We Learn from a "Medical" Approach? IEEE Software 2004; 21:86-88.
60. Davis AM. The art of requirements triage. IEEE Computer 2003; 36:42-49.
61. Khurum M, Gorschek T. A systematic review of domain analysis solutions for software product lines. Journal of Systems and Software 2009; 82:1982-2003.