Information Technology Reference
In-Depth Information
requirements elicitation team, including users, customers, system engi-
neers, and developers.
1.3 Overview
Provides a brief overview of the product defined as a result of the
requirements elicitation process.
1.4 Business context
Provides an overview of the business organization sponsoring the devel-
opment of this product. This overview should include the business's mis-
sion statement and its organizational objectives or goals.
2. General Description
2.1 Product Functions
Describes the general functionality of the product, which will be discussed
in more detail below.
2.2 Similar System Information
Describes the relationship of this product with any other products. Specifies
if this product is intended to be stand-alone, or else used as a component of
a larger product.
2.3 User Characteristics
Describes the features of the user community, including their expected
expertise with software systems and the application domain.
2.4 User Problem Statement
This section describes the essential problem(s) currently confronted by the
user community.
2.5 User Objectives
This section describes the set of objectives and requirements for the system
from the user's perspective.
2.6 General Constraints
Lists general constraints placed upon the design team, including speed
requirements, industry protocols, hardware platforms, and so forth.
3. Functional Requirements
This section lists the functional requirements in ranked order. Functional
requirements describe the possible effects of a software system, in other words,
what the system must accomplish. Each functional requirement should be specified
in a format similar to the following:
4. Interface Requirements
This section describes how the software interfaces with other software products or
users for input or output. Examples of such interfaces include library routines,
token streams, shared memory, data streams, and so forth.
4.1 User Interfaces
Describes how this product interfaces with the user.
