Version: <1.0>
Software Design Description Template / Date: <dd/mm/yy>

Software Design Description

Template

Version 1.0 ● 30 SEPT. 2006


Using This Template

To create a document from this template:

  1. Delete the template title page (previous page) and this page.
  2. Replace [bracketed text] on the cover page (next page) with your project information.
  3. Replace [bracketed text] in the document header area at the top of page i (Contents page) with the same project information as on the cover page.

Note: Please do not remove or modify content in the footer area.

  1. Complete the entire template. Each section contains abbreviated instructions and a content area. The content area is marked with a placeholder symbol (Þ) or with a table. Relevant text from other project documents may be pasted into content areas.
  2. Update the table of contents by right-clicking and selecting “Update Field,” then “Update Page Numbers Only.”


SOFTWARE ENGINEERING COURSE PROJECT

Software Design Description Document

[PROJECT NAME]

Team Members

Document Change Control

Identify changes to the Software Design Description.

Version Number / Version Date / Description of Changes / Location of Changes
1.0 / 2 Dec. 2006 / Initial version / -

Section 1. System decomposition

Provide and describe a figure that depicts the overall system decomposition.

Þ

Subsystem ID / Subsystem Name / Description /

Section 2. Class diagrams

Add in your design class diagrams

Þ

List down your classes and describe them

Class ID / Class Name / Subsystem ID / Description /

Section 3. Sequence diagrams

Add in your design sequence diagrams

Þ

Section 4. Entity-Relationship Diagram

Add in your ERD

Þ

Section 5. User interface design

5.1 Prototype screenshots

Add screenshots for your user interface prototypes, along with any necessary descriptions. Add an ID to every

Þ

5.2 Navigation hierarchy

Provide and describe a diagram of the navigation hierarchy that illustrates how a user moves through the user interface.

Þ

5.3 User interface traceability

Fill in the table to map between requirements (or use cases) and user interface screenshots

Þ

Use case ID / Screenshot ID / Comment /

Section 6. Requirements Traceability Matrix

Requirement ID / Requirement Statement / Use case ID / Subsystem ID / Design Classes / ERD Tables /
Course project / User, 2006 / Page 4