12 Functional Design Document Template

Prepared for
[Customer Name]

Project
[Project Name]

Prepared by
Eduardo

Contributors
[Document contributors]

Error! Unknown document property name.Error!

Unknown document property name.

Revision and Signoff Sheet

Change Record
Date

Editor

Revision Notes
Initial draft for review/discussion

Directions for Using this Template

Read the template guidance portion of this document (blue Arial font within brackets)
to understand the information that should be placed into each section of this
template. Then delete the guidance text and replace the placeholder within the
<<Begin Test Here>> with your response. There may be additional guidance in the
appendices of some documents, which should also be deleted once it has been used.
This template uses the document property fields throughout for consistent one-stop
update of these details. These properties should be updated during the initiation of
document creation.

Template Guidance
Description: The Functional Design Document provides an overview of the business issue to be
addressed, a mock-up of the User Interface (UI) design, and a plain English synopsis of the logic
anticipated. This document provides the customer with the opportunity to approve the high-level
design before the effort is made to develop a detailed or technical design.
Justification: Its important that the solution design be documented and approved by the customer to
avoid confusion and ensure that the customers needs are being met by the proposed design.
Primary Roles: Application Consultant, Key Users
Optional Roles: Project Manager and Customer Project Manager

Table of Contents
1 Design Planning Summary....................................................................2
Subsection Heading 2..................................................................................................2
2 Business Overview...............................................................................3
Subsection Heading 2..................................................................................................3
3 Overview of Design Concepts................................................................4
Subsection Heading 2..................................................................................................4
4 Solution Architecture...........................................................................5
Subsection Heading 2..................................................................................................5

1 Design Planning Summary

[Description: The Design Planning Summary section provides an overview of this
specific development project, a synopsis of the situation that led to the need, and a
short description of the issues that the development project is going to solve, as well
as a general description of the proposed solution and the rationale for the solution.
Any attempts to resolve the issue through other means should also be noted and
explained.]

Subsection Heading 2
Subsection text
Paragraph Heading 7
Paragraph text

2 Business Overview
[Description: The Business Overview section should provide a detailed explanation of
the business logic that lead to the need for a solution. This section should include the
specific business need being addressed and the rationale for the business need. This
information will help the development team to better address the issue and can avoid
delays during development.]

Subsection Heading 2
Subsection text
Paragraph Heading 7
Paragraph text

3 Overview of Design Concepts

[Description: The Overview of Design Concepts section should provide the high-level
design of the proposed solution. This design should include mock-up screen shots for
the proposed user interface, and a plain English description of the programming logic
proposed, as well as the anticipated process flow. The purpose of the solution design
is to allow the customer to approve the concepts before committing resources to the
technical design.]

Subsection Heading 2
Subsection text
Paragraph Heading 7
Paragraph text

4 Solution Architecture
[Description: The Solution Architecture section should provide an overview of how the
proposed design fits into the overall solution structure. This section should include
any interactions or integrations with other solution processes or with other
applications. This section should also include any solution configuration changes that
will be required to develop and implement the proposed solution.]

Subsection Heading 2
Subsection text
Paragraph Heading 7
Paragraph text