Revision
History
|
Date |
Issue |
Description |
Author |
|
<mm/dd/yy> |
<x.x> |
<details> |
<name> |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Revisions to documents
should follow the procedures
outlined in the “Versioned
Documents in Microsoft Word”
in the Playbook->Methodology->General->Guidelines
and Standards section of
the Software Development
Process and Procedures Database.
Table of
Contents
1. Overview
2. Scope
3. References
4. High-Level
Requirements
4.1 <Requirement
1>
4.n <Requirement
n>
5. Approval
High-Level
Requirements Statement (HLRS)
The
High-Level Requirements
Statement (HLRS) document
provides a brief description
of each product/project
requirement. The high-level
requirements capture the
initial set of requirements
and these requirements are
defined in more detail as
the project progresses.
All
sections of this document
are required.
This
section contains a brief
description, overview, or
objective of these requirements.
Define the problem that
is to be resolved.
This
section defines the scope
of the requirements. Include
a brief description of what
the requirements apply to,
what is affected or influenced
by the requirements.
Any
related or referenced documents
are listed here in bullet
form. Include details about the document location
in addition to the title.
·
<Document
Reference 1 and location>
·
<Document
Reference n and location>
Each
of the requirements are
listed and described in
the sections below. A brief
description (about a paragraph)
is provided that explains
to the reader what the requirement
is about. Refrain from
discussing “how” something
is to be implemented, but
define “what” must be implemented.
Provide
requirement description.
Provide
requirement description.
Required
The following people have provided input,
reviewed and approved this
document as being correct
and complete.
