Software Design and Development
Wentworth Institute Of Technology
Department of Computer Science Software Design and Development COMP 566
Spring 2012
Software Design
Prof. Suresh.
This document is largely borrowed from a similar document used at the University of Texas at Austin in teaching the software-engineering course and the adapted version from one of my Professors from Saint Joseph’s University (now at Standford).
I am citing one other document here from the scholars.google.com search where I was looking to see some more detail to the architectural design. This template was the closest to ours and also gives you guys the freedom to use more than one template.
You can feel free to make a hybrid document too. The major differences I see are that the “ Architectural Strategies” section that is not included in this template and hence making it different. I like the details described and I strongly urge you to read through both of these documents before you start writing your SDS. http://www.cmcrossroads.com/bradapp/docs/sdd.html Remember that the design specification has as its primary audience the developers/coders who will implement the design and the testers who will need to verify that the software does do what it is supposed to do, and does not contain errors. The SDS has several goals: to facilitate full understanding of the problem being solved, to decompose the problem into appropriate parts, and to provide a high-quality basis for the implementation phase.
The following content suggests a reasonable organization for the Software Design Specification. 1. Introduction 1. Purpose of this Document
This section should contain a full description of the main objectives of the SDS document. 2. Scope of the Development Project
This will be similar to what was written in the SRS. 3. Definitions, Acronyms, and Abbreviations
Please alphabetize! This should be the same as what is in the SRS with any necessary additions. 4.
Department of Computer Science Software Design and Development COMP 566
Spring 2012
Software Design
Prof. Suresh.
This document is largely borrowed from a similar document used at the University of Texas at Austin in teaching the software-engineering course and the adapted version from one of my Professors from Saint Joseph’s University (now at Standford).
I am citing one other document here from the scholars.google.com search where I was looking to see some more detail to the architectural design. This template was the closest to ours and also gives you guys the freedom to use more than one template.
You can feel free to make a hybrid document too. The major differences I see are that the “ Architectural Strategies” section that is not included in this template and hence making it different. I like the details described and I strongly urge you to read through both of these documents before you start writing your SDS. http://www.cmcrossroads.com/bradapp/docs/sdd.html Remember that the design specification has as its primary audience the developers/coders who will implement the design and the testers who will need to verify that the software does do what it is supposed to do, and does not contain errors. The SDS has several goals: to facilitate full understanding of the problem being solved, to decompose the problem into appropriate parts, and to provide a high-quality basis for the implementation phase.
The following content suggests a reasonable organization for the Software Design Specification. 1. Introduction 1. Purpose of this Document
This section should contain a full description of the main objectives of the SDS document. 2. Scope of the Development Project
This will be similar to what was written in the SRS. 3. Definitions, Acronyms, and Abbreviations
Please alphabetize! This should be the same as what is in the SRS with any necessary additions. 4.