®

IBM Software Group

Essentials of Rational ClearCase

Module 1: Getting Started

1
Objectives
Upon completing this module, you should be able to:
 Define software configuration management (SCM)
 Explain how ClearCase implements SCM
 Explain ClearCase roles
 Define basic ClearCase terminology and concepts
 Explain the typical developer workflow in ClearCase
 Set up your ClearCase workspace
 Access ClearCase Help

2
Software Development and Change
 Software development involves change
 A defect to be fixed
 An existing function to be enhanced
 A new feature to be added
 A new platform to support
 A customer-driven special project
 Internationalization

3
Change Causes Developers Pain
 Working in isolation, you can’t “see” code changes made
by team members
 You can’t work in parallel on files that a co-worker is
modifying
 You frequently lose time and have to redo work because of
lost defects or overwritten code
 You have trouble determining which versions of the code
you should be working on
 You have difficulty answering your manager’s questions
about project status
 You don’t know who on the team is working on what
 You have no idea which versions of files went into a build
4
Software Configuration Management
(SCM)

“SCM is about
managing change
to software.”

Brian White, Software

Configuration
Management Strategies and
Rational ClearCase (2000)

5
Software Configuration Management
(cont.)
 A successful SCM effort ensures:
 Safety
 Stability
 Control
 Auditability
 Reproducibility
 Traceability
 Scalability

6
ClearCase Implements SCM
 Version control  Workspace management
 Version all types of  Work in parallel with
files and directories other developers

 Build management  Process control

 Ensure the integrity of  Record and report
all software elements actions, history, and
 Accurately reproduce milestones
every release  Customize process
 Trace and reproduce
builds

7
ClearCase Roles
 ClearCase developer  ClearCase integrator
 Set up workspace  Create integration
 Make changes workspace
 Integrate changes  Create baselines
 Update workspace
 Build components
 ClearCase configuration  ClearCase administrator
manager
 Set up hardware
 Write CM plan
environment
 Design development
environment  Implement development
 Establish CM Policies environment
 Assign and schedule work  Maintain hardware and
 Monitor project status development
environments
8
Typical Developer ClearCase
Workflow

9
Typical Workflow: Setting Up Your
Workspace

10
What Is a Versioned Object Base
(VOB)?
 A permanent, read-only data repository that:
 Stores files, directories, and
metadata
 Stores version-controlled data
 Displays its contents as files
in a file system
 Stores anything that can be
represented as a file or directory
 Can be replicated in two or more sites

11
Projects and VOBs
 A project can span more than one VOB
 Multiple projects can share common VOBs

12
What Is an Element?
 A file or a directory, under source control,
stored in a ClearCase VOB
 Can be any object that can be stored in a native
file system, including:
 Source files
 Directories
 Binary files
 Object libraries
 Documents
13
What Is a Version?
 An element consists of a set of versions, organized
into a version tree
 Each version represents
one revision of a file
under source control
 Versions are displayed
in a workspace or view

14
What Is a View?
 A ClearCase mechanism that allows users access
to versions of elements in VOBs
 An isolated workspace for a user or a group
 Enables users to work in parallel

15
What Is a Configuration Specification?
 For each view, a set of ordered rules used to
select at most one version of each element
 Determine which versions of an element are
visible in the view

16
Types of Views

17
Which Type of View Should I Use?

Dynamic Snapshot
• You want to access • You are using Win 9X,
elements in repositories Win ME, or ClearCase
without copying them to LT, which do not
your computer support dynamic views
• You want the view to • You want to work
reflect changes made by disconnected from the
other team members at network
all times
• You do not need build
• Your project uses build avoidance
auditing

18
Structure of a Dynamic View

19
Structure of a Snapshot View

20
Intro to ClearCase Explorer

Folder Pane Details Pane

Shortcut
Pane

Information
Pane

21
Creating a Dynamic View
Base ClearCase

1
Launch the View
Creation Wizard.

2
Select Dynamic View.

Toolbox tab

22
Creating a Dynamic View (cont.)
3
Choose a view name (or view-tag).

4
Select a drive letter to which you want to
connect the new view, or you can select
{none} and work directly on the MVFS
(M:) drive.
5
Click Advanced Options.

6
Accept the default or
specify the location of
the view storage
directory.

23
Starting a View
 Each view has a unique tag name
 When you create a dynamic view, it starts automatically,
or you can start a different dynamic view
2
Select the view you
want to start, and then
click OK.
1
Click
Start View.

24
Dynamic Views Drive

When started, the

dynamic view always
appears under the
MVFS drive.

When you start a

view, it can also be
mapped to a logical
drive.

25
Mounting a VOB for Dynamic Views
 The mount command activates a VOB for use on
the local workstation
 You access a VOB through its unique tag name

26
ClearCase Online Manuals
 Select Help
> Help
Topics to
access the
ClearCase
online
manuals
 Manuals
are in .pdf
format

Online Manuals

27
Help Topics

Search the index

Search by keyword

28
Module Review
 What is SCM?
 How does ClearCase help you manage change to
software?
 What tasks are involved in setting up your
workspace?
 What is a VOB? Element? Version? View?
 How do you access particular versions of elements
in a ClearCase VOB?
 What is the difference between a snapshot view and
a dynamic view?
 How do you access online Help in ClearCase?

29
Module Lab
 In this lab, you will:
 Launch ClearCase GUI
 Create a dynamic view
 Mount a VOB

30