* 4.0 CONFIGURATION MANAGEMENT (CM) Configuration management plan mainly in purpose of provide overview of the organization, activities, overall tasks, and objectives of Configuration Management for the Red Modani Shoes Inventory System. CM enhances productivity and boosts application quality because it automatically versions files, labels and organizes them as they change during the development process. It’s commonly used in software development groups in which several developers are concurrently working on a common set of files. For example, if two developers change the same file, that file might be overwritten and critical code changes lost. Software configuration management systems are designed to avoid this inherent problem with sharing files in a multiuser environment. Besides, CM is also to identify the organization providing the configuration control, define what a configuration-controlled item is, describe the change control process, and identify the plan for configuration status accounting and verification. CM activities include:
1. Change management An approach to shifting or transitioning individuals, teams, and organizations from a current state to a desired future state. It is an organizational process aimed at helping change stakeholders to accept and embrace changes in their business environment. In some project management contexts, change management refers to a project management process wherein changes to a project are formally introduced and approved.
2. Version management
Version management is to keep track of the multiple versions of system components and ensuring that changes made to components by different developers do not interfere with each other.
3. System buildings
This is the process of assembling program components, data and libraries, then compiling these to create an executable system.
4. Release management A relatively new but rapidly growing discipline within software engineering of managing