Concepts of Product Software: Paving the Road for Urgently Needed Research

Software products are an everyday phenomenon. Yet, there are very few scientific studies reported on the engineering of software as a product in particular. This paper stipulates the urgent need for more research on product software. The various terms used for software products are reviewed and some categorizations of software products are presented. Moreover, we provide a software product development framework to position the key business domains in a product software company. From the perspective of the software product development framework, we evaluate the related work and provide directions for future research.

[1]  J. Vahaniitty,et al.  Product portfolio management in small software product businesses - a tentative research agenda , 2004, ICSE 2004.

[2]  Kimmo Alajoutsijärvi,et al.  Customer relationships and the small software firm: A framework for understanding challenges faced in marketing , 2000, Inf. Manag..

[3]  Michael A. Cusumano,et al.  Beyond the Waterfall: Software Development at Microsoft , 1995 .

[4]  Ian Sommerville,et al.  Improving Market-Driven RE Processes , 1999 .

[5]  Mika Mäntylä,et al.  Developing new approaches for software design quality improvement based on subjective evaluations , 2004, Proceedings. 26th International Conference on Software Engineering.

[6]  Jacky Estublier Software Configuration Management: ICSE SCM-4 and SCM-5 Workshops. Selected Papers , 1995 .

[7]  Erran Carmel,et al.  American Software Hegemony in Packaged Software and 'the Culture Software' , 1997, Inf. Soc..

[8]  BrynjolfssonErik The productivity paradox of information technology , 1993 .

[9]  Jyrki Kontio,et al.  A case study in applying a systematic method for COTS selection , 1996, Proceedings of IEEE 18th International Conference on Software Engineering.

[10]  Jim Buffenbarger,et al.  Syntactic Software Merging , 1995, SCM.

[11]  Lisa Brownsword,et al.  Developing New Processes for COTS-Based Systems , 2000, IEEE Softw..

[12]  Reijo Sulonen,et al.  4CC: A Framework for Managing Software Product Development , 2002 .

[13]  David J. Carney,et al.  What Do You Mean by COTS? Finally, a Useful Answer , 2000, IEEE Softw..

[14]  Reidar Conradi,et al.  Modelling Systems with Variability using the PROTEUS Configuration Language , 1995, SCM.

[15]  Jacky Estublier Software configuration management: a roadmap , 2000, ICSE '00.

[16]  B. Boehm,et al.  Reasoning About the Value of Dependability : The iDave Model , 2003 .

[17]  Steven Sawyer,et al.  Packaged software: implications of the differences from custom approaches to software development , 2000, Eur. J. Inf. Syst..

[18]  Björn Regnell,et al.  Speeding up requirements management in a product software company: linking customer wishes to product requirements through linguistic engineering , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[19]  Robert L. Glass,et al.  Contemporary Application-Domain Taxonomies , 1995, IEEE Softw..

[20]  Steve Sawyer,et al.  Software Development: Processes and Performance , 1998, IBM Syst. J..

[21]  Erik Brynjolfsson,et al.  The productivity paradox of information technology , 1993, CACM.

[22]  Jennifer L. Hartnett,et al.  Managing Quality: The Strategic and Competitive Edge , 1988 .

[23]  Barry Boehm,et al.  Avoiding the Software Model-Clash Spiderweb , 2000, Computer.

[24]  David Carney Assembling Large Systems from COTS Components: Opportunities, Cautions, and Complexities , 1997 .

[25]  Leslie Leong,et al.  Theoretical models in IS research and the technology acceptance model (TAM) , 2003 .

[26]  Stuart I. Feldman,et al.  Make — a program for maintaining computer programs , 1979, Softw. Pract. Exp..

[27]  Andrew Forward,et al.  Software documentation: Building and maintaining artefacts of communication. , 2002 .

[28]  Erran Carmel,et al.  A process model for packaged software development , 1995 .

[29]  Michael A. Cusumano,et al.  The Business of Software: What Every Manager, Programmer, and Entrepreneur Must Know to Thrive and Survive in Good Times and Bad , 2004 .

[30]  Susan Carlson Skalak House of Quality , 2002 .

[31]  Steve Sawyer,et al.  Packaged software development teams: what makes them different? , 1998, Inf. Technol. People.

[32]  Björn Regnell,et al.  Requirements lifecycle management and release planning in market-driven requirements engineering processes , 2000, Proceedings 11th International Workshop on Database and Expert Systems Applications.

[33]  Marco Torchiano,et al.  Definition and Classification of COTS: A Proposal , 2002, ICCBSS.

[34]  P. M. Rao,et al.  Growing importance of marketing strategies for the software industry , 1994 .

[35]  Paul Clements,et al.  Software architecture in practice , 1999, SEI series in software engineering.

[36]  Barry Boehm,et al.  Spiral Acquisition of Software-Intensive Systems of Systems , 2004 .

[37]  Laura Wingerd,et al.  Constructing a Large Product with Jam , 1997, SCM.

[38]  Abraham Seidmann,et al.  Two dimensions of software acquisition , 1996, CACM.

[39]  Alexis Tsoukiàs,et al.  IusWare: a methodology for the evaluation and selection of software products , 1997, IEE Proc. Softw. Eng..

[40]  Stefan Biffl,et al.  4.3.1 Formalizing Informal Stakeholder Requirements Inputs , 2003 .

[41]  T. B. Hilburn,et al.  Software engineering education: a modest proposal , 1997 .

[42]  Steve Sawyer,et al.  A market-based perspective on information systems development , 2001, CACM.

[43]  Martin Höst,et al.  An Industrial Case Study on Distributed Prioritisation in Market-Driven Requirements Engineering for Packaged Software , 2001, Requirements Engineering.

[44]  Marco Torchiano,et al.  Classifying COTS Products , 2002, ECSQ.

[45]  M. Ochs,et al.  A method for efficient measurement-based COTS assessment and selection method description and evaluation results , 2001, Proceedings Seventh International Software Metrics Symposium.

[46]  Björn Regnell,et al.  A linguistic-engineering approach to large-scale requirements management , 2005, IEEE Software.