This paper describes a model, denoted architectural software configuration management, that minimises the gap between software design and configuration management by allowing developers to do configuration- and version control of the abstractions and hierarchy in a software architecture. The model emphasises traceability and reproducibility by unifying the concepts version and bound configuration. Experiences with such a model, implemented in a prototype “Ragnarok”, from three real-life, small- to medium-sized, software development projects are reported. The conclusion is that the presented model is viable and “feels natural ” for software developers.
System Configuration Management: Ecoop'98 Scm-8 Symposium Brussels, Belgium, July 20–21, 1998 Proceedings, 1998, p. 67-74
Symposium on System Configuration Management. SCM-8, 1998