Views

Enterprise:Engineering:SCM

Contents

Navigation

Home · Main Page · Enterprise  ·


Related categories



About this page

We apologize for that little information on this page, which is still under construction. Please stay tuned.
Image:Construction_worker.gif

Configuration management resources

Configuration management is a must in various areas and is important for several reasons:
  • Quality management frameworks include configuration management as a key process area to be audited for
  • Quality management practices create the need for versioning, baselining and change control in product-delivery activities
  • All engineering practices create the need for versioning, baselining and change control for product documentation
  • Operational best-practices, e.g. ITIL, insist on using configuration- and change-control procedures for service-delivery activities
  • Information security best practice recommend using configuration auditing and management procedures


CMII

Configuration management is much more than properly using a configuration management toolset but a base component of many business processes that span all engineering disciplines. In fact multifaceted elements of Configuration management can be found under various names in many business processes. The basic cyclic lifecycle associated with project management and product development is "plan-do-check-act" and involves accomodation of changes at all levels. The role of Configuration management elements in all these processes is to increase information integrity, minimize rework and improve overall efficiency. The CMII initiative all these elements are brought together and understood in order to improve the overall efficiency of the business infrastructure, in terms of:
  • Requirements Management
  • Change Management
  • Release Management
  • Data Management
  • Records Management
  • Document Control
  • Part library Management


CMII approach tries to optimize the heavy-weight configuration- and change-management processes recommended by standards as ISO 10007 or IEEE 1042. Instead CMII proposes a fast-track approach by recognizing that Configuration Management, is much more than a supporting process. Instead, it spans across all business infrastructure, being a core, integrating process for all other business processes. The availability of suitable software tools is essential for implementing CMII processes. The CMII Research Institute is responsible for certifying such software tools as CMII Compliant.

Individual certifications are granted by the CMII Research Institute:
  • CMII Certified - basic certification in CMII practice
  • CMII Professional - highest level of individual CMII certification
  • CMII Provider - an organization entitled to assist and advise clients with their CMII implementation


A large number of corporations are currently interested in reengineering their business processes according to CMII recommended practices.

Resources on CMII
  • CMII World - access to international CMII training schedules [1]
  • CMII Self Assessment questionnaire [2]
  • CMII whitepapers [3]
  • The CMII Model [4]
  • The Institute of Configuration Management and CMII [5]
  • The CMII user group : CMII user group


Configuration and Change management in Engineering practice

Other engineering practices than the software-engineering one (where the idea of configuration management originated) take advantage from incorporating Change- and Configuration-Management. All engineering practices that intervene in a product life-cycle, as well as the associated project management practices, need in a form or another to track all the product-associated information, from the drawing board to the production floor. This is actually much larger as scope and quite different than the Configuration- and Change-Management disciplines applicable in Software Engineering and IT Service Management.

Product Data Management (PDM)

The Product Data Management (PDM) discipline is about managing relationships and changes for all engineering data defining a product, like:
  • Requirements, specifications and engineering change requests
  • Engineering drawings and CAD artifacts
  • Bill of materials


Implementing Product Data Management practices along the entire Product LifeCycle help organizations to reduce costs and expedite product delivery. Most software tools for engineering (e.g. CAD tools) provide to different degrees Configuration Management and Change Control capabilities, for instance those from Autodesk and SolidWorks.

References:
  • Product Data Management on Wikipedia [6]
  • Product Data Management links [7]
  • Raven Configuration Management and Product Data Management [8]


Product Information Management (PIM)

The Product Information Management (PIM) practice is about providing complete, consistent and updated product information over a variety of internal and external channels and in different formats. As this information may have a large volume and be scattered across an organization's functional units, the need arises to efficiently consolidate, categorize, identify and manage change for this information. The Product Information Management discipline is to be found under various other names like [Master Data Management] (MDM) or Product Catalog Management (PCM).

References:
  • Product Information Management on Wikipedia [9]
  • Product Information Management tools [10]


Configuration Management in IT Operations

The best practices in IT operations and service delivery are generally governed by the ITIL framework and its kins:

The configuration and change management pocesses are integral part of ITIL disciplines in the "Service Support" area. The IT Service Management (ITSM) Configuration Management process is structured around the Configuration Management Database (CMDB). The Change Management within ITSM is an IT Service Management discipline, defining standardized processes, methodologies and procedures for controlling, coordinating and efficiently handling of changes in IT production environments.

References
  • ISO 20000 overview and relation to ITIL [11]
  • Configuration Management within IT Service Management [12]
  • Change management within IT Service Management [13]
  • Self Assessment guides for ITIL compliance of process-support tools [14]
    • Mandatory Change Management criteria [15]
    • Mandatory Configuration Management criteria [16]
    • Mandatory Release Management criteria [17]
  • IT Service Management: Configuration Management [18]


Configuration management requirements

Quality Management frameworks set forth requirements on auditing Configuration Management processes within an organization.

CMMI

  • 5 STEPS OF CONFIGURATION MANAGEMENT FUNCTIONALITIES [19]
  • Configuration Management process area in CMMI [20]
  • Configuration Management & Change Management - NDIA CMMI presentation [21]


ISO

The ISO 9001:2000 sub-clause 7.5.3, under "7.5 Production and Service provision", set forth a requirement for "identification and traceability". However, this is deemed a conditional requirement, up to the organization to decide whether this is a required process to be considered or not. A Traceability Matrix correlates versioned artifact sets according to a many to many relationship, e.g. requirements
  • ISO 9001:2000 SELF ASSESSMENT CHECKLIST [22]
  • The ultimate SME implementation guide for ISO 9001:2000 [23]


Configuration management practice

