|
Chicago Configuration
Management
Chicago configuration
management seems to be a hot topic also.
In an article on
Configuration Management Best practice I came across recently it
stated organizations are starting to realize that as the complexity
of distributed applications increases, and the number of people
working on the same system grows larger, there's a pressing need for
change management (CM) products that track the alterations made to
software during development.
Without sufficient
tracking and management throughout a new project's life cycle, there
can be costly delays in a system rollout.
Chicago configuration
management – What has this got to do with Chicago?
Well it seems that a
certain Bank in Chicago went live with a new system
after a substantial development cycle only to have a resounding
failure. Why? Goes to two things really Configuration management and
testing.
The concept of change
management-sometimes called configuration management or version
control-isn't new; it's been around since the heyday of the
mainframe.
With the advent of
minicomputers and midrange systems, two rudimentary version control
systems for the Unix environment were created: Source Code Control
System (SCCS) by AT&T Bell Labs, and Revision Control System
(RCS) by Purdue
University in West Lafayette, Ind.
Both are still bundled
with most Unix operating systems. Over the past few years, however,
more sophisticated CM systems have emerged with features that manage
all phases of software development within distributed environments.
THE ASSET MANAGEMENT TOOLKIT
Each
item included is of the highest quality, tailor made to cover a
different aspect and issue. It includes presentations,
questionnaires, guidelines, fact sheets.... and whole gamut of
material specifically put together to both introduce and take you
through Asset Management.
It comprises the
following components (click
here)
| 
