Abstract
The Configuration Management (CM) is a very important area of concentration in software development and maintenance processes. Quality parameters for Configuration Management Tools' architectural designs require rigorous identification and measurement. Two methods for quantitative assessment of quality parameters of the software architectures are proposed. These methods are based upon modularization properties, like, cohesion type, coupling type, module complexity, module size and others. Looking at the problems with the studied tools, like, low flexibility, interoperability, etc., and recent requirements for the CM tools, a new architectural model has been proposed[1]. All the three models are assessed on quality parameters applying both the methods with an objective to validate the superiority of the proposed model.
Highlights
Software Configuration Management (SCM) is the supportive activities, which go along the whole software development and maintenance cycles
As per the relationship between McCall’s software quality factors and quality metrics[2], we find that flexibility and testability are dependent on the complexity this is in addition to their primary dependency on modularity, so for their ratings CMPX and MOD both are incorporated
We introduce another metrics COM, which will indicate logical simplicity and strength of modularization of a module: Rating (COM) = sqrt ((10-CMPX)*MOD), if module coupling and/or fan-out information is not available at architectural design level, we will use M1 instead of MOD
Summary
Software Configuration Management (SCM) is the supportive activities, which go along the whole software development and maintenance cycles. SCM takes care of making the changes in a managed way. Some of the fundamental activities of software configuration management are configuration identification, version control, change control, status accounting and reporting, and configuration audits. Configuration identification and version control deals with storing software process artifacts with proper version numbers in a data bank called repository. Change control deals with making changes in the established artifacts in a systematic way. Status accounting and reporting works regard storing information, like, when the change was made, who made the change, etc. CM audits verify and validate that the changes have been made as desired
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
