configuration management

Configuration Management

Presentation to CMMI DEV V1.2 Intermediate Class

Israel Jan.2007 Kobi Vider - Picker

Agenda

• Class Assignment Objectives • Organization Mission • Organization Structure – High Level • Organization Structure – Technical • Multi Product Environment • Configuration Management In The Product Development Life Cycle • High Level Process Description • Interpretation Issues • Key Activities • Difficulties Encountered And Plans For Implementation • CMMI DVE V1.2 CM Coverage • References

Class Assignment Objectives

• Exercise: Describe implementation aspects of a Process Area • Purpose: Provide a demonstration of your understanding of model

and PA concept implementation and your presentation skills. • Duration: 10 minute • Scenario: organization that is in the process of implementing

CMMI-compliant processes that satisfy the PA you have been assigned, prepare a presentation that describes how the PA-related practices are being implemented across your projects’ or organization’s processes. – BRIEF overview of organization structure – Interpretation issues encountered and how addressed – Key activities that were necessary to implement the CMMI-compliant

processes in your organization – Difficulties encountered and plans for completing the implementation

Organization Mission

• Focus on three highlights:

– Advanced printing Technology

– Advanced Publishing and Archiving Technology

– Advanced Imaging Systems

• worldwide group of ~300 product development people

• Working on systems and not just software

Organization Structure

Vice President

Operation Support Account Mange. R&D

Project Officer QA& QC

Program 1 Program 3 Program 2

Program management

Product B1 Core Team

Product B2 - Core Team

Joint Project with R&D Core Team

Product A - Core Team

New Generation Core Team

Project Officer

Organization Structure - Technical

R&D

Software

System Architect

Development Teams

Engineering

Optic Mechanics Laser

Electronics Materials

Design

System Industry

Validation

Subsystem System

Multi Product Environment

Needs

Features

Product X

System A System B System C

Needs

Features

Product Y

Phase 0 Phases 3 – 4

Phases 5 – 6 Phase 7

Gate 0

Gate 2

Gate 6 Gate 7

Phases 1 – 2

Gate 4 Gate 8

Life-Cycle

Management

Pre

-Pla

nin

g

Phase 0

• Analyze and refine

a specific, scope,

functional impact,

Phases 1 – 2

• Define the whole

product offering and

its business case

unambiguously

• Develop an

integrated, cross-

functional plan that

can deliver it

• Validate technology

feasibility and

robustness

Phases 3 – 4

• Develop the

whole product

and it’s

supporting

processes

Phases 5 – 6

• Verify that the

whole product and

its supporting

functional

processes are

forceful before

launch

Phase 7

• Deliver the

product to

customers in a

controlled manner

and prepare for

and be able to

manufacture,

Life-Cycle

Management

• Ensure a long

run for the

product and

provide feedback

into the product

family planning

process

Pre-Phase 0

• Develop market-

based portfolios

(including , product

platform plans, and

links to technology

management)

Purpose of Each Phase

Configuration Management in the Product Development life Cycle

First Baseline CR Process New Baseline

Milestone Baseline

• A reviewed and approved release of artifacts that constitutes an agreed basis for further evolution or development and that can be changed only through a formal procedure, such as change management and configuration control.

By tracing features to needs and requirements to features, we can better

set priorities and verify that we don’t develop unnecessary requirements and

don’t omit important ones

High Level Process Description

12

Motivation

• Improve: – Quality

– Time to market

– Reduce Costs (development & testing)

• By: – Enhance control on product versions development

– Adaptation to development and testing processes

– Enhanced integration between development groups

13

Highlights

• Task oriented management

• Additional product oriented layer – Isolate development and product/testing env.

– Controlled & stable build environment

– Defined permission/restriction policy

– Defined responsibilities

• Build server

• Product/version creation

• Development cycle workflow

14

Current development cycle Design Dev

PDR Ready CDR Ready Int + Programer

Package 1 preliminary designPDR IntegrationUnittest

Package 2 preliminary designPDR detailed design Unittest




