Managing Software Changes (G06.24+)

Managing Software Changes427169-003
A-1
A What Is in a Softdoc
A software release document, commonly known as a softdoc, provides information
regarding a software product revision (SPR). Software release documents are issued
as either:
Softdoc (see also Softdoc Example)
Softdoc Addendum (see also Softdoc Addendum Example)
Softdocs supplement a product’s manuals with information about:
Interproduct and intraproduct revision relationships
Installation and migration considerations
New features
Problems corrected
Known problems still remaining
Other information about the revision deemed important enough to be issued with
the revision rather than waiting for the appropriate manual to be updated and
distributed
Softdoc
A softdoc describes a new product or changes to an existing product that are so major
that the product now has a new product version, called an initial product version
update (PVU). Softdocs for initial PVUs contain these sections:
Product Name is the official name of the product.
Product Number is the product number (Tnnnn), followed by the product version
suffix; for example, T7862G05.
Date contains the nominal SPR date.
Copyright Notice indicates the year this softdoc was released.
Revision History indicates any revisions made to this softdoc. For example:
Revision History:
# Rev.-Date Description of changes in each revision
1 02JUN1999 Added Requisite IPMs needed for G05.xx and added
items 13 - 16 to Known Problems Remaining
2 18AUG1999 Added workaround for Known Problems Remaining 13
and updated Known Problems Remaining 14