References:
  • Traceability matrix primer [24]
  • DOE Change & Configuration management guidelines [25]
  • ISPW eSCM - Enterprise Software Change Management [26]
  • Baselines in Configuration Management [27]
  • Training for Small and Medium Enterprises on CONFIGURATION MANAGEMENT [28]
    • The Four plus One Functions of CM [29]
    • Establishing a Configuration Management Organization [30]
    • Index of CM and Software Life-cycle Standards publicly available [31]
  • CHAPTER 7 fo SWEBOK - SOFTWARE CONFIGURATION MANAGEMENT [32]
  • Change Control and Change Control and Configuration Management [33]
  • Assembling Configuration Management Environments - Brad Appleton page on CM best practices [34]
  • European Space Agency guidelines for Configuration Management [35]
  • Electronic Records Archive (ERA) Configuration Management Plan (CMP) [36]
  • DCII Release Management Plan and guidelines [37]
  • Software Configuration Management (SCM) Security [38]


CM Standards

The ISO 10007:1995 "Quality Management — Guidance for Configuration Management" and then the revised ISO 1007:2003 "Quality management systems -- Guidelines for configuration management" are similar (and inspired by) MIL-STD-973 "Configuration Management". The standard defines the traditional CM process, consisting in planning, identification, change control, status accounting, reviews and audits.

References:
  • Complete list of CM standards [39]
  • ISO 9000 — Quality Management [40]
  • ISO/TC 176 Quality Management Standards [41]
  • Index of CM and Software Life-cycle Standards publicly available [42]
  • Sumary Report on Standards to Department of Energy (DOE) [43]


Configuration management standards



IEEE Standards

  • Standard for Software Configuration Management Plans IEEE STD 828-1990
  • Guide to Software Configuration Management IEEE STD 1042-1987


Configuration management tools

  • Configuration Management Tools Summary - by Dave Eaton [44]
  • List of revision control software [45]


CVS

CVS is a time-verified version-control system, based on RCS and enhanced with better tagging/branching
  • Configuration management using CVS [46]
  • CVS Links [47]
  • Configuration Management with CVS - Derek Clifford (RIP) local copy
  • Version Control - Distributed Systems, Lecture 7, Spring 2004. Henning Niss [48]
  • CVS Best Practices. Vivek Venugopalan [49]
  • Open Source Development with CVS - excellent eBook [50]
  • Chapter 14 - CVS and RCS - Linux in a Nutshell, 3rd Edition [51]
  • CVS Best Practices - Vivek Venugopalan [52]
  • CVS Primer [53]
  • André van der Hoek - Configuration Management and Open Source Projects [54]
  • CVS checkout over HTTP [55]
  • Conversion Scripts from other VC systems to CVS [56]
  • Running Arbitrary Scripts Under CVS [57], hooks for facilitating integration with other tools
  • Bugzilla-CVS integration scripts [58]
  • CVS integration with Eclipse [59]
  • Bonsai - a web-based graphical front-end for CVS queries [60]
  • Cervisia - a graphical CVS client front-end for Linux KDE [61]
  • Tortoise CVS - a Microsoft Windows Explorer CVS front-end plugin [62]
  • Tinderbox - a build-management system [63]


Subversion

  • Version Control with Subversion - official eBook [64]
  • "Unofficial" Version Control with Subversion 1.3 [65]
  • Version Control with Subversion 1.3 [66]
  • Basic Version Control with Subversion [67]
  • TortoiseSVN - A Subversion client for Windows [68]
  • Browser interface for CVS and Subversion [69]
  • SVN integration with Eclipse [70]
  • RapidSVN - a cross-platform GUI front-end for Subversion [71] (developer site)
  • Subversion tools directory [72]


PVCS

Serena Dimensions CM is a successor to Merant's Professional Version Control System (PVCS). It is part of Serena Dimensions 10, a software life-cycle management enterprise-class solution providing, beyond Configuration Management, the following functionality:
  • Project requirements management
  • Build and Release Management
  • Project visibility & traceability
Conversion of PVCS archives to CVS is possible, while preserving all history of changes, using the pvcs2cvs.pl script and locally-installed version of RCS and PVCS command-line utilities. The script is actually executing PVCS commands to retrieve all versions of each archived file from the PVCS archives and RCS commands to re-archive them in the CVS archive (CVS archives being RCS-compatible).

Clearcase

Clearcase is an advanced configuration control systems, allowing distributed multi-site implementations, automation of configuration-management and build tasks and granular access-control to archives. Clearcase administration is no trivial task, as it involves a significant amount of scripting, maintenance and user support and training. Once correctly set-up and its concepts well understood, Clearcase is easy to use, through a powerful graphical interface. The great advantage of Clearcase is that integrates smoothly with all other IBM/Rational support tools recommended by the Unified Process - Rational Rose, ClearQuest and RequisitePro.

References:
  • Clearcase documentation [73]
  • Eric J. Ostrander's ClearCase / ClearQuest pages [74]
  • Clearcase resources [75]


Other CM tools

  • Aegis, a transaction-based software configuration management system [76]


Configuration management resources

  • The Configuration Management Body of Knowledge [77]
  • Configuration Management and CMII Communities [78]
  • Configuration Management Wiki [79]
  • The Configuration Management Resource Guide [80]
  • Hot CM and related sites [81]
  • Brad Appleton's Software Configuration Management Links [82]
  • Software Engineering Research Laboratory (SERL) - CM resources [83]
  • Versioning and Configuration Management of WWW Content [84]
  • Configuration Management Yellow Pages [85]
  • Software Configuration Management (SCM) resources at SEI [86]
  • The online community of CM professionals [87]
  • Configuration Management sources [88]