Software Engineering

Document Title
Document Description
1. Functional 
Decomposition 
Description
This document describes the manner by which the software 
functionality has been decomposed into subfunctions. The 
functional hierarchy diagrams present the levels of functional 
breakdown of functional requirements to components and units.
2. Functional 
Component 
Specifications
Software functional and performance specifications for 
compound elements of the software functional configuration. 
These specifications represent the subrequirements necessary to 
support the achievement of higher-level functional components 
or software product requirements.
3. Functional Unit 
Specifications
Software functional, performance, and design specifications 
for the basic elements of the software functional configuration. 
These specifications represent the subrequirements necessary to 
support the achievement of a lowest-level functional component.
4. Functional 
Interface 
Specifications
Technical description of each software functional interface. 
Identifies the purpose of the interface and provides the general 
information concerning the type of information exchanged by the 
interface.
5. Software 
Behavioral 
Models
The behavioral models describe the functional sequences, 
control, and data flows for complex functions. The behavioral 
models establish the software performance and resource 
utilization specifications for each thread of behavior. Failure 
modes and effects are described, and fault detection, isolation, 
and recovery procedures should be described.
6. Data Persistence 
Specifications
Documents the requirements for data persistence, including 
the data storage capacity requirements and data storage and 
retrieval transactions.
7. Requirements 
Traceability 
Matrix
Documents how each requirement in the software specifications 
has been satisfied by the elements of the functional architecture.
8. Software 
Nomenclature 
Document
Documents the characteristics of every function, data item, and 
resource identified in the functional architecture to provide a 
consistent glossary of named elements.

---

This page intentionally left blank

---