Design preservation over subsequent releases of a software product: a case study of Baan ERP: Practice Articles

Authors:
Jilles van Gurp;Sjaak Brinkkemper;Jan Bosch
Affiliations:
Creative Online Development B.V., Nijmegen, The Netherlands;Institute of Information and Computing Sciences, University of Utrecht, Utrecht, The Netherlands;Nokia Research Center, FI-00045 Nokia Group, Finland
Venue:
Journal of Software Maintenance and Evolution: Research and Practice
Year:
2005

Citing 0
Cited 7

Functional architecture modeling for the software product industry

ECSA'10 Proceedings of the 4th European conference on Software architecture
Transforming trace information in architectural documents into re-usable and effective traceability links

Proceedings of the 6th International Workshop on SHAring and Reusing Architectural Knowledge
Causes of premature aging during software development: an observational study

Proceedings of the 12th International Workshop on Principles of Software Evolution and the 7th annual ERCIM Workshop on Software Evolution
Controlling software architecture erosion: A survey

Journal of Systems and Software
A tactic-centric approach for automating traceability of quality concerns

Proceedings of the 34th International Conference on Software Engineering
Variability points and design pattern usage in architectural tactics

Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
What can commit metadata tell us about design degradation?

Proceedings of the 2013 International Workshop on Principles of Software Evolution

Quantified Score

Hi-index	0.00

Visualization

Abstract

We present the results of two case studies we conducted at Baan in the Netherlands. At the time of conducting the case studies, Baan was part of Invensys plc. (Baan is now owned by SSA Global Technologies.) In these case studies we investigated how companies identify design erosion and address this in their software, a practice we call ‘design preservation’. In this study, we selected two sub-systems in Baan products that had recently been subjected to extensive maintenance activities because they were eroded. In this paper, we analyze the problems these systems had, how Baan identified that these systems were problematic, and the remedies that were used to address the problems. In addition to confirming some of our earlier conclusions, we have been able to extract some common causes for design erosion problems as well as a number of recommended design preservation practices, which, at least for Baan, have proven to be very effective in strengthening design preservation. Copyright © 2005 John Wiley & Sons, Ltd.