Browse Prior Art Database

Using Code Database to do Associated Publications Work

IP.com Disclosure Number: IPCOM000115426D
Original Publication Date: 1995-May-01
Included in the Prior Art Database: 2005-Mar-30
Document File: 2 page(s) / 66K

Publishing Venue

IBM

Related People

Williams, SG: AUTHOR

Abstract

A method for maintaining publications across releases using the same database system as is used for the program source code is disclosed. This enables multiple levels of the publications to exist at the same level as the code. Changes can be made to an earlier release of publications, and it will "bubble up" to the latest level of the publications--just as it does with the code.

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

Using Code Database to do Associated Publications Work

      A method for maintaining publications across releases using the
same database system as is used for the program source code is
disclosed.  This enables multiple levels of the publications to exist
at the same level as the code.  Changes can be made to an earlier
release of publications, and it will "bubble up" to the latest level
of the publications--just as it does with the code.

      Changes to any of the NCP manuals were made after the previous
release's manuals were finished.  The current release would make its
changes on the hardcopy, to the best of its knowledge, and then hope
that the changes were made correctly.  These changes were made and
reviewed and any errors that were discovered were fixed.  This was an
iterative process which may not have detected all of the errors.
This
seriously affected our 6-sigma quality goal for our publications.

      The information contained in the manuals are needed during the
test phases.  A copy of the hard-copy changes was provided to the
test group for their use.  To make this copy was extremely difficult
because the master copy had paper-clips and staples to remove before
copying.  Due to this, very few copies were made during the test
phases.

      The next release could not make its changes to the manuals
until the immediately previous release finishes its manuals.  This
forces subsequent releases to wait until near the end of their cycles
before they can get a draft of the manual.  Since many subsequent
releases have enhancements to line items developed in earlier
releases, they could have "tested" those lin...