Browse Prior Art Database

Automated Software Product Inventory Control

IP.com Disclosure Number: IPCOM000114436D
Original Publication Date: 1994-Dec-01
Included in the Prior Art Database: 2005-Mar-28
Document File: 4 page(s) / 171K

Publishing Venue

IBM

Related People

Calvert, N: AUTHOR [+3]

Abstract

Described is a mechanism to manage software products across environments via a set of common tools/structures.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 30% of the total text.

Automated Software Product Inventory Control

      Described is a mechanism to manage software products across
environments via a set of common tools/structures.

      Software is a composite of many different entities.  These
entities can exist across environments associated with the
development, delivery, and usage of the software.  The
characteristics of software entities may themselves be different.
For example, a program in the development environment may be a source
part while a program in the production environment may be an external
object or load module.  The owner of these entities is usually the
same in these environments.  Software entities may also be part of a
software product which exists at some maintenance level.  It becomes
very important to correlate software product control information for
a product across these environments such that development activities,
maintenance activities, and problem determination activities can be
done with some order and control.

      The problem today is that there is no good mechanism to manage
software products across environments via a set of common
tools/structures.  For example, an IBM development tool provides a
mechanism for developing source parts for a product but the tool
manages source parts in a totally different manner than the way the
production environment handles its corresponding objects in the
Licensed Program (LP) production environment.

      The objective of this disclosure is to increase software
management process efficiencies by defining common processes and
structures for software.  These common processes and structures allow
information obtained during LP Library Control System Setup to be
used throughout the LP's life cycle to manage the software.

      Another objective of this disclosure to define how LP packaging
information defined during the development cycle may be propagated to
environments in which software may exist.  These environments consist
of the following:
  o  Development environment - This is the environment in which
      software is developed.  It contains the source entities from
      which LP objects are formed.
  o  Intermediate production environment - This is the environment in
      which released software may exist prior to being installed.
  o  Production environment - This is the environment in which
      software is installed within an operating system.  Software
      packaged as LPs provide some well defined set of functions.

      Product control information is defined during the development
phase.  This information provides a mechanism to:
  1.  Declare up-front the data needed to manage software in the
       development environment.
  2.  Manage the transition of software in the development
environment
       to the production environments
  3.  Insure the consistency and completeness of information across
all
       environments.

The...