Content deleted Content added
Citation bot (talk | contribs) Alter: url, template type. URLs might have been internationalized/anonymized. Add: isbn. Upgrade ISBN10 to ISBN13. | You can use this bot yourself. Report bugs here. | Suggested by AManWithNoPlan | All pages linked from cached copy of User:AManWithNoPlan/sandbox2 | via #UCB_webform_linked 3/111 |
Citation bot (talk | contribs) Alter: url, template type. URLs might have been anonymized. Add: isbn, title, doi, pages, date, journal. | Use this bot. Report bugs. | Suggested by Abductive | #UCB_toolbar |
||
Line 4:
{{Short description|written design description of a software product}}
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|journal=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 36:
== IEEE Status ==
IEEE 1016-2009 is currently listed as 'Inactive - Reserved'.<ref>{{cite
== See also ==
| |||