You are here: Home Blogs Configuration Management
Error
  • JUser: :_load: Unable to load user with ID: 62
Thursday, 25 January 2007 17:41

Configuration Management

Written by 
Rate this item
(0 votes)

Configuration management is the term given to the identification, tracking and managing of all the assets of a project; it focuses on controlling the characteristics of a product or service (also referred to as deliverables). In a general sense, configuration management consists of the following:

 

  • The documentation of the features, characteristics, and functions of a product or service
  • The applied control to restrict changes to the features, characteristics, and function of the product or service
  • The process of documenting any changes to the product or service
  • The ongoing auditing of products and services to ensure their conformance to documented requirements
  • Establishes a method to consistently identify and request changes to established baselines
  • To assess the value and effectiveness of changes
  • Provides opportunities to continuously validate and improve the project by considering the impact of each change
  • Provides the mechanism for the project management team to consistently communicate all changes to the stakeholders.

 

Configuration management activities included in the integrated change control process are:

  • Configuration Identification - Providing the basis from which the configuration of products is defined and verified, products and documents are labeled, changes are managed, and accountability is maintained.
  • Configuration Status Accounting - Capturing, storing, and accessing configuration information needed to manage products and product information effectively.
  • Configuration Verification and Auditing - Establishing that the performance and functional requirements defined in the configuration documentation have been met.

When it comes to configuration management, think paperwork. Think about all the paperwork that is involved in documenting every single component of a system deliverable and making sure that there are no changes to that deliverable, or if there are changes, that they are thoroughly documented. Configuration management is traceable. For the exam, know that all change must be screened, tracked, accepted, approved, and the development process updated thereafter.

 

Read 4371 times Last modified on Wednesday, 29 April 2009 13:15

Login to post comments

News and Promotions

Keep up to date with the latest happenings by signing up for our newsletter. Subscribe below.

Twitter Update

Who's Online

We have 731 guests and no members online

Got something to say?