Scribd
Upload
5 views

SDD_updated_explanation

The Software Design Description (SDD) outlines the structure and design of a software system, including sections on system overview, architecture, data design, component design, user interface design, and a requirements matrix. It provides guidelines for preparing each section, emphasizing the importance of architectural styles, data descriptions, and user interface functionalities. Additionally, it includes hints for enhancing the content based on the Software Requirements Specification (SRS).

Uploaded by

gboxanas54
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
5 views

SDD_updated_explanation

The Software Design Description (SDD) outlines the structure and design of a software system, including sections on system overview, architecture, data design, component design, user interface design, and a requirements matrix. It provides guidelines for preparing each section, emphasizing the importance of architectural styles, data descriptions, and user interface functionalities. Additionally, it includes hints for enhancing the content based on the Software Requirements Specification (SRS).

Uploaded by

gboxanas54
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Software Design Description

TABLE OF CONTENT

1. INTRODUCTION
1.1 Purpose
1.2 Scope
1.3 Overview
1.4 Reference Material
1.5 Definitions and Acronyms

2. SYSTEM OVERVIEW

3. SYSTEM ARCHITECTURE
3.1 Architectural Design
3.2 Decomposition Description
3.3 Design Rationale

4. DATA DESIGN
4.1 Data Description
4.2 Data Dictionary

5. COMPONENT DESIGN
5.1 Sequence Diagram
5.2 Class Diagram
5.3 State Diagram

6. USER INTERFACE DESIGN


6.1 Overview of User Interface
6.2 Screen Images

7. REQUIREMENTS MATRIX

8. APPENDICES
HINTS ON PREPARING SDD
1. SECTION 1 & 2
• Copy from your SRS, and improve the contents and subsection descriptions if required

2. SECTION 3 : SYSTEM ARCHITECTURE


• 3.1 Architectural Design
Specify your chosen architectural style in designing the architectural
decomposition. (i.e. layered – 4 tiers)
Provide the architectural model (the visualization diagram) based on the chosen
style. (Weather Station/ LibSYS example in textbook)

• 3.2 Decomposition Description


Describe and elaborate further on the architectural decomposition in subsection
3.1
You may describe in term of the 6 questions in architectural design decisions
consideration
1. What approach will be used to structure the system?
2. What architectural styles are appropriate?
3. What control strategy should be used?
4. How will the structural components be decomposed into subcomponents?
5. Is there a generic application architecture that can be used?
6. What architectural organization is best for delivering the non functional
requirements?

• 3.3 Design Rationale


Justify and elaborate on the reasons for the architectural decomposition in
subsection 3.1, why, benefits, trade‐offs

3. SECTION 4 : DATA DESIGN


• 4.1 Data Description
Describe and elaborate your database entities or data storage designs
• 4.2 Data Dictionary
All related entities/records and its attribute/specifications

4. SECTION 5 : COMPONENT DESIGN


• 5.1 Sequence diagram
Copy from your SRS, improve the diagrams by having correct flow of events upon
sequence, messages to be passed from 1 object to another objects.
• 5.2 Class diagram
Create a class diagram for overall proposed system. (It is good if you can separate a
group of classes according to the layered that you designed in subsection 3.1)
Provide the relationships & multiplicities between classes, attributes & operations
for the class (which can be extracted from the sequence diagram messages)
• 5.3 State Diagram
Choose only ONE class, provide its state diagram to represent its behavior in the
system

5. SECTION 6 USER INTERFACE DESIGN


• 6.1 Overview of User Interface
Introduce all the functionalities provided by the proposed system. i.e. function login
(from elicited use cases)
• 6.2 Screen Images
Provide the user interface/ screen images for each functions of the system
You may design using simple rectangle‐box diagram or provide the interface of real
forms (extra marks to make me impress ☺)

6. REQUIREMENT MATRIX
• Create the requirement‐matrix table & traceability diagram (from EA)
• Refer to Week 11 slides OOD & SDD

7. APPENDICES
• Support documents if you have not included in previous SRS

You might also like