> **Technical**
>
> **SPECIFICATIONS**
>
> *Project id [(each project will have a project id assigned
> OCIO)]{.mark}*
>
> *Project or System Name*
>
> **U.S. Small Business Administration**
>
> Month, Year

**Revision Sheet**

  ----------- ---------- --------------------------------------------------
  **Release   **Date**   **Revision Description**
  No.**                  

  Rev. 1      3/22/04    Technical Specifications Template and Checklist

                         

                         

                         

                         

                         

                         
  ----------- ---------- --------------------------------------------------

[Page \#]{.underline}

1.0 GENERAL INFORMATION [1-1](#general-information)

1.1 Purpose [1-1](#purpose)

1.2 Scope [1-1](#scope)

1.3 System Overview [1-1](#system-overview)

1.4 Project References [1-2](#project-references)

1.5 Terms and Abbreviations [1-2](#terms-and-abbreviations)

1.6 Points of Contact [1-2](#points-of-contact)

2.0 SYSTEM CHARACTERISTICS [2-1](#system-characteristics)

2.1 System Architecture [2-1](#system-architecture)

2.2 System/Subsystem Site Map [2-1](#systemsubsystem-site-map)

2.3 System/Subsystem Partitions and Functions
[2-1](#systemsubsystem-partitions-and-functions)

2.3.1 Unit/*Function* [2-1](#unitfunction)

2.3.2 Unit/*Function* [2-2](#unitfunction-1)

2.4 Adaptability [2-2](#adaptability)

2.5 System Logical Flow [2-2](#system-logical-flow)

3.0 ENVIRONMENT [3-1](#environment)

3.1 Equipment Environment [3-1](#equipment-environment)

3.2 Communications Environment [3-1](#communications-environment)

3.2.1 Network [3-1](#network)

3.2.2 Interface Protocol [3-1](#interface-protocol)

3.3 Software Environment [3-1](#software-environment)

3.4 Software Interfaces [3-2](#software-interfaces)

3.5 Diagnostics [3-2](#diagnostics)

4.0 SECURITY [4-1](#security)

4.1 Control Points [4-1](#control-points)

4.2 Vulnerabilities [4-1](#vulnerabilities)

4.3 Safeguards [4-1](#safeguards)

RECOMMENDED POINT OF CONTACT FOR THIS DOCUMENT: OCIO Point of Contact

*The Point of Contact for the Document coordinates and insures that the
document is completed. This individual as well as others in the program
areas may also contribute in a collaborative fashion as is often
necessary in systems development projects.*

*[**NOTE TO AUTHOR:** Italicized text throughout this template is
provided solely as background information to assist you in creating this
document. Please delete all such text, as well as the instructions in
each section, prior to submitting this document. **ONLY YOUR
PROJECT-SPECIFIC INFORMATION SHOULD APPEAR IN THE FINAL VERSION OF THIS
DOCUMENT**.]{.mark}*

*[The Technical Specifications provides a listing of the specifications
of the system and its subsystems, as well as a detailed description of
the system/subsystem functions. It also defines in detail the interfaces
with other systems and subsystems and the facilities to be used for
accomplishing the interfaces. For each subsystem, include such
information as timing requirements, equipment needs, communications
environment, support software, security, and input and output
records.]{.mark}*

# GENERAL INFORMATION

## 1.1 Purpose

*Describe the purpose of the Technical Specifications.*

## 1.2 Scope

*Describe the scope of the Technical Specifications as it relates to the
project.*

## 1.3 System Overview

-   *Major functions performed by the system*

-   *Describe the architecture of the system in non-technical terms
    (e.g., client/server, web-based, etc.)*

-   *User access mode (e.g., graphical user interface)*

-   *Responsible organization*

-   *System name or title*

-   *System code*

-   *System category:*

```{=html}
<!-- -->
```
-   *Major application: performs clearly defined functions for which
    there is a readily identifiable security consideration and need*

-   *General support system: provides general ADP or network support for
    a variety of users and applications*

```{=html}
<!-- -->
```
-   *General description*

-   *System environment or special conditions*

## 1.4 Project References

*Provide a list of the references that were used in preparation of this
document. Examples of references are:*

-   *Previously developed documents relating to the project*

-   *Documentation concerning related projects*

-   *SBA standard procedures documents*

## 1.5 Terms and Abbreviations

*Provide a list of the terms and abbreviations used in this document and
the meaning of each.*

## 1.6 Points of Contact

*Provide a list of the points of organizational contact (POCs) that may
be needed by the document user for informational and troubleshooting
purposes. Include type of contact, contact name, department, telephone
number, and E-mail address (if applicable). Points of contact may
include, but are not limited to, helpdesk POC, development/maintenance
POC, and operations POC.*

# SYSTEM CHARACTERISTICS

## 2.1 System Architecture

*Provide a description of the system, subsystem, communications, etc.,
in terms of their overall relationships. Accompany the description with
a graphic representation that depicts the interrelationships of the
major components of the system. Show the communications network for
systems that are networked or that support distributed processing.*

## 2.2 System/Subsystem Site Map

*Where applicable, provide a hierarchal diagram that depicts the
navigation of the system functions.*

## 2.3 System/Subsystem Partitions and Functions

*Although the descriptions of the system/subsystem functions may be
refined and more detailed as a result of the continuing analysis and
design effort, they must maintain a direct relationship to the system
functions established in the FRD and be described in such a way that the
system/subsystem environment can be related to them.*

*Describe the system/subsystem partitions and functions, documenting the
traceability between the functional and data requirements and the
defined subsystem. Where applicable, include a site map.*

## 2.3.1 Unit/*Function* 

+--------------------+-------------------------------------------------+
| **Business         | *Describe the business functions being          |
| Function**         | performed by the software unit*                 |
+--------------------+-------------------------------------------------+
| **User Entry**     | *User response/entry*                           |
+--------------------+-------------------------------------------------+
| **System           | *system response*                               |
| Response**         |                                                 |
+--------------------+-------------------------------------------------+
| **Application      | *Name and description*                          |
| Component**        |                                                 |
+--------------------+-------------------------------------------------+
| **Stored Procedure | *Stored procedure name and identifier*          |
| n:**               |                                                 |
+--------------------+-------------------------------------------------+
| -   Passing        |                                                 |
|     Parameter:     |                                                 |
+--------------------+-------------------------------------------------+
| -   Result Set:    |                                                 |
+--------------------+-------------------------------------------------+
|                    |                                                 |
+--------------------+-------------------------------------------------+
|                    |                                                 |
+--------------------+-------------------------------------------------+

**Screen/Report Layout**

![](media/image1.wmf){width="1.9944444444444445in"
height="1.4833333333333334in"}

Field Level Validations

  --------------------- -------------------------------------------------
  *Field name*          *List field level validations (i.e. numeric,
                        date, etc.)*

                        

                        
  --------------------- -------------------------------------------------

Business Logic

  --------------------- -------------------------------------------------
  *Business Rule*       *Description of the business rule (i.e.
                        relational edit, calculation, etc.)*

                        
  --------------------- -------------------------------------------------

## 2.3.2 Unit/*Function* 

*Continue the above format for each of the unit/functions.*

## 2.4 Adaptability

*Provide a description of the capability incorporated for adapting the
system/subsystem to changing requirements, such as anticipated
operational changes, interaction with new or improved systems, and
planned periodic changes. Components and procedures designed to be
subject to change will be identified.*

## 2.5 System Logical Flow

*Present the logical flow of the system/subsystem. Supplement the
representation with a program design language presentation, a narrative
presentation, or a combination of the two. Graphics should provide an
integrated presentation of the system/subsystem dynamics, entrances and
exits, and interfaces with other software units. Represent all modes of
operations, priorities, cycles, special handling and general flow of
control.*

# ENVIRONMENT

## 3.1 Equipment Environment

*Provide a description of the equipment required for the operation of
the system/subsystem. Include descriptions of the equipment presently
available, as well as a more detailed discussion of the characteristics
and impact of any new equipment necessary for system operation.*

## 3.2 Communications Environment

*Describe the data communications environment of the system.
Additionally, provide detailed schematics of the portions of the
communications environment that directly relate to the system or
subsystem being documented. If a standard communications environment is
being used, reference can be made to it.*

### 3.2.1 Network

*Describe the network configuration and characteristics if non-SBA
standard configuration or Web-based, including, at a minimum, the
following:*

-   *Transmission requirements and technique*

-   *Data transfer rates (baud rates)*

-   *Gateways*

-   *Geographic locations*

-   *Required system use times, if any*

-   *Line speed capability*

### 3.2.2 Interface Protocol

*Identify all protocols.*

## 3.3 Software Environment

*Describe the software with which the system/subsystem must interact.
Include both support software and test software, if needed. Provide the
correct name, description, and documentation references of each such
software system, subsystem, and program. Include a reference to the
operating system to be used, the database management system (if any),
and the language for the following:*

-   *compiler*

-   *assembler*

-   *program*

-   *query*

## 3.4 Software Interfaces

*Provide a description of the interfaces with other application software
units, including those of other operational capabilities and from other
government agencies. For each interface, specify the file format
(input/output) and delivery media.*

## 3.5 Diagnostics

*Describe diagnostic procedures that will allow identification and
classification of system/subsystem problems.*

-   *source documents and their disposition*

-   *security and privacy considerations*

# SECURITY

*To control dissemination of sensitive information, all or portions of
this chapter may be maintained and distributed separately from the
remainder of the document; typically a separate System Security Plan
will be developed and referenced here.*

*System/subsystem specific roles will be defined here.*

## 4.1 Control Points

*A control point can be located at any interface at which there is
movement of data within or between sites. Describe the points in the
system at which there is a known vulnerability that requires specific
safeguards.*

## 4.2 Vulnerabilities

*A design, implementation, or operational condition inherent in the
application or system that lends itself to error, loss, or compromise of
information, or denial of service is a system vulnerability. Describe
the vulnerabilities at each control point.*

## 4.3 Safeguards

*Describe the safeguard requirements at each control point to reduce
vulnerabilities.*