Software design description: Difference between revisions

Revision as of 05:48, 6 September 2023

Latest revision as of 10:51, 27 August 2025

(One intermediate revision by one other user not shown)

Line 3:

{{refimprove|date=September 2014}}

{{IEEE software documents}}

A '''software design description''' (a.k.a. '''software design document''' or '''SDD'''; just '''design document'''; also [[Software Design Specification]]) is a representation of a software design that is to be used for recording design information, addressing various design concerns, and communicating that information to the design’s stakeholders. <ref>{{Cite book|title=IEEE Standard for Information Technology--Systems Design--Software Design Descriptions|publisher=IEEE STD 1016-2009|date=July 2009|pages=1–35|url=https://ieeexplore.ieee.org/document/5167255|doi=10.1109/ieeestd.2009.5167255|isbn=978-0-7381-5925-6 }}</ref> An SDD usually accompanies an architecture diagram with pointers to detailed feature specifications of smaller pieces of the design. Practically, the description is required to coordinate a large team under a single vision, needs to be a stable reference, and outline all parts of the software and how they will work.

==Composition==

Line 34:

In addition, users of the standard are not limited to these viewpoints but may define their own.<ref>IEEE 1016, sub-clause 4.5.</ref>

== IEEE Statusstatus ==

IEEE 1016-2009 is currently listed as 'Inactive - Reserved'.<ref>{{cite book | url = https://ieeexplore.ieee.org/document/5167255| doi = 10.1109/IEEESTD.2009.5167255| title = IEEE Standard for Information Technology--Systems Design--Software Design Descriptions| publisher = IEEE STD 1016-2009| date = July 2009| pages = 1–35| isbn = 978-0-7381-5925-6}}</ref>

== See also ==