Configuration management (CM) is a field of management that focuses on establishing and maintaining consistency of a system's or product's performance and its functional and physical attributes with its requirements, design, and operational information throughout its life.[1] For information assurance, CM can be defined as the management of security features and assurances through control of changes made to hardware, software, firmware, documentation, test, test fixtures, and test documentation throughout the life cycle of an information system.

1. Introduction to Software Configuration Management www.scmGalaxy.com scmGalaxy Author: Rajesh Kumar [email_address]

5. Intro to SCM: List of Components for Nova SCM The following page contains the list of the components of SCM.

16. Intro to SCM: Process Principle #1 The following four slides illustrate one of the most effective SCM process principles used in the BASA applications today. For applications that do not have a well-defined development process, implementing this principle will usually cut their defect rate significantly.

17. Intro to SCM: Process Principle #1 – The Right Way Access to modify code is only allowed in the Development State. There is no opportunity to circumvent the process downstream.

18. Intro to SCM: Process Principle #1 – The Right Way The Development Team has read-only access to the Test and subsequent environments. Once Code enters the Test State, it is not touched again by the Development Team.

19. Intro to SCM: Process Principle #1 – The Wrong Way Code moved from environment to environment without process circumvents the development process. Code should only be promoted through the Version Control Tool.

20. Intro to SCM: Process Principle #1 – The Right Way Code should only be promoted through the Version Control Tool, not from environment to environment.

26. www.scmGalaxy.com Thank You ! Author: Rajesh Kumar [email_address]