Identification and documentation of the need for a change in a change request 2. Analysis and evaluation of a change request and production of a change proposal 3. Approval or disapproval of a change proposal 4.
The Configuration Control Process Why Configuration Control is Important Configuration control is an essential component of a project's risk management strategy. Scenario - Curse of the Feature Creep A project misses several key milestones and shows no sign of delivering anything. The customer regularly talks directly to software developers asking them to make 'little changes' without consulting the project manager.
The developers are keen to show off the new technology they are using. Connect with us. Sign up. Term of the Day. Best of Techopedia weekly. News and Special Offers occasional. Techopedia Explains Configuration.
What Does Configuration Mean? Techopedia Explains Configuration With the advent of plug and play technology, most configurations can be performed automatically in the case of software configurations. Share this Term. Like agile, configuration management gives teams the confidence to move quickly with their changes. Under agile practices, the company gives configuration management responsibilities to the development teams, empowering them to provision, configure, and manage their own infrastructure.
You build it, you run it. Pipelines usually involve steps such as linting code, unit testing code, integration testing code, and creating artifacts. A software pipeline therefore is a form of configuration management. When we build software with tools like Docker, we codify our build instructions into our Dockerfile.
This allows us to better understand the dependencies of our artifacts. Infrastructure-as-code or IaC for short is the practice of ensuring all provisioned infrastructure is done so through code. The purpose of IaC is to have a written record of which services exist, where they are located, and under what circumstance. Configuration management might choose to leverage aspects of IaC in order to achieve the full understanding of all the technology assets a company owns.
Continuous delivery is the process of ensuring that software is always in a releasable state. You can achieve this through heavy automation and testing. Continuous integration is the process of bringing separate software artifacts together into a single location on a frequent basis, for the purposes of verifying that the code integrates properly. Continuous integration tools, which are typically servers that run automation-testing suites, act as a form of configuration management by providing visibility into the steps required to set up and configure a given software artifact.
That should clear up some of your lingering questions about how configuration management fits with some practices or ideas that you might be using or are familiar with. Any discussion of configuration management would be incomplete, however, without a discussion about tooling.
But before we get to that, I need to quickly discuss a concept to consider when comparing tools. And the concept is declarative style. When it comes to software, having a declarative style means telling your software the end result you want and then letting the software do the work in figuring out the way to get there.
The opposite of the declarative style would be a procedural style, where instead of giving an end state, you give instructions on how to get there. You can think of it like this: declarative versus procedural is the difference between giving a friend your home address and giving them step-by-step instructions to get to your house from where they are.
But why is it important? Declarative style is important because configuration management is all about knowing the current state of your applications. There are many different tools for configuration management. In fact, it can get confusing, as there are tools that support configuration management without explicitly being configuration management tools. This does not necessarily mean that the PM takes delivery and acceptance of the Technical Data Package.
Attributes of the product baseline include:. The program office and developer share responsibility for planning, implementing and overseeing the Configuration Management process and its supporting activities.
The distribution of responsibilities between the program office and the developer varies, based on the acquisition strategy and the life-cycle phase. The PM approves the Configuration Management Plan and should ensure adequate resources are allocated for implementing Configuration Management throughout the life cycle.
In accordance with DoDI Technical Data Management Process.
0コメント