{'fraction_non_alphanumeric': 0.016016016016016016, 'fraction_numerical': 0.0, 'mean_word_length': 5.410256410256411, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
A configuration management model for software product line

Software Product Line has proved to be an effective approach to benefit from software reuse. Configuration management, an integral part of any software development activity, takes on a special significance in software product line context. This is due to the special property of software product line, in which the core assets are shared by all products. In this paper, we compare the existing configuration management models and analyze the artifacts that need to be configuration managed in software product line. We then present an evolution-based configuration management model for software product line, in which, the configuration management is divided into two domains, the production domain and the product domain. In this model, the evolution propagation of corrective changes and enhancement changes on different configuration artifacts follow different paths. The advantages and the constraints of this model are also discussed.