10/27/23, 2:36 PM Software Design Specification Template
SOFTWARE DESIGN SPECIFICATION GUIDELINES 2021
What is System Design?
Systems design is the process of defining elements of a system like modules, architecture,
components and their interfaces and data for a system based on the specified requirements. It is
the process of defining, developing and designing systems which satisfies the specific needs and
requirements of a business or organization.
What is SDD?
The System Design Document (SDD) is a documentation that describes how the functional and
nonfunctional requirements recorded in the Requirements Document; transform into more
technical system design specifications from which the system is built. The SDD documents the
high-level system design and the low-level detailed design specifications.
The SDD describes design goals and considerations, provides a high-level overview of the
system architecture, and describes the data design associated with the system, as well as the
human-machine interface and operational scenarios.
The high-level system design is further decomposed into low-level detailed design specifications
for each system component, including hardware, internal communications, software, system
integrity controls, and external interfaces. The high-level system design serves as primary input
to the Preliminary Design Review (PDR). The low-level detailed design serves as input to the
Detailed Design Review (DDR).
SOFTWARE DESIGN SPECIFICATION TEMPLATE
Note: - You should begin to develop the software design specification after completion of the
software requirements specification. The software requirements feed the design task.
The software design specification focuses on how the system will be constructed. It includes four
models: data design (section 2.0), architectural design (section 3.0), interface design (section 4.0)
and component-level design (section 3.0).
©Juliet 2021 Page 1
about:blank 1/7
, 10/27/23, 2:36 PM Software Design Specification Template
SOFTWARE DESIGN SPECIFICATION GUIDELINES 2021
(Section 1.0 is repeated from the Software Requirements Specification. This section provides
background information about the System.)
Note:-Page one of your submitted SDS documentation should be your cover page and page two
the document Table of Contents (TOC).
Section One.
1.0 Introduction
This section provides an overview of the entire requirement document. This document describes
all data, functional and behavioral requirements for the proposed system.
An Example:
The purpose of this document is to describe in sufficient detail how the proposed system is to be
constructed. The System Design Document translates the Requirement Specifications into a
document from which the developers can create the actual system. It identifies the top-level
system architecture, and identifies hardware, software, communication, and interface
components.
1.1 Goals and objectives
Overall goals and proposed system objectives are described.
1.2 Statement of scope
A description of the proposed system software is presented. Major inputs, processing
functionality and outputs are described without regards to implementation detail.
Rank the major processing functionality from the developer’s point of view. Use a simple
ranking system such as: essential, desirable and future requirements. This should represent what
you think you can accomplish in the time frame of a semester. The essential requirements, you
are sure you can complete.
©Juliet 2021 Page 2
about:blank 2/7
SOFTWARE DESIGN SPECIFICATION GUIDELINES 2021
What is System Design?
Systems design is the process of defining elements of a system like modules, architecture,
components and their interfaces and data for a system based on the specified requirements. It is
the process of defining, developing and designing systems which satisfies the specific needs and
requirements of a business or organization.
What is SDD?
The System Design Document (SDD) is a documentation that describes how the functional and
nonfunctional requirements recorded in the Requirements Document; transform into more
technical system design specifications from which the system is built. The SDD documents the
high-level system design and the low-level detailed design specifications.
The SDD describes design goals and considerations, provides a high-level overview of the
system architecture, and describes the data design associated with the system, as well as the
human-machine interface and operational scenarios.
The high-level system design is further decomposed into low-level detailed design specifications
for each system component, including hardware, internal communications, software, system
integrity controls, and external interfaces. The high-level system design serves as primary input
to the Preliminary Design Review (PDR). The low-level detailed design serves as input to the
Detailed Design Review (DDR).
SOFTWARE DESIGN SPECIFICATION TEMPLATE
Note: - You should begin to develop the software design specification after completion of the
software requirements specification. The software requirements feed the design task.
The software design specification focuses on how the system will be constructed. It includes four
models: data design (section 2.0), architectural design (section 3.0), interface design (section 4.0)
and component-level design (section 3.0).
©Juliet 2021 Page 1
about:blank 1/7
, 10/27/23, 2:36 PM Software Design Specification Template
SOFTWARE DESIGN SPECIFICATION GUIDELINES 2021
(Section 1.0 is repeated from the Software Requirements Specification. This section provides
background information about the System.)
Note:-Page one of your submitted SDS documentation should be your cover page and page two
the document Table of Contents (TOC).
Section One.
1.0 Introduction
This section provides an overview of the entire requirement document. This document describes
all data, functional and behavioral requirements for the proposed system.
An Example:
The purpose of this document is to describe in sufficient detail how the proposed system is to be
constructed. The System Design Document translates the Requirement Specifications into a
document from which the developers can create the actual system. It identifies the top-level
system architecture, and identifies hardware, software, communication, and interface
components.
1.1 Goals and objectives
Overall goals and proposed system objectives are described.
1.2 Statement of scope
A description of the proposed system software is presented. Major inputs, processing
functionality and outputs are described without regards to implementation detail.
Rank the major processing functionality from the developer’s point of view. Use a simple
ranking system such as: essential, desirable and future requirements. This should represent what
you think you can accomplish in the time frame of a semester. The essential requirements, you
are sure you can complete.
©Juliet 2021 Page 2
about:blank 2/7
