Configuration Management (managing change) - PowerPoint PPT Presentation

Loading...

PPT – Configuration Management (managing change) PowerPoint presentation | free to download - id: 4490b5-MDNkN



Loading


The Adobe Flash plugin is needed to view this content

Get the plugin now

View by Category
About This Presentation
Title:

Configuration Management (managing change)

Description:

Configuration Management (managing change) Starter Questions... Which is more important? stability progress Why is change potentially dangerous? – PowerPoint PPT presentation

Number of Views:178
Avg rating:3.0/5.0
Slides: 23
Provided by: StephenD6
Category:

less

Write a Comment
User Comments (0)
Transcript and Presenter's Notes

Title: Configuration Management (managing change)


1
Configuration Management(managing change)
2
Starter Questions...
  • Which is more important?
  • stability
  • progress
  • Why is change potentially dangerous?
  • What causes configuration problems?
  • multiple developers
  • multiple releases
  • components used in multiple products
  • changing requirements
  • etc...

3
Change is inevitable.
AND
Change creates confusion.
BUT,
Confusion is NOT inevitable.
4
Outline for Tonight
  • "Baselines"
  • CM Repository and Config Tools
  • CM Plan

Much of this SCM presentation is based on Chapter
27 of Pressman's Software Engineering A
Practitioners Approach 6th Edition
5
Goals of CM
5 of 22
  • Identify Change
  • Control Change
  • Stability vs Progress
  • Ensure Change is Properly Implemented
  • Report Changes to people who Need to Know

6
What Changes?
  • Software Code
  • source code
  • object code
  • Data
  • Documents
  • SRS
  • designs
  • project schedules
  • test plans, test results

7
Key Concept "Baseline"
  • "A specification or product that has been
    formally reviewed and agreed upon, that
    there-after serves as the basis for further
    development, and that can be changed only through
    formal change control procedures."
  • IEEE Std 729
  • Standard Glossary of Software Engineering
    Terminology

8
Baseline Use
8 of 22
  • Establishment of a baseline is a milestone.
  • Before that milestone, change can be made
    informally.
  • Once reviewed and accepted, the product becomes
    an established baseline. Everyone proceeds using
    that version, which is located in a central
    database.
  • Therefore, further change requires formal review,
    notifications, etc.

9
Baseline - Standard Change Process
9 of 22
  • Change Request is made (see next slide)
  • Request is Approved or Denied
  • "Check Out" the item(s)
  • Make Changes
  • Testing or Reviews
  • formal review of design changes,
  • regression testing of modules, etc
  • Review the Change Order
  • Notify all Dependencies
  • when baseline change will occur
  • what changes were made to baseline
  • "Check In" the new baseline

10
Template for Baseline Change Requests
10 of 22
  • Name, Date, yadda yadda
  • Type of change
  • Goal of making the change
  • Priority / Urgency
  • Detailed description of the changes
  • Expected Effects
  • Timetable for making changes, testing, release,
  • Estimated Costs

11
http//satc.gsfc.nasa.gov/GuideBooks/Image4.jpg
12
Version Numbering
12 of 22
  • Item After Modify Build 1 Build 2 Release
    1
  • Test Plan 0.0.0 (original version)
  • 0.0.1 --gt 0.1.0
  • 0.1.1 --gt 0.2.0 --gt 1.0.0
  • Module 1 0.0.0 --gt 0.1.0 --gt 0.2.0 --gt
    1.0.0
  • Module 2 0.0.0
  • ...
  • 0.0.8 --gt 0.1.0
  • 0.1.1 --gt 0.2.0
  • 0.2.1
  • 0.2.2 --gt 1.0.0

13
Question...
  • How do we keep track of all these versions,
    dependencies among components, approval records,
    etc. etc. etc.?
  • Use Good CM Tools
  • Have a Sound CM Procedure

14
CM Repository - Common Jargon
14 of 22
  • CM Objects
  • CM probably organized as object-oriented database
  • Basic Objects
  • Aggregate Objects
  • Configuration Item
  • standard term for entities in the CMR

15
CM Tools - Necessary Features
15 of 22
  • Versioning
  • Dependency Tracking!!!
  • Audit Trails!!!
  • Reporting of Changes
  • Supports the Change Rules
  • Requirements Tracing
  • Repository arranged as "basic objects" and
    "aggregate objects"
  • Supports both Linear evolution and Trees

16
CM Tools
16 of 22
  • Commercial SCM Tools
  • Google " 'Software Configuration Management' "
  • 2009 959K hits
  • 2012 "About 1,250,000 results"
  • Simple example
  • Linux tool RCS or CVS
  • next slide

17
17 of 22
  • Get a copy of the module tc
  • cvs checkout tc
  • Get a copy of the module tc as it looked one day
    ago
  • cvs checkout -D yesterday tc
  • If you had to create a patch to the 1.2 version
    of the product, even though the 2.0 version is
    already under development, you might do
  • cvs rtag -b -r FCS1_2 FCS1_2_Patch
    product_module
  • cvs checkout -r FCS1_2_Patch
    product_module
  • cd product_module
  • hack away
  • cvs commit
  • Other very handy commands
  • annotate - for each line, print the version that
    created it
  • diff - differences in versions, LOTS of
    options
  • history - version dates, etc.
  • log - who last edited each line
  • release - stop editing, but don't save changes

18
Parts of a CM Plan
18 of 22
  • Process Elements
  • collection of procedures that define
    approach to change management
  • Component Elements
  • set of tools and file management system that
    enable access to and management of items
  • Construction Elements
  • tools that automate the construction of
    software, test suites, etc.
  • Human Elements

19
IEEE / ANSI 828
19 of 22
  • Standard for Software Configuration Management
    Plans
  • 1. Introduction
  • a) purpose
  • b) scope
  • c) definitions and acronyms
  • d) references
  • 2. Management
  • a) organization
  • b) SCM responsibilities
  • c) interface control
  • d) SCMP implementation
  • e) policies, directives, procedures (naming
    conventions, version designations, problem report
    process)
  • 3. SCM Activities
  • a) configuration identification
  • b) configuration control (change history, review
    authority, read/write control, member
    identification)
  • c) configuration status accounting (status of
    change requests, status of approved changes, )
  • d) audits and reviews
  • 4. Tools, Techniques, and Methodologies

20
IEEE 1042
20 of 22
  • Guide to Software Configuration Management
  • Defines terms such as baseline and version
  • Discusses configuration management as a
    management discipline and its role in the
    engineering process
  • Includes checklists of issues for sections of the
    SCMP (IEEE Std 828)
  • Includes four complete examples of SCMPs

21
CM Audits
21 of 22
  • of unapproved changes
  • of Change Orders completed on schedule
  • of affected Configuration Items that were not
    checked
  • of properly documented Configuration Items
  • number of CM Process Failures

22
Summary
  • Change is inevitable.
  • Baselines are milestones of a configuration item.
  • Use a tool or set of tools to control change
  • access control
  • version tracking
  • etc
  • Adopt a Change Management Plan
About PowerShow.com