Designing a Component-Based Common SCM System

7/31/98


Click here to start


Table of Contents

Designing a Component-Based Common SCM System

Overview

The Passport Team - A Great Group Of People

Business Motivators

Technology Adoption Life-Cycle (Geoffrey A. Moore - Crossing the Chasm)

Merger And Acquisition History

Worldwide Product And Service Operations

Also Acquired Many CM Systems And Processes

Combine Core Competencies Into New Products

The Dependency Management Problem

Attempted Solutions And Results

The Component Solution

Introducing Passport

Passport SCM Architecture

Architectural Building Blocks

Streams - A Gathering Place For Components

Components - The Center of the Passport Universe

Component Internals

Private and Public VOBs

Private And Public VOBs (continued)

Dependencies - Connects Customers and Suppliers

How Do You Track Dependencies?

Resolving Dependencies Between Components

Dependency Graphs Over Time

Workspaces

Processes

Development Methodology

Build Methodology (typically performed by CM)

PV Methodology (typically performed by PV)

Release Methodology (typically performed by CM)

Change Sets - The Heart of Source Management

Change Set Management - Overall Flow

Change Set Management - Trivial Merge

Change Set Management - Non-Trivial Merge

Deploying Passport SCM - The Challenge

The 8-Step Deployment Process

A Real World Example: Project Team Alpha

ALPHA Component Architecture

Conclusions

Author: Dan O'Neill