Configuration Management

Get Started. It's Free
or sign up with your email address
Rocket clouds
Configuration Management by Mind Map: Configuration Management

1. is concerned with the policies, processes and tools for managing changing software systems(versions)

2. Software Configuration Item

2.1. Computer programs

2.2. Documentation

2.3. Data

3. Activities

3.1. Change Management

3.1.1. Change management is intended to ensure 1- system evolution is a managed process 2- and that priority is given to the most urgent and cost-effective changes.

3.1.2. The change management process is concerned with analyzing the costs and benefits of proposed changes, approving those changes that are worthwhile and tracking which components in the system have been changed.

3.1.3. The Change Management Process

3.1.4. Factors in Change Analysis ▶ The consequences of not making the change ▶ The benefits of the change ▶ The number of users affected by the change ▶ The costs of making the change ▶ The product release cycle

3.1.5. To avoid implementing change issues you need to email ur teammate for the changes or use dropbox You need to keep old files. You need a way to detect what changed in code and who made those changes. You need to be able to know what each of your team is working on You need a way to push changes you made on the code to your friends without affecting their work.

3.2. Version Management

3.2.1. Version Management Systems Features Version and release identification ex v2 2- Storage management Instead of keeping a complete copy of each version, the system stores a list of differences (deltas) Change history recording This involves tagging components with key words describing the changes made. Independent development make sure they do not interfere Project support Version Management Tools A category of software tools that help a software team manage changes to source code over time.

3.3. System Building

3.3.1. the process of creating a complete, executable system by compiling and linking the system components, external libraries, configuration files, etc.

3.4. Release Management

3.4.1. version of a software system that is distributed to customers.

3.4.2. For mass market software, it is usually possible to identify two types of release: Major releases which deliver significant new functionality Minor releases, which repair bugs and fix customer problems that have been reported.