0% found this document useful (0 votes)
98 views

Example of SDS

This document is a software design specification for project <Project>. It includes an introduction describing the purpose, scope, definitions, and references. Section 2 describes the application architecture and decomposition. Section 3 covers the data design, including conceptual, logical, and physical data models and a data dictionary. Section 4 provides details on inputting teaching information, including interface design and data requirements. Section 5 maps the system components to functional requirements. Appendices may contain additional explanatory information.

Uploaded by

Lâm Trường
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
98 views

Example of SDS

This document is a software design specification for project <Project>. It includes an introduction describing the purpose, scope, definitions, and references. Section 2 describes the application architecture and decomposition. Section 3 covers the data design, including conceptual, logical, and physical data models and a data dictionary. Section 4 provides details on inputting teaching information, including interface design and data requirements. Section 5 maps the system components to functional requirements. Appendices may contain additional explanatory information.

Uploaded by

Lâm Trường
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Software Design Specification for <Project> Page i

Software Design
for

<Project>
Version <X.X>

Prepared by

Group: <group name>


<student code> <full name> Team leader

<student code> <full name> Vice of team leader

<student code> < full name> Member

<student code> < full name> Member

Instructor: <full name>


Course: Introduction to Software Engineering
Software Design Specification for <Project> Page ii

Table of Contents
1. Introduction.........................................................................................................................1
1.1 Purpose..................................................................................................................................1
1.2 Product Scope........................................................................................................................1
1.3 Definitions, Acronyms and Abbreviations.............................................................................1
1.4 References.............................................................................................................................1
2. Architectural Design.............................................................Error! Bookmark not defined.
2.1 Architectural Design.............................................................Error! Bookmark not defined.
2.2 Decomposition Description...................................................................................................1
2.3 Design Basis.........................................................................Error! Bookmark not defined.
3. Data Design..........................................................................................................................2
3.1 Conceptual Data Model.........................................................................................................2
3.2 Logical Data Model...............................................................................................................2
3.3 Physical Data Model.............................................................................................................2
3.4 Data Dictionary.....................................................................................................................2
4. Detailed Design....................................................................................................................2
4.1 Input the teaching information...............................................................................................2
4.2 Function YY (YY: specific name).........................................................................................3
5. References to Requirements...............................................................................................3
6. Appendices...........................................................................................................................4
Software Design Specification for <Project> Page iii

Revision History
Name Date Reason For Changes Version
Software Design Specification for Page

1. Introduction
1.1 Purpose

1.2 Product Scope

1.3 Definitions, Acronyms and Abbreviations

No. Term / Acronyms Definition / Explanation

1.4 References

2. Application Architecture
2.1 Application Architecture

2.2 Description

< Describe the application architecture. We can provide further explanations if


necessary.>
Software Design Specification for Page

3. Data Design
3.1 Data Description
3.1.1 Conceptual Data Model

3.1.2 Logical Data Model

3.1.3 Physical Data Model

3.2 Data Dictionary

4. Detailed Design
4.1 Input the teaching information

- Purpose:
- Interface:

Teaching Information1

Semester: II 2 Academic Year: 2020-2021 3

Lecturer: 4 Course: 5
001235 Nguyen Van A CT101 Lap trinh C
001236 Nguyen Thi B CT103 Cau truc du lieu
… … … …

Ok 6 Cancel 7
Software Design Specification for Page

- The components of interface:

No. Controller type Default value Note


1 Form
Set: current semester.
2 Combobox Current semester Values of “Semester” is
I, II, III.
Set: current academic
year. Values of
Current academic
3 Combobox “Academic year - ay” is
year
2 ay before and after the
current ay.
Display LID, LName in
4 Combobox table “Lecturer”; select
LID
Display CID, CName in
5 Combobox table “Course”; select
CID
6 Button
Refresh all comboboxes
7 Button
to the default values.

- Data to be used: list the tables in a database or the data structures needed by
this function.

Table name / Data Method


No.
structure Add Modify Delete Query
1 Teach x
2 Lecturer x
3 Course x

- Process: describe the algorithm for each event via diagrams (flowchart). >

4.2 Function YY (YY: specific name)

< There are items similar to the function XX>

5. References to Requirements
<Use a table to map the components of the system to the functional requirements in
SRS. Refer to the functional requirements by the number we have assigned to them in
SRS.>
Software Design Specification for Page

6. Appendices
<Optional.
The appendices provide the additional detailed information to assist in understanding
software design documentation.>

You might also like