Gerco Ballintijn

A process model and typology for software product updaters

Product software is constantly evolving through extensions, maintenance, changing requirements, changes in configuration settings, and changing licensing information. Managing evolution of released and deployed product software is a complex and often underestimated problem that has been the cause of many difficulties for both software vendors and customers. This paper presents a process model and typology to characterize techniques that support product software update methods. Also, this paper assesses and surveys a variety of existing techniques against the characterization framework and lists unsolved problems related to software product updaters.

Integrated development and maintenance for the release, delivery, deployment, and customization of product software: a case study in mass-market ERP software

SUMMARY The maintenance of enterprise application software at a customer site is a complex task for software vendors. This complexity results in a significant amount of work and risk. This article presents a case study of a product software vendor that tries to reduce this complexity by integrating product data management (PDM), software configuration management (SCM), and customer relationship management (CRM) into one system. The case study shows that by combiningthese management areas in a single software knowledge base, software maintenance processes can be automated and improved, thereby enabling a software vendor of enterprise resource planning software to serve a large number of customers with many different product configurations. Copyright c � 2006 John Wiley & Sons, Ltd. Received 26 September 2005; Revised 29 November 2005; Accepted 16 December 2005

Integrated development and maintenance of software products to support efficient updating of customer configurations: a case study in mass market ERP software

The maintenance of enterprise application software at a customer site is a potentially complex task for software vendors. This complexity can unfortunately result in a significant amount of work and risk. This paper presents a case study of a product software vendor that tries to reduce this complexity by integrating product data management (PDM), software configuration management (SCM), and customer relationship management (CRM) into one system. The case study shows that by combining these management areas in a single software itnowledge base, software maintenance processes can be automated and improved, thereby enabling a software vendor of enterprise software to serve a large number of customers with many different product configurations.