{'fraction_non_alphanumeric': 0.01707650273224044, 'fraction_numerical': 0.001366120218579235, 'mean_word_length': 5.751152073732719, '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 Change-Oriented Conceptual Framework Of Software Configuration Management

In the IT industry, software maintenance after system delivery is a major concern for any system development team. Software maintenance involves system updates for new customer requirements and error corrections within the delivered software. The management of maintenance is the service management of IT products, the cost of which can account for more than 50% of the total development budget. A major reason for the high cost is the changes brought about by the software updates and error corrections. Inconsistencies in the changes occurring in software development and service management afterwards cause confusion and misunderstanding, leading to further difficulties of maintenance, which enevitably result in further cost increases. To keep the consistency of software products and improve the service management in IT software products, software configuration management(SCM) is an approach. Here, a conceptual framework is set up to introduce relationships between the four areas of SCM and implement mandatory referential integrity between them within the software development stages, then maintain these enforced relationships between stages. It can set up rules to ensure mandatory integrity in changes, retaining consistency and improving Service Management. It is flexible enough to apply with any development models, waterfall, rapid prototyping, spiral development, etc.