Software Design Description (SDD Report) Template
Software Design Description (SDD Report) Template
Software Design Description (SDD Report) Template
On
<Project Title>
Date: ..............
has been examined by us and is hereby approved for the award of degree
“Bachelor of Technology in Information Technology Discipline”, for which it
has been submitted. It is understood that by this approval the undersigned do not
necessarily endorse or approve any statement made, opinion expressed or
conclusion drawn therein, but approve the report only for the purpose for which it
has been submitted.
Date: Date:
2. SYSTEM OVERVIEW
3. SYSTEM ARCHITECTURE
3.1 Architectural Design
3.2 Decomposition Description
4. DATA DESIGN
4.1 Data Description
4.2 Data Dictionary
1.1 Purpose
1.2 Scope
Provide a description and scope of the software and explain the goals, objectives and benefits
of your project. This will provide the basis for the brief description of your product.
1.3 Overview
Provide definitions of all terms, acronyms, and abbreviations that might exist to properly
Interpret the SDD. These definitions should be items used in the SDD that are most likely not
known to the audience.
2. SYSTEM OVERVIEW
Give a general description of the functionality, context and design of your project. Provide any b
ackground information if necessary.
3. SYSTEM ARCHITECTURE
Develop a modular program structure and explain the relationships between the modules to achie
ve the complete functionality of the system. This is a high level overview of how
responsibilities of the system were partitioned and then assigned to subsystems. Identify each hig
h level subsystem and the roles or responsibilities assigned to it.
Describe how these subsystems collaborate with each other in order to achieve the desired functi
onality. Don’t go into too much detail about the individual subsystems. The main purpose is to g
ain a general understanding of how and why the system was decomposed,
and how the individual parts work together. Provide a diagram showing the major subsystems an
d data repositories and their interconnections. Describe the diagram if required.
3.2 Decomposition Description
Provide a decomposition of the subsystems in the architectural design. Supplement with text as
needed. You may choose to give a functional description or an object-oriented description. For
a functional description, put top-level data flow diagram (DFD) and
structural decomposition diagrams. For an OO description, put subsystem model, object
diagrams, generalization hierarchy diagram(s) (if any), aggregation hierarchy diagram(s)
(if any), interface specifications, and sequence diagrams here.
4. DATA DESIGN
Explain how the information domain of your system is transformed into data structures. Describe
how the major data or system entities are stored, processed and organized. List any databases or
data storage items.
Alphabetically list the system entities or major data along with their types and descriptions.
Describe the functionality of the system from the user’s perspective. Explain how the user will
be able to use your system to complete all the expected features and the
feedback information that will be displayed for the user.
6.2 Screen Images
Display screenshots showing the interface from the user’s perspective. These can be hand-
drawn or you can use an automated drawing tool. Just make them as accurate as possible.
(Graph paper works well.)