Integration Test

CDR

CDR

CDR

CDR

Implementation

Implementation

Implementation

Implementation

detailed design

detailed design

Implementation

Integration

detailed design CDR

detailed design

EP

Release

AlphaTest

Beta Test

Sys Alfa Test

Configuration Management Process Flow

Change Request Flow

Interpretation issues

• How to define multidiscipline baseline

• Configuration items definition in system environment

• How to Track change requests cross different products on the same configuration item

Key activities • Identify needs and goals

• Obtain senior management commitments

• Specify scope for pilot

– Project

– Product / product family

• Select and prepare improvement team

• Understand the current implemented processes And Practices.

• Identify processes and practices improvement opportunities (and strengths) in the organization unit.

• Evaluate degree of satisfaction of CMMI process area goals

• Develop the implementation plan and set success criteria

• Execute the improvement plan, monitor it and refine as needed

Difficulties encountered and plans for implementation

• How to define multidiscipline baseline

• Configuration items definition in system environment

• Cross product change control of same configuration item

CMMI DVE V1.2 CM Coverage

CMMI DEV. V1.2 Organization Process

SG 1 Establish Baselines - Baselines of identified work products are established

Gate 2 checklist and configuration plan with first base line

SP 1.1 Identify Configuration Items - Identify the configuration items, components, and related work products that will be placed under configuration management

Gate 2 checklist and configuration plan with first base line captured in the CCDB (as described in slide 15)

SP 1.2 Establish a Configuration Management System - Establish and maintain a configuration management and change management system for controlling work products

Using the tools with process description document, templates and guidelines as described in slide 15

SP 1.3 Create or Release Baselines - Create or release baselines for internal use and for delivery to the customer




SG 2 Track and Control Changes - Changes to the work products under configuration management are tracked and controlled


SP 2.1 Track Change Requests - Track change requests for the configuration items


SP 2.2 Control Configuration Items - Control changes to the configuration items

Using the tools with access rights and process description document, templates and guidelines as described in slide 16



SG 3 Establish Integrity - Integrity of baselines is established and maintained

SP 3.1 Establish Configuration Management Records - Establish and maintain records describing configuration items

As the result of the tools reports

SP 3.2 Perform Configuration Audits - Perform configuration audits to maintain integrity of the configuration baselines

Using the tools with flows, checklists, templates and guidelines as described in slide 15

CMMI DVE V1.2 CM Coverage CMMI DEV. V1.2 Organization Process

GP 2.1 Establish an Organizational Policy Policy document that describe the business motivation and expected results

GP 2.2 Plan the Process process description document, templates and guidelines

GP 2.3 Provide Resources Tools, checklists, templates, funding and Subject Matter Experts

GP 2.4 Assign Responsibility With established and maintained communication and focal point contacts

GP 2.5 Train People User guides, guidelines, formal training and orientation training

GP 2.6 Manage Configurations Relevant documents are managed in the CC tool (Clear Case) such as process flow and configuration plan

GP 2.7 Identify and Involve Relevant Stakeholders With established and maintained communication and roles and responsibilities matrix

GP 2.8 Monitor and Control the Process Through core team and Change Control Board meetings

GP 2.9 Objectively Evaluate Adherence Through Quality Engineer external audits, work products review and observations

GP 2.10 Review Status with Higher Level Management Through core team meetings, status meetings and gate review

GP 3.1 Establish a Defined Process One process description for all products and projects in the division

GP 3.2 Collect Improvement Information Through Quality Engineer monthly reviews and meetings



GP 4.1 Establish Quantitative Objectives for the Process

We have defined targets with tight relationship to our business objective, currently we are in the process of implemntation our measurements and targets as defined in our plan

GP 4.2 Stabilize Subprocess Performance We have selected critical subprocess for this, currently we are in the process of training for it

GP 5.1 Ensure Continuous Process Improvement

Not in phase

GP 5.2 Correct Root Causes of Problems Not in phase

References • Software Configuration Management Strategies and IBM® Rational® ClearCase® Second Edition A Practical

Introduction – By David E. Bellagio, Tom J. Milligan

– Publisher: Addison Wesley Professional

– ISBN: 0-321-20019-5

• Software Configuration Management – by Jessica Keyes

– Auerbach Publications

– ISBN:0849319765

• Designing a Change and Configuration Management Infrastructure - Delivery Guide – Microsoft press

• Software Configuration Management Patterns: Effective Teamwork, Practical Integration – By Stephen P. Berczuk, Brad Appleton

– Publisher : Addison Wesley Pub

– ISBN : 0-201-74117-2

• MILITARY HANDBOOK - Configuration Management Guidance – MIL-HDBK-61

• MILITARY STANDARD- Configuration Management – MIL-STD-793

• IEEE Std 828-1990 standard for software configuration management plans

• IEEE Std 828-1998 Standard For Software Configuration Management Plans

• Configuration Management Principles and Practice – By Anne Mette Jonassen Hass

– Publisher : Addison Wesley Pub

– ISBN : 0-321-11766-2 Pages : 432

Thank You

Questions?

Backup slides

For more detailed insight in to the process

28

Task oriented management

• Clear Activities name conventions – MS project task (feature) = CC activity – Bug ID = CC activity – Examples:

• Improve_Paper_ disposal_ sequence_integration • Insert_right_click_diag • Problem_in_Plate_Grounding_in_Cassette

– Activities grouping (Basket orientation)– TBD – Baseline viewing upon activities – Promotion/Delivery upon activities state

29

Enhanced model basic diagram

D

E

V

S

T

R

E

M

D

E

V

S

T

R

E

M

DC ver X.XX

Coding

Stream

Unitest

DC ver X.XX

Integration

Stream

Product X

3.75.xx

Product Layer Development Layer

30

Enhanced model ClearCase view

31

Build server

• Controlled environment

• Scheduled compilations on Coding and Integration

• Compilation SW products managed in ClearCase

• Build results notification – by e-mail to specific e-mail

list

• Manual build option

32

“CC-CD” = ClearCase CD

– Target Baseline – code & SW products

– Install Shield – automatic “CC_CD” creation

– Notification of “new CD” to QA list

– Device version installation from “CC_CD”.

33

Developer Environment

– Development Stream for each developer

– Activity oriented = development effort

– Activity name = task name from WP

– Local compilation

– Local debugging on machine

– Re-base and merge in Dev Stream

– Activity Delivery to Coding Integration Stream

– Verify successful build in Coding Stream

34

Coding environment

– Scheduled build – Scheduled as listed

– Build Notification - Distribution to list

– Delivery Package Notification - Distribution to list

– Base line if new deliveries – Distribution to list

– Check-In build results – compilation products – Distribution to list

– Create “version image = “CC_CD” - Distribution to list

– New “CC_CD” Notification – Distribution to list

– Install shield from “CC_CD” – Distribution to list

– Delivery Package status management – Distribution to list

– Promote Tested Delivery Package to Integration Stream

35

Integration environment

– Scheduled build – every night * (weekly) – Build Notification - management list (PM,QA,TL) – Delivery Package Notification - management list – Base line if new deliveries – TL *(weekly) – Check-In build results – compilation products – TL – Create “version image = “CC_CD” - TL – New “CC_CD” Notification – management list – Install shield from “CC_CD” – for integration&Alpha tests – Delivery Package status management – QA&TL

36

Cross project deliveries

• Promote/Deliver delivery pack between different projects Coding streams !

• Notification Upstream (to higher version of the DC)

• The target project is the delivery initiator

37

Cross project deliveries

D

E

V

S

T

R

E

M

D

E

V

S

T

R

E

M

ver X.XX

Coding

Stream

Unitest

ver X.XX

Integratio

n

Stream

Product

A

D

E

V

S

T

R

E

M

D

E

V

S

T

R

E

M

ver X.XY

Coding

Stream

Unitest

ver X.XY

Integratio

n

Stream

Product

Aa

configuration management

Documents