Rational's generic Unified Change Management (UCM) process
supports best practices for change management as described in the
Rational Unified Process. Project managers can configure UCM policies to meet most project needs.
share name for storage.
A Software Configuration Item (SCI) is information that is created as part of the software engineering process, such as Requirements Specifications and User Manuals. NOT considered a potential SCI is a Project Proposal.
Directories and Files are elements stored in
VOBs (Versioned Object Bases)
To make a VOB (pronounced as a one-syllable word), invoke the Create VOB wizard or:
cleartool mkvob
Note: Examples of commands here use the forward slashes (/) so that
they can be used in both Windows and UNIX environments.
Internal control information about VOBs are stored in a
physical storage directory/folder.
within each VOB, ClearCase automatically creates for itself a lost+found special directory.
Profiles
To mount a VOB, invoke from Start ClearCase Administration > Mount VOB or
cleartool mount
The element keyword precede version selection rules which selects a version of an element.
All elements are stored with a version history and other information.
Each specific version of elements are accessed by a View.
A view is a filter that allows work on only one version in a VOB.
It is best practice to create each version with a comment.
Each view shows a directory tree of elements.
There are two types of views:
- Snapshot views
- Dynamic views use the ClearCase Multiversion File System
The elements in each view is defined by a Config spec (Configuration Specification).
The default config spec has the following rules:
element * CHECKEDOUT
element * /main/LATEST
To find elements created between Jan. 1st and Jan 7th:
A view also establishes a private work area and
creates a layer of view-private files on top of the public VOB elements
available to everyone who uses the VOB.
It then makes the two sets of files appear as if they are part
of the same directory structure.
By default, work on elements begin from the
/main line of development with an empty Version 0 file.
Each checkin increments the version number.
A specific version may be labeled as a particular release
such as “REL1.0”
To make a new release ...
Which one of the following statements describes the difference between items that are both baselined and configuration controlled versus items that are NOT baselined, but configuration controlled?
Choice 1
Items that are not baselined require only CCB approval for a change. Items that are baselined require both technical team approval and CCB approval.
Choice 2 >>>
Items that are not baselined require only CM Manager approval for a change. Items that are baselined require CCB approval.
Choice 3
Items that are not baselined require only technical team approval for a change. Items that are baselined require CM Manager approval.
Choice 4
Items that are not baselined require only program management approval for a change. Items that are baselined require CCB approval.
Choice 5
Items that are not baselined require the technical team approval and the program management approval. Likewise, items that are baselined require the same review and approval level.
To build an application, use a variant of the UNIX makefile utility:
cleartool app1
Build with OMAKE (windows)
To facilitate parallel development on the same piece of code,
a new branch is created.
ClearCase prevents you from saving a changed file unless you check it out.
as long as you are not changing a VOB element, you can treat a VOB element as if it were a normal file or directory. You can read it, print it, compile it, and run it without invoking special ClearCase commands.
You can perform regular non-destructive file operations on VOB elements
without first interacting with ClearCase.
For example, you can use MS-DOS commands or
an application installed on your computer to browse through or open VOB files.
Invoke the ClearCase Explorer GUI.
Load rule
Deltas
CM software often provides some form of delta versioning to store multiple versions of a software item.
Referring to the statement above, what is the correct definition for forward delta-based versioning?
Choice 1
Deltas are kept for all versions of the file except for the latest version and other frequently used versions.
Choice 2
Deltas for each version are stored in the original file with special notations to mark and identify the configuration of each version.
Choice 3
The first version of a file is stored in its entirety. Incremental deltas are kept for all subsequent versions including the latest version.
Choice 4
Delta annotations are stored separately from the file. Versions are built by reading the delta annotations and applying the changes to the file.
Choice 5
The latest version of the file is stored in its entirety. Deltas are kept for all previous versions.
Triggers
Triggers (.tgr files) define what ClearCase watches
ClearTrigger triggers at the enterprise level.
Even a locked VOB can have a lshistory performed on it by anyone, even those not in the VOB's group list. The checkin/out comments used to track changes are visible to anyone.
Pre-operation triggers
Post-operation triggers
Source Control HOWTO by Eric Sink
Version/Change and Configuration Management
Take the Brainbench certification test
Brad Appleton's Software Configuration Management Links
The comp.software.config-mgmt newsgroup on cm tools