<Project Name>
Bill of Materials
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).]
[To customize automatic fields in Microsoft Word (which display a gray background when selected), select File>Properties and replace the Title, Subject and Company fields with the appropriate information for this document. After closing the dialog, automatic fields may be updated throughout the document by selecting Edit>Select All (or Ctrl-A) and pressing F9, or simply click on the field and press F9.á This must be done separately for Headers and Footers.á Alt-F9 will toggle between displaying the field names and the field contents.á See Word help for more information on working with fields.]
Revision History
|
Date |
Version |
Description |
Author |
|
<dd/mmm/yy> |
<x.x> |
<details> |
<name> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Table of Contents
1.3áááá Definitions, Acronyms and Abbreviations
2.1áááá Inventory of Materials
2.1.1áááááááá Handling Considerations
2.2áááá Inventory of Software Contents
2.5áááá Installation Instructions
2.6áááá Known Errors and Problematic Features
Bill of Materials
[Provide an overview of the entire document.]
[Describe the purpose of the software to which this document applies.]
[Identify the recipients for the items identified in the Bill of Materials, for example, the source code is typically not released to all recipients]
[This subsection should provide the definitions of all terms, acronyms, and abbreviations required to properly interpret the Bill of Materials. This information may be provided by reference to the project Glossary.]
[This subsection should provide a complete list of all documents referenced elsewhere in the Bill of Materials.á Each document should be identified 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 should describe what the rest of the Bill of Materials contains and explain how the document is organized.]
[List all the physical media (CDs, floppies, etc) and associated documentation that make up the software version being released. Identify numbers, titles, abbreviations, dates, versions and release numbers as applicable.]
[Describe safeguards for handling the material, such as concerns for static and magnetic fields, and instructions and restrictions regarding duplication and licensing.
[List all the files that make up the software version being released. Identify numbers, titles, abbreviations, dates, versions and release numbers as applicable.]
[List all the changes incorporated into the software version since the previous version. Identify, as applicable, the problem reports and Change Requests associated with each change. Describe the effect of each change on software use or operation as applicable.]
[Identify any site-unique data contained in the software.]
[Provide or reference the following information:
╖ Instructions for installing the software, and
╖ Procedures for determining whether the version has been installed properly.
[Identify any possible problems or known errors with the software at the time of release. Describe steps that can be taken to recognize, avoid, correct or handle the problematic features.]