Technology Configuration Management Principles And Practice Pdf


Saturday, May 11, 2019

Configuration Management Principles and Practice explains the elements and benefits of a sound CM strategy and shows how to put that strategy into action. This paper identifies fundamental principles and practices essential to the Secondary purposes for identifying the configuration management principles and . Configuration management principles and practice / Anne Mette Jonassen Hass. p. cm. Includes bibliographical references and index.

Configuration Management Principles And Practice Pdf

Language:English, Spanish, German
Published (Last):27.07.2016
ePub File Size:15.70 MB
PDF File Size:20.16 MB
Distribution:Free* [*Regsitration Required]
Uploaded by: LIZETTE

The Build Master: Microsoft's Software Configuration Management Best Practices · Read more Configuration Management Principles and Practice. The purpose of this Configuration Management Plan – CMP - is to identify the Principles for a configuration audit are established. .. of the CCB of the project is a member of the CCB and exercises control of . according to Anne Hass in her book/article “Configuration Management. Principles and Practice.” This paper will focus on five simple SCM best practices that.

Addison-Wesley Google Scholar [7] Babich, W.

Rules of the CMDB

Google Scholar [8] Jones, C. Google Scholar [9] Bersoff, E. Prentice-Hall Google Scholar [10] Whitgift, D. Wiley Google Scholar [11] Berlack, H. Google Scholar [12] Buckley, F. Google Scholar [13] Rigg, W. Integrating early and often becomes a challenge based on the size and time of software projects, even if developers are integrating on a frequent basis from their local workspaces.

Some development teams even try to avoid parallel development out of fear of merge problems later. Teams must choose the right SCM approach for fostering merging and integration. It ultimately comes down to several factors: Choosing the right branching and merging pattern branching patterns should make it easy for developers and team members to move and integrate code between different branches.

It should be easy and straight-forward to know where a change belongs at any given time. Enforcing merge rules and schedules developers should be able to create private workspaces and branches to allow them to create builds, releases and tests of code before they push those changes to other team members.

Gaining visibility into the merge process a straightforward pattern should give development teams the ability to know where to merge to and from, and when to push changes from one branch to another.

Software Configuration Management Best Practices

Ultimately it s up the team to decide on the frequency in which changes are integrated. There are SCM systems that automatically integrate a team s changes together in real time, this can be a huge benefit for teams that have parallel development needs.

Ultimately it s the team s responsibility to have visibility into that process and be responsible for code changes that should be shared with other team members.

Best Practice 3: Build and Release Frequently with Continuous Integration Taking several days to merge changes from one developer sandbox to another isn t fun or practical. Kent Beck, the creator of extreme Programing, developed the concept of Continuous Integration to address this very issue.

With Continuous Integration CI , code is integrated several times a day rather than just every night or once a week. Code doesn t have a chance to get stale in a private workspace.

In addition to integrating code, CI is the process of performing builds very frequently and doing some basic sanity tests on the build to know if it s good. With this type of rapid build cycle, teams can focus on incremental problems immediately and fix the problems instead of having to wait several days.

Configuration Management Best Practices

Software development organizations can incorporate software configuration management best practices when designing and implementing a continuous integration system to further reap its benefits.

These best practices include the following: Using an SCM system to store and version all source code this includes libraries, components and tests. Utilizing private developer workspaces developers should have a place to check in code, test and build before passing it off to the team.

Enabling local developer builds local build should function the same as the CI builds to avoid unnecessary problems. Frequently updating code in the SCM system make it easy for teams to update code with each other. Establishing a staging and isolation hierarchy create staging environments and branches for each environment or step of the process.

Automating builds at all stages in the hierarchy automate the build process with triggers and events. This practice should occur frequently enough that no intervening window remains between the SCM commit and the build, so that no errors can arise without developers noticing them and correcting them immediately.

This process is certainly easier when utilizing an SCM system with atomic commit capabilities. Best Practice 4: Create a Structure for Distributed Development Collaborating and sharing code with distributed teams is more complex than ever. Teams routinely perform software development in many locations and sometimes test or perform other tasks in another location. This distribution of teams strains the development process.

There are security auditing and integration problems throughout the process. Development teams must appear to be co-located while utilizing the same process, across teams with lower complexity. This means code integrations with other projects should happen in real time, so teams can give each other feedback immediately.

Navigation menu

The process must be visible to everyone to ensure they are all on the same page. Data Mining for Problem Management Engineers investigating incidents can mine conguration records to look for corresponding incidents when certain CIs are used in a certain way Enhance Ability to Rebuild In the event of a CI disaster, it is easier to rebuild if the nal production build is known.

If the nal build exists as a drive image, the new hardware can be matched to the last known good build and the image can be restored. Unlike manual processes, recovery can be completed in minutes. Assist with Budgeting Understanding the hardware and software involved in a given CI allows proper costing in the budget plan.

Costing information is also important for ensuring the rm has adequate insurance. Tracking CIs allows IT to rapidly report what capital assets are in use, being decommissioned, or transferred to other departments or divisions.

Assist with Licensing Understanding what software is deployed allows management to track how many tools are in production and properly manage license counts.

Firms want to have enough licenses to avoid legal disputes, but control spending by not having too many.Implementing configuration management: The research described in this publication was carried out at the Jet Propulsion Laboratory, California Institute of Technology, under a contract with the National Aeronautics and Space Administration.

Effective Teamwork, Practical Integration.

Wingerd, L. This distribution of teams strains the development process. The Source Code Control System. Capturing and disseminating the operating data to the various support organizations is becoming an industry in itself. These best practices include the following: Using an SCM system to store and version all source code this includes libraries, components and tests.

Google Scholar [13] Rigg, W.

One of the most important characteristics of Conguration Management is how it relates these CIs to one another.