Browse Prior Art Database

Message Database

IP.com Disclosure Number: IPCOM000105371D
Original Publication Date: 1993-Jul-01
Included in the Prior Art Database: 2005-Mar-19
Document File: 2 page(s) / 101K

Publishing Venue

IBM

Related People

Condon, JB: AUTHOR [+4]

Abstract

In every development project the maintenance and tracking of messages can be a very time consuming and error-prone process. The current methodology involves the following tasks:

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

Message Database

      In every development project the maintenance and tracking of
messages can be a very time consuming and error-prone process.  The
current methodology involves the following tasks:

o   Monitoring message creations and changes
o   Verifying the message contents
o   Maintaining and tracking message information such as message
    numbering, internal id assignments, routing information, and
    recording of the component/subcomponent that issued the message
o   Generating text, header, and online-help files
o   Maintaining an accurate list of all messages, including list by
    subcomponent/component
o   Notifying Information Development of message changes to ensure
    that documentation is consistent with the actual message content
o   Notifying the test department of message changes to ensure that
    the messages have been adequately tested

     Currently these tasks are done manually, and are both time
consuming and error prone.  If ID or Test is not notified of message
changes, the documentation becomes outdated or the test results are
invalid.  Coding errors are prone to occur in the text and/or header
files.  Errors in message number assignments can occur (such as two
messages being assigned the same message numbers or internal
identifiers).  If these errors are caught early in the development
cycle, the impact or scheduling can be kept to a minimum.  However,
if these errors are not caught until late in the cycle, correcting
them can impact the schedules for ID, Test, and Development.  A
Message Database (AMDB) was created to solve these types of errors.

      AMDB solves these problems because it is a fully automated
tool.  The tool will perform the following functions:

o   Automatic notification of the appropriate persons upon the
    creation, modification, or deletion of a message.
o   Automatic generation of the internal ids and message numbers.
    This prohibits the possibility of duplicate message-number
    assignments.
o   Automatic generation of the source files for message text,
    message header, and online-help files, along with those required
    for online help on OS/2*.
o   Automatic generation of a message listing according to component
    or subcomponent.
o   Automatic generation of Bookmaster files for use in documentation
    and by ID.

     Because the tool performs these tasks automatically, the
possibility of errors in these tasks has been eliminated.  These
tasks have been reduced to less than a one person effort.

      AMDB is designed to function on VM.  Access to the message
library for a specific product is controlled by assigning each
product a VM disk.  A user is then authorized to 'WRITE" to the disk
if the user has authority to edit messages.  A user with 'READ'"
access can only generate output files and obtain reports on the
existing messages.

AMDB consists of the following parts:

o  ...