<Project Name>
Release Notes
Version <1.0>
[Note: The following template is provided for use with the Rational Unified Process. Text enclosed in square brackets and displayed in blue italics (style=InfoBlue) is included to provide guidance to the author and should be deleted before publishing the document. A paragraph entered following this style will automatically be set to normal (style=Body Text).]
Revision History
|
Date |
Version |
Description |
Author |
|
<dd/mmm/yy> |
<x.x> |
<short description of release> |
<Author Name> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
1.4 Definitions, Acronyms, and Abbreviations
Release Notes
[The introduction of the Release Notes provides an overview of the entire document. It includes the disclaimer of warranty, purpose, scope, definitions, acronyms, abbreviations, references and overview of this Release Notes.]
<Company Name> makes no representations or warranties, either express or implied, by or with respect to anything in this document, and shall not be liable for any implied warranties of merchantability or fitness for a particular purpose or for any indirect, special or consequential damages.
Copyright © 1999, <Company
Name>.
All rights reserved.
GOVERNMENT RIGHTS LEGEND: Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the applicable <Company Name> license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (Oct 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14, as applicable.
"<Company Name>" and <Company Name>'s products are trademarks of <Company Name>. References to other companies and their products use trademarks owned by the respective companies and are for reference purpose only.
The purpose of the Release Notes is to communicate the major new features and changes in this release of the <Project Name>. It also documents known problems and workarounds.
This document describes the <Project Name>.
[This subsection provides the definitions of all terms, acronyms, and abbreviations required to properly interpret the Release Notes. This information may be provided by reference to the project's Glossary.]
[This subsection provides a complete list of all documents referenced elsewhere in the Release Notes. Identify each document by title, report number if applicable, date, and publishing organization. Specify the sources from which the references can be obtained. This information may be provided by reference to an appendix or to another document.]
[This subsection describes what the rest of the Release Notes contains and explains how the document is organized.]
[A description of the release is presented here, including release-defining characteristics or features. The description needs to be brief, however, and simply clarifies the release definition.]
This product has been tested on the following platforms or with the following products:
- [List products or platforms here.]
[Also list any product operating environment requirements here.]
[Describe the process for upgrading from previous product releases.]
The following new features appear in this release:
- [List of new features.]
[Describe any general limitations that affect overall functionality.]
[Describe the defect or bug symptom and any workarounds, if they exist.]