Here are my notes on using Version/Change and Configuration Management software to manage digital assets.
Maintain an auditable and repeatable history of your organization's source files and software builds.
According to the SEI CMM Software Configuration Management Key Process Area (KPA), the goal of Software Configuration Management:
The Change Control Board (CCB) determines what changes will be approved and implemented during the Code Implementation, System Test, Post-Release phases. (Not during Requirements or Design phases).
In SCM, one deals with the problem of several people developing, building, shipping, and maintaining several copies of software products, each with an individual set of changes applied to make it fit into a particular environment.
SCM engineers identify and control these changes so that resulting work products are well-identified and well-defined.
Software Configuration Management consists of four basic processes:
The normal hierarchical structure of CSCI components, from highest to lowest:
Responsibilities of the CMO (Configuration Management Officer) include:
The key success factors for implementing a change management process include:
A waiver is designated as major if the configuration documentation defining the requirements for the item classifies defects in requirements and the waivers consist of a departure from a requirement classified as major.
According to MIL-STD-498 and IEEE standard Std 610.12-1990, Allocated Configuration Identification is the approved allocated baseline plus approved changes.
The current approved or conditionally approved technical documentation defines the configuration of a CI during the production, operation, maintenance, and logistic support phases of its life-cycle.
A Functional Configuration Identification (Functional Configuration Item) is approved functional baseline plus approved changes to functional characteristics, design constraints, and lower level CIs.
Source Control HOWTO by Eric Sink
Packages such as Moonlight collect and store configuration settings in a specialized repository SQL database system.
HP's LGPL SmartFrog (Framework for Object Groups) has runtime daemons (written in Java) to implement PKI-secured requests written in its generic configuration description XML language and stored in Java data structures. It was originally designed as a framework for building and managing large monitoring systems where flexible configurations are essential. Its components include sequencing, distributed workflows, failure detection, script execution, installation of software, ignition, dynamic discovery and naming.
Among the 618 Sourceforge.net projects under System > Install/Setup projects, System Installation Suite, which includes SystemImager, to make the installation of Linux to masses of similar machines relatively easy by taking images containing unconfigured OS plus apps from a "golden" base. Images are stored in an image server. This makes software distribution, configuration, and operating system updates easy, and can also be used for content distribution.
Modeling your applications for understandability and consistency
Automatic UNIX Documentation with unixdoc by Roman Marxer
Google: Computers > Software > Configuration Management > Tools
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:
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.
To mount a VOB, invoke from Start ClearCase Administration > Mount VOB or
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:
The elements in each view is defined by a Config spec (Configuration Specification). The default config spec has the following rules:
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:
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
DeltasCM 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.
TriggersTriggers (.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
Rational's user documentation are in Acrobat files stored in folder
Program Files > Rational > ClearCase > bin
The XYZ Systems is rolling out their Configuration Management process and the CMO is giving a presentation on Configuration Status Accounting.
Based on the above statement, which one of the following items is NOT part of Configuration Status Accounting?
Choice 2 The status of authorized changes for a configuration item.
Choice 3 The status of changes by a configuration item in the categories of approved, deferred, and rejected.
Choice 4 A listing of configuration items for the entire system and their status.
Choice 5 The number of design changes by each configuration item during the design phase of the software life cycle.
Which one of the following CANNOT be said of SCM Audits and Reviews?
Choice 2 Emergency changes do not need written approval from the appropriate department head but must be communicated to all other department heads. The changes must be reviewed at the next CCB meeting.
Choice 3 Release Control is the process that correlates the release changes with the output of the release authorization process.
Choice 4 SCM reviews include the Release Authorization Review and the Release Control Review.
Choice 5 SCM audits must include a Change Control Audit that produces a log that is used during the Release Control Review.
Get this print framed for your wall!
Your first name:
Your family name:
Your location (city, country):
Your Email address:
Top of Page