International Journal of Network Security & Its Applications (IJNSA) Vol.7, No.1, January 2015 DOI : 10.5121/ijnsa.2015.7103 29 SERVICE ORIENTED CONFIGURATION MANAGEMENT OF SOFTWARE ARCHITECTURE Razie Alidoosti 1 , Shahrouz Moaven 2 and Jafar Habibi 3 1,2,3 Department of Computer Engineering, Sharif University of Technology ABSTRACT Software configuration management (SCM) is an important activity in the software engineering life cycle. SCM by control of the evolution process of products leads to constancy and stability in software systems. Nowadays, use of software configuration management is essential during the process of software development as rules to control and manage the evolution of software systems. SCM effects different levels of abstraction included the architectural level. Configuration of software architecture causes improvement in the configuration of the lower abstraction levels. CM of software architecture is more significant in large scale software with longevity of life cycle. Traditional SCM approaches, at the architectural level, do not provided the necessary support to software configuration management, so systems that use these approaches are faced with problems. These problems arise because of the lack of a serious constant and repeated changes in the software process. To overcome this it is necessary to create an infrastructure. Hence, a service oriented approach for configuration management is presented in this paper. In this approach, the activities of configuration management are conducted from a service oriented viewpoint. This approach was also used to try and control the evolution and number of versions of different software systems in order to identify, organize and control change and reforms during the production process. This approach can compose services and create composite services for new undefined activities of configuration. KEYWORDS Software configuration management, Service-oriented approach, Version control 1.INTRODUCTION The ability to manage the evolution of software architecture is an important issue in the domain of software engineering. In this regard, many methods have been proposed for logical level software systems. These methods present the relationship between the concepts of software configuration management and software architecture [1]. Configuration management for each domain should adopt a comprehensive strategy that includes a set of rules and policies for the specific field. Configuration management of software architecture demands special considerations. Not only is there revision or change management based on the components, connectors, and their governing rules; but the same discussion is also necessary for architectural artifacts such as software documents, directories, etc. In other words, since there is the possibility of changes being made to