Rational Software Corp.

TOC PREV NEXT INDEX



Preface

This book provides an overview of the basic team development concepts in Rational Rose, and shows how to set up and use Rational Rose in a team environment.


Audience

This manual is intended for:

This manual assumes you are familiar with a high-level language and the life-cycle of a software development project.


Using this Guide

This guide provides an overview of the basic team development concepts in Rational Rose, as well as how to set up and use Rational Rose in a team environment.

The information in this book spans other product lines, including software from other vendors. Its primary goal is to help you develop and tailor your own guidlines.

While this book provides explanations of some features, you will need to rely on additional product libraries for information. For example, you may need to refer to the ClearCase documentation to configure ClearCase for your environment.

In addition to this guide, refer to the Rational web site (www.rational.com) for white papers, technical notes, and articles relating to team development.


Other Resources


What to Read Next

All users of Rational Rose should familiarize themselves with how models are stored and how Rational Rose interacts with source control systems. See Managing/Administering a Model and Source Control Fundamentals for details on these areas.

Developers should also read Working with a Version Control System. Project leads and architects will want to review the material in Developing a Model Architecture.

Development environment infrastructure is discussed in Working with a Version Control System. That section should be read by source control administrators and anyone involved with preparing builds. As well, specific details regarding the creation of a build process and automating builds, as well as how to perform model integration, is covered in Establishing a Model Architecture and Process for Team Development.


Limitations of this Document

One of the primary goals of Rational Rose is to fit into your existing development and build processes. While this document tries to be thorough, you will encounter team development issues which are not covered here. As a general guideline, you should approach these situations with the same mindset you would have for `more typical' C++, C, and Java development. In most cases, you can apply the same, or slightly modified practices to achieve your goals.


Contacting Rational Technical Publications

To send feedback about documentation for Rational products, please send e-mail to techpubs@rational.com.


Contacting Rational Technical Support

If you have questions about installing, using, or maintaining this product, contact Rational Technical Support.

Your Location

Telephone

Fax

E-mail

North America
(800) 433-5444
(toll free)
(408) 863-4000
Cupertino, CA

(781) 676-2460
Lexington, MA

support@rational.com
Europe, Middle East, Africa
+31 (0) 20-4546-200
Netherlands

+31 (0) 20-4546-202
Netherlands

support@europe.rational.com
Asia Pacific
+61-2-9419-0111
Australia

+61-2-9419-0123
Australia

support@apac.rational.com

Note: When you contact Rational Technical Support, please be prepared to supply the following information:


Rational Software Corporation  http://www.rational.com
support@rational.com
techpubs@rational.com
Copyright © 1993-2001, Rational Software Corporation. All rights reserved.
TOC PREV NEXT INDEX