 |
 |
 |
 |
Contents
Preface
- Audience
- Using this Guide
- Other Resources
- What to Read Next
- Limitations of this Document
- Contacting Rational Technical Publications
- Contacting Rational Technical Support
Understanding Team Development
- Contents
- Planning for Team Development
- Developing a Strategy
- How Rational Rose Supports Team Development
Establishing a Model Architecture and Process for Team Development
- Model Architecture and Process
- Establishing Roles and Responsibilities
- Model Architect
- Model Manager
- Modeler/Developer
- Model Integrator
- Source Control Administrators
- Configuration Managers
- Developing a Model Architecture
- Understanding Subsystems
- One Model Versus Multiple Models
- Mapping the Architecture to Subsystems
- Checking Package Dependencies for Completeness
- Checking if a Subsystem is Self-Contained
- Defining Subsystem Interfaces
- Configuring Subsystem Components
- Providing Support for Unit Testing
- Using Property Sets for Build Settings
- Creating Processors and Component Instances
- Preparing and Releasing Subsystems
- Splitting a Model into Subsystem Models
- Splitting a Model Under Version Control
- Managing/Administering a Model
- Configuring Compatible Workspaces
- Configuring a Version Control System and Repository
- Partitioning the Model into Controlled Units
- Save Model to Local Work Area
- Adding the Model to Version Control
- Defining Developer Work Areas
- Creating Labels and Lineups
- Manipulating the Version Control Repository
- Developing/Implementing a Model
- Setting up Version Control
- Setting up Developer Work Areas
- Getting a Specific Lineup of a Model
- Opening a Model Under Version Control
- Working under Version Control
- Comparing and Merging Model Elements
- Promoting Changes for Integration
- Integrating Changes
- Automating Model Validation
Best Practices
- Contents
- Goals of Team Development
- Sharing Within a Team Environment
- Protecting Configuration Items From Unintentional Changes
- Overwriting a Modification
- Adding Dependency Issues
- Managing Relationships Between Configuration Items
- Managing and Delivering Configuration Items
- Improving Efficiency in Team Development
- Model Architect Role
- Recommendations
- Source Control Fundamentals
- Preempting Conflicts
- Managing Dependencies
- Labeling
- When Merging is Necessary
- Advanced Concepts and Heuristics
- Moving Controlled Units
- Parallel Development
- Model Integrator
- Using Rational ClearCase Multi-Site
- Additional Heuristics for Team Development
Dividing a Model into Controlled Units
- What is a Controlled Unit?
- What Can be a Controlled Unit
- How Controlled Units are Related and What They Contain
- Working with Controlled Units
- Creating Controlled Units
- Loading, Reloading, and Unloading Controlled Units
- Creating and Using Model Workspaces
- Protecting Controlled Units
- Splitting a Controlled Unit
- Merging Controlled Units
- Adding Controlled Units to a Model (Importing/Loading)
- Uncontrolling Controlled Units
- Creating Virtual Paths to Controlled Units
- Understanding Virtual Path Maps
- How Virtual Paths Work
- Creating Virtual Path Maps
- Defining a Path Map Relative to the Location of the Model File
- Defining a New Path Map Using Another Path Map Symbol
- Defining a Path Map with Wildcards
- Using Virtual Paths for the Value of a Model Property
- Using Path Maps for Other Artifacts
- Where Virtual Path Maps are Stored
- Checking References and Access Violations
- Check Model
- Show Access Violations
- Organizing Controlled Units for Teams
- Suggested Strategies
Comparing and Merging Models
- Contents
- About the Model Integrator
- Model Integrator Interface
- Contributors
- Base Model
- Comparing Models
- Merging Models
- Differences and Conflicts
- Model Files and Model Integrator
- Understanding Semantic Checking
- Memory Requirements and Performance
- Model Integrator and ClearCase
- Merging Whole Models with Controlled Subunits
- Starting Model Integrator in a ClearCase Integration
- Comparing and Merging Models
- Starting Model Integrator
- Preparing Models for Merging
- Selecting the Contributors
- Loading or Unloading Controlled Units
- Using Compare Mode
- Using Merge Mode
- Interpreting Compare and Merge Results
- Navigating Through a Model
- Accepting Changes from Contributors
- Changing Nodes with Differences
- Reversing Changes to Nodes
- Using Subtree Mode
- Using Semantic Checking
- Checking Merged Model for Consistency
- Correcting Merge Errors
- Saving Results
- Performing a Partial Merge
- Merging Models Without a Base Model
- Viewing a Single Model File
- Using Model Integrator from the Command Line
Working with a Version Control System
- Understanding Version Control
- Types of Version Control Systems
- Version Control Development Concepts
- Versioning Strategies
- Rational Rose Integration with Version Control Systems
- Version Control Add-In
- ClearCase Add-In
- Choosing and Activating a Version Control Add-In
- Using Rational ClearCase
- About ClearCase
- Versioned Object Bases (VOBs)
- ClearCase Views
- Configuring ClearCase for Rational Rose
- Using Microsoft Visual SourceSafe
- Configuring Microsoft Visual SourceSafe for Rational Rose
- Using Version Control Features From Rational Rose
- Using the Version Control Add-In on a Previously Controlled Model
- Adding Controlled Units to Version Control
- Checking in Controlled Units
- Checking Out Controlled Units
- Undoing the Check-Out of Controlled Units
- Getting the Latest Version of Controlled Units
- Removing Controlled Units from Version Control
Index
| Rational Software Corporation
http://www.rational.com support@rational.com techpubs@rational.com Copyright © 1993-2001, Rational Software Corporation. All rights reserved. |
| |
|
|
|