Re: CM tools and Ada

[ploedere@TARTAN.COM]

Re: Lisa Lane (3/15) and Jim Showalter (3/17) messages

For the last two years, we have designed and implemented a Configuration
Management Assistant (CMA) under the STARS program. CMA addresses a number
of configuration management issues, particularly in the setting of software
reuse, e.g., the integration of systems from independently versioned and
administered subsystems. The main theme of CMA is to help the user decide
BEFORE building the system, whether the configuration is likely to (not)
function properly and to pin-point potential troublespots. Put in Ada terms,
CMA will for example tell which Ada libraries need to be combined to form a
complete system configuration, and which versions of these libraries fit
together.

We are most interested to hear from the general Ada user community what
their requirements are on CM in Ada projects. Particularly, we are
struggling with the issue on where the boundaries are between a tool like
CMA and source and object version control, Ada librarian functionality,
release policies and procedures, engineering change request systems, etc.
While we could incorporate all such functionality in CM, we would prefer
a less monolithic approach. Which other tools should we interface with ?

If you have feedback that you don't want to post to the general public,
or if you want to know more about CMA, please send e-mail to 
ploedere@tartan.com.

Erhard Ploedereder
Chief Scientist
Tartan, Inc.