The Community for Technology Leaders
RSS Icon
Issue No.04 - July/August (2009 vol.26)
pp: 84-90
Sebastian Barney , Blekinge Institute of Technology
Ganglan Hu , University of New South Wales
Aybüke Aurum , University of New South Wales
Claes Wohlin , Blekinge Institute of Technology
China has become a formidable player and continues to experience strong growth in a dynamic global market for software development. This highly competitive environment makes maximizing the creation of software product value both difficult and important. When looking at a software product, different stakeholder groups—purchasers, users, software managers, and developers—have different notions of value. This study examines the stakeholder perspectives and criteria used to select and prioritize software release requirements in three groups of software development companies: Chinese companies with a domestic market, Chinese companies with an international market, and Western companies operating in China. The results are similar for all three groups, except for after-sales support, which was a significantly greater concern for Chinese companies with an international market.
China, planning, market-driven software development, requirements analysis, requirements prioritization, requirements selection, scope definition, value-based requirements engineering, value-based software engineering
Sebastian Barney, Ganglan Hu, Aybüke Aurum, Claes Wohlin, "Creating Software Product Value in China", IEEE Software, vol.26, no. 4, pp. 84-90, July/August 2009, doi:10.1109/MS.2009.89
1. China Software 2005, Snapdata Int'l Group;
2. Strategic Research Report on the Development of the Chinese Software Industry, Chinalabs, 2006; .
3. H. Erdogmus, J. Favaro, and W. Strigel, "Return on Investment," IEEE Software, vol. 21, no. 3, 2004, pp. 18–22.
4. J. Favaro, "Value-Based Management and Agile Methods," Proc. 4th Int'l Conf. Extreme Programming and Agile Methods, LNCS 2675, Springer, 2003, pp. 16–25.
5. B.W. Boehm and K.J. Sullivan, "Software Economics: A Roadmap," Proc. Conf. Future Software Eng., ACM Press, 2000, pp. 319–343.
6. C. Wohlin and A. Aurum, "What Is Important When Deciding to Include a Software Requirement in a Project or a Release?" Proc. 4th Int'l Symp. Empirical Software Eng., IEEE Press, 2005, pp. 246–255.
7. S. Barney, A. Aurum, and C. Wohlin, "A Product Management Challenge: Creating Software Product Value through Requirements Selection," J. Systems Architecture, vol. 54, no. 6, 2008, pp. 576–593.
8. B. Boehm, "Value-Based Software Engineering: Overview and Agenda," Value-Based Software Engineering, S. Biffl et al., eds., Springer, 2006, pp. 3–14.
9. R. Peat, "Values Drive Value," , Univ. of Auckland Business Rev., vol. 5, no. 2, 2003, pp. 1–11.
10. W. Ahmed and B. Yannou, "Polysemy of Values or Conflict of Interests: A Multi-Disciplinary Analysis," Int'l J. Value-Based Management, vol. 16, no. 2, 2003, pp. 153–179.
11. D. Besanko, D. Dranove, and M. Shanley, Economics of Strategy, John Wiley &Sons, 2000.
12. B. Regnell et al., "An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software," Requirements Eng., vol. 6, no. 1, 2001, pp. 51–62.
13. V. Mummalaneni, K.M. Dubas, and C. Chao, "Chinese Purchasing Managers' Preferences and Trade-Offs in Supplier Selection and Performance Evaluation," Industrial Marketing Management, vol. 25, no. 2, 1996, pp. 115–124.
14. X. Zhao, J.H.Y. Yeung, and Z. Qiang, "Competitive Priorities of Enterprises in Mainland China," Total Quality Management, vol. 13, no. 3, 2002, pp. 285–300.
19 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool