Introduction To Software Configuration Management
Upcoming SlideShare
Loading in...5
×
 

Introduction To Software Configuration Management

on

  • 7,836 views

Configuration management (CM) is a field of management that focuses on establishing and maintaining consistency of a system's or product's performance and its functional and physical attributes with ...

Configuration management (CM) is a field of management that focuses on establishing and maintaining consistency of a system's or product's performance and its functional and physical attributes with its requirements, design, and operational information throughout its life.[1] For information assurance, CM can be defined as the management of security features and assurances through control of changes made to hardware, software, firmware, documentation, test, test fixtures, and test documentation throughout the life cycle of an information system.

Statistics

Views

Total Views
7,836
Views on SlideShare
6,024
Embed Views
1,812

Actions

Likes
8
Downloads
205
Comments
1

9 Embeds 1,812

http://www.scmgalaxy.com 1768
http://www.slideshare.net 18
http://www.techgig.com 8
http://scmgalaxy.com 7
http://translate.googleusercontent.com 5
http://www.linkedin.com 2
https://www.linkedin.com 2
http://runonce.msn.com 1
http://115.112.206.131 1
More...

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Introduction To Software Configuration Management Introduction To Software Configuration Management Presentation Transcript

  • Introduction to Software Configuration Management www.scmGalaxy.com scmGalaxy Author: Rajesh Kumar [email_address]
  • Intro to SCM: Table of Contents
    • Purpose of This Presentation
    • General Definition of SCM
    • List of Components for SCM
    • Detailed Description of the SCM Components
  • Intro to SCM: Purpose of This Presentation
    • There are a number of definitions of SCM out there. Everyone has their own idea of what it means.
    • The purpose of this presentation is twofold:
      • to describe what is involved in Software Configuration Management (SCM) in the BASA environment, and
      • to help the SCM practitioner look beyond the SCM tasks to understand the spirit and reasoning behind those tasks and to learn to think in SCM terms.
  • Intro to SCM: General Definition of SCM in Nova
    • In general, the purpose of SCM is to manage and control changes to the Customer’s software assets.
    • This includes the following three principle areas:
      • Manage the Software Process,
      • Perform the Compile/Build Function for the Software, and
      • Packaging the Software for delivery into the Customer’s production environment.
  • Intro to SCM: List of Components for Nova SCM The following page contains the list of the components of SCM.
  • Intro to SCM: List of Components for Nova SCM
    • Configuration Identification
    • Configuration Control
    • Status Accounting and Audits
    • Baselines
    • Build Management
    • Process Management
    • Packaging Management
    • Teamwork
    • SOX Compliance
  • Intro to SCM: Detailed Description of the SCM Components
    • The following slides describe each of the SCM Components in more detail.
  • Intro to SCM: Configuration Identification
    • Configuration Identification – To be able to determine the components of the Software Product.
      • What is the Software Product? You cannot manage or control something if you don’t know what it is.
      • Configuration Identification is the process of determining the scope of the Software Product.
      • We must have a list of the components that make up the Software Product, including all user and project documentation.
      • The components within the scope are known as Configuration Items, or CIs.
  • Intro to SCM: Configuration Control
    • Configuration Control – Control changes to the Software Product.
      • SCM requires that we manage and control all changes to the Software Product so that we know exactly what changes have been applied.
      • We must ensure that no unauthorized changes are made.
      • We must ensure that every authorized change is made by following a well-defined change process.
  • Intro to SCM: Status Accounting and Audits
    • Status Accounting and Audits – Know the current state of all components in the Software Product and which are affected by what change request.
      • Status Accounting is used to track the progress of changes to the Software Product associated with a project.
      • Audits are used to ensure the integrity of the scope of the project.
  • Intro to SCM: Status Accounting and Audits (cont’d)
    • Status Accounting
      • The Status Accounting process tracks baselines, work requests, and the inventory of current CIs.
      • The purpose of Status Accounting is to provide project status throughout the development process and to maintain a living documentation of the changes in status of all CIs.
  • Intro to SCM: Status Accounting and Audits (cont’d)
    • Audits
      • SCM audits verify that the software product satisfies the baselined requirements and ensures that what is built is what is actually delivered.
      • SCM audits also ensure that traceability is maintained between all CIs and that all work requests are associated with one or more CI modifications.
      • SCM Audits are the “watchdogs” that ensure that the integrity of the project’s scope is preserved.
  • Intro to SCM: Baseline
    • Baseline – Create the ability to easily re-construct earlier versions of the Software Product.
      • A baseline is a snapshot in time of the Software Product or documentation.
      • We “take a baseline” at every point in the process that we want to be able to get back to.
      • A baseline might be as simple as taking a Harvest Snapshot or certifying a version of a product and moving it to a specified directory.
  • Intro to SCM: Build Management
    • Build Management – Ensure that the components of the Software Product were built/compiled or distributed directly from the code repository without opportunity for unauthorized changes.
      • This is the process of extracting the Software Product source from the version control tool, compiling it, and storing it in a secure location.
      • The key is to ensure that the SCM Team knows exactly where the source code came from, what is included, and can certify that it was not tampered with by unauthorized persons.
  • Intro to SCM: Process Management
    • Process Management – Ensure that the Software Product that goes into Production is the same as the Software Product that was tested.
      • Process Management is designing, establishing, and maintaining a consistent development process that meets the needs of the development team while allowing the changes to the Software Product to be controlled and tracked.
      • Process Management for an application is defined in the SCM Plan, which is developed and owned by the SCM Team.
      • Process Management is also the act of protecting the Software Product from being modified by circumventing the defined process.
  • Intro to SCM: Process Principle #1 The following four slides illustrate one of the most effective SCM process principles used in the BASA applications today. For applications that do not have a well-defined development process, implementing this principle will usually cut their defect rate significantly.
  • Intro to SCM: Process Principle #1 – The Right Way Access to modify code is only allowed in the Development State. There is no opportunity to circumvent the process downstream.
  • Intro to SCM: Process Principle #1 – The Right Way The Development Team has read-only access to the Test and subsequent environments. Once Code enters the Test State, it is not touched again by the Development Team.
  • Intro to SCM: Process Principle #1 – The Wrong Way Code moved from environment to environment without process circumvents the development process. Code should only be promoted through the Version Control Tool.
  • Intro to SCM: Process Principle #1 – The Right Way Code should only be promoted through the Version Control Tool, not from environment to environment.
  • Intro to SCM: Packaging Management
    • Packaging Management – Ensure that the Software Product is packaged/prepared for Production in a standardized and consistent manner.
      • Once the Software Product has been built, it must be packaged for delivery to the production environment.
      • Package management means having a standard and consistent process for preparing the Software Product for installation, so that installations are consistent and the chances of installation problems are reduced.
  • Intro to SCM: Teamwork
    • Teamwork – Work with each Project Team to provide the appropriate amount of SCM process for each application, balancing risk, expediency, and funding.
      • The SCM needs for a large, critical application are different from that of a small non-critical application.
      • Designing and maintaining process costs money. The goal is to use enough process to reduce the risk to an acceptable level.
        • Too much process introduces excessive costs.
        • Too little process introduces excessive risks.
  • Intro to SCM: Teamwork (cont’d)
    • Teamwork –
      • The SCM Team works with all of the other teams to determine the appropriate level of process. Again the Development Process is described in the SCM Plan.
      • Too much process strangles and slows the development process.
      • Not enough process allows recurring defects, unauthorized changes, and, in the extreme, unexplained changes to the production environment.
      • The SCM Team involve the other teams in developing the process so they understand the reason for each part of the process.
  • Intro to SCM: Teamwork (cont’d)
    • Teamwork –
      • Some keys to developing the appropriate amount of process:
        • Start out the process design with too much process. Design tight controls for every part of the development process. The idea is that it is easier to loosen up later than to tighten up.
        • Examine each part of the process to determine the benefit it brings. If you cannot qualify the benefit of a process, then you probably should not implement it.
        • Look for gaps in the defined process and close them. These gaps usually represent ways to circumvent the process.
  • Intro to SCM: SOX Compliance
    • SOX Compliance – Ensure that all changes to Software Products are conducted according to BellSouth’s SOX directives.
      • As a publicly traded corporation, BellSouth is bound by US law to comply with SOX guidelines.
      • The SCM Team participates in SOX compliance and is obligated to report any SOX violations to the SOX Auditing Team.
      • All applications must have a process for providing the appropriate SOX artifacts to substantiate our Customer’s compliance with the SOX guidelines.
  • www.scmGalaxy.com Thank You ! Author: Rajesh Kumar [email_address]