Functional Design Specification for [Project Name]

Version 1.0

Prepared by: [Author's Name goes here]

Date: [Date the draft was completed goes here.]

1

Template provided by:

How Software Gets Done

2

Table of Contents

Table of Contents

Revision History

Overview of Business Requirements............................................................................................4

System Specifications...................................................................................................................4

Output/Report Specifications........................................................................................................6

[Output/Report Specification Title Goes Here]....................................................................7

[Output/Report Specification Title Goes Here]....................................................................7

[Output/Report Specification Title Goes Here]....................................................................8

Decision Tables.............................................................................................................................8

Data Analysis................................................................................................................................8

Logical Database Model...............................................................................................................9

Data Conversion............................................................................................................................9

Code Value Definitions.................................................................................................................9

External System Dependencies...................................................................................................10

Testing Needs..............................................................................................................................10

3

Revision History

This section records the change history of this document.

Name Date Reason For Changes Version

4

Overview of Business Requirements

The most important design consideration in any project is to design the project based on the business requirements. The following section provides an overview of the business requirements. For more information about the business requirements see the Business Requirements document for this project.

[Overview of the Business Requirements goes here]

System Specifications

Certain system requirements exist for this project as follows:

(If there is a prototype…)

The prototype that describes the input specifications can be found [enter instructions on how to find and install the prototype.]

(OR, if no prototype, describe system requirements and/or create mock-ups of the screens as shown here…)

[System Specification Name Goes Here]

Inputs Processing Outputs

5

[System Specification Name Goes Here]

Inputs Processing Outputs

6

[System Specification Name Goes Here]

Inputs Processing Outputs

Output/Report Specifications

Certain output requirements exist for this project as follows:

(If there is a prototype…)

The prototype that describes the output specifications can be found [enter instructions on how to find and install the prototype.]

(OR, if no prototype, describe input requirements and/or create mock-ups of the screens, and/or report layouts, as shown starting on the next page…)

7

[Output/Report Specification Title Goes Here]

[Enter a description of the output specification here]

[Output/Report Specification Title Goes Here]

[Enter a description of the output specification here]

8

[Output/Report Specification Title Goes Here]

[Enter a description of the output specification here]

Decision Tables

These tables provide a set of business data that can be used by the system to make decisions critical during system processing. The tables specify a set of conditions and their corresponding actions. They allow us to specify complex policies and decision-making rules

Business or Data Condition Corresponding Action Output or New State

[Enter a Business Condition here] [Internal action resulting] [New state or output]

[Enter a Business Condition here] [Internal action resulting] [New state or output]

[Enter a Business Condition here] [Internal action resulting] [New state or output]

[Enter a Business Condition here] [Internal action resulting] [New state or output]

[Enter a Business Condition here] [Internal action resulting] [New state or output]

[Enter a Business Condition here] [Internal action resulting] [New state or output]

… … …

Data Analysis

The data analysis consists of specific characteristics and behavior values of data elements. It also includes an optional data flow diagram and a data field definition table. This section also includes some sample data as a description of the data to be stored in the database.

Data Element Characteristics Behavior of Element

[Data Element goes here] [Text, Boolean, Long, etc.] [Defaults, range, size, etc.]

9

Data Element Characteristics Behavior of Element

[Data Element goes here] [Text, Boolean, Long, etc.] [Defaults, range, size, etc.]

[Data Element goes here] [Text, Boolean, Long, etc.] [Defaults, range, size, etc.]

[Data Element goes here] [Text, Boolean, Long, etc.] [Defaults, range, size, etc.]

[Data Element goes here] [Text, Boolean, Long, etc.] [Defaults, range, size, etc.]

[Data Element goes here] [Text, Boolean, Long, etc.] [Defaults, range, size, etc.]

[Data Element goes here] [Text, Boolean, Long, etc.] [Defaults, range, size, etc.]

[Data Element goes here] [Text, Boolean, Long, etc.] [Defaults, range, size, etc.]

… … …

Logical Database Model

[Add a logical database model or a reference to the logical database model here.]

Data Conversion

Existing data must be converted from a legacy system. This section describes the conversion procedure. The data is stored in [type of database] on [name of the system where data is stored]. The data will be converted to [type of database] on [name of the machine where it will be stored].

The conversion will be accomplished by [describe the conversion process here.]

Code Value Definitions

This system uses a set of codes and shortened forms throughout the data to represent status and other specific information. The following table describes the value of each code in the system:

Field Name Code Value

[Table and Field Name goes here] [code 1 goes here][code 2 goes here][code 3 goes here][code 4 goes here]…

[value of code 1 goes here][value of code 2 goes here][value of code 3 goes here][value of code 4 goes here]…

[Table and Field Name goes here] [code 1 goes here][code 2 goes here][code 3 goes here][code 4 goes here]…

[value of code 1 goes here][value of code 2 goes here][value of code 3 goes here][value of code 4 goes here]…

[Table and Field Name goes here] [code 1 goes here][code 2 goes here][code 3 goes here][code 4 goes here]…

[value of code 1 goes here][value of code 2 goes here][value of code 3 goes here][value of code 4 goes here]…

10

Field Name Code Value

[Table and Field Name goes here] [code 1 goes here][code 2 goes here][code 3 goes here][code 4 goes here]…

[value of code 1 goes here][value of code 2 goes here][value of code 3 goes here][value of code 4 goes here]…

External System Dependencies

The new system depends on certain external systems to complete some or all of its tasks. This section lists those dependencies explicitly:

External System Dependencies on that System

[System Name goes system here.] [List of dependencies on that system goes here.]

[System Name goes system here.] [List of dependencies on that system goes here.]

[System Name goes system here.] [List of dependencies on that system goes here.]

Testing Needs

This system requires testing before it can be released to the user population. This section provides a general overview of the different testing that should be completed. This section does not replace the Test Plan. It is provided here as a guide for the author of that document.

[Describe testing needs in general here.]

11