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. 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.
14-442: SDD may refer to: Computing [ edit ] Software Design Description (IEEE 1016–2009), a standard that specifies the form of the document used to specify system architecture and application design in a software-related project Software Design Document , a written outline of the development of a course or a description of a software product Solution Deployment Descriptor ,
28-829: A payment system in the Single Euro Payments Area in Europe SDD, ISO code for the Sudanese dinar , the currency of Sudan 1992–2007, now replaced by the Sudanese pound Science [ edit ] Sulfadimidine , an antibiotic whose abbreviations include SDD Shared delusional disorder , a psychiatric syndrome Silicon drift detector , a p-n junction-based detector for ionizing radiation, such as for X-rays Seasonal deficit disorder , another name for seasonal affective disorder Symmetric diagonally dominant matrix systems in mathematics Selective decontamination of
42-510: A proposed OASIS standard for software deployment, configuration and maintenance Software Design and Development , an HSC subject in NSW that details the basics of designing and developing software applications Syntax-Directed Definition - a context-free grammar with attributes and rules Sentential Decision Diagram , a formalism in knowledge compilation and artificial intelligence Finances [ edit ] SDD, for SEPA Direct Debit ,
56-599: A special "fast-track procedure", in parallel with its approval by national bodies of ISO and IEC. A coordinated revision of this standard by ISO/IEC JTC1/SC7/WG42 and IEEE CS commenced in 2006, following the successful ISO/IEC fast-track ballot and in line with the IEEE standard 5-year review of the standard. In November 2011, IEEE 1471-2000 and ISO/IEC 42010:2007 was superseded by ISO/IEC/IEEE 42010:2011 , Systems and software engineering — Architecture description . According to IEEE 1471 an architecture description can be used for
70-425: Is an IEEE standard that specifies "the required information content and organization" for an SDD. IEEE 1016 does not specify the medium of an SDD; it is "applicable to automated databases and design description languages but can be used for paper documents and other means of descriptions." The 2009 edition was a major revision to IEEE 1016-1998, elevating it from recommended practice to full standard. This revision
84-514: Is different from Wikidata All article disambiguation pages All disambiguation pages Software Design Description The SDD usually contains the following information: These design mediums enable the designer to represent procedural detail, that facilitates translation to code. This blueprint for implementation forms the basis for all subsequent software engineering work. IEEE 1016-2009 , titled IEEE Standard for Information Technology—Systems Design—Software Design Descriptions ,
98-609: The IEEE Software Engineering Standards Committee (SESC) chartered an IEEE Architecture Planning Group (APG) to set direction for incorporating architectural thinking into IEEE standards. In April 1996, the Architecture Working Group (AWG) was created to implement the recommendations made by APG to the SESC. The AWG was chaired by Basil Sherlund, vice-chairs Ronald Wade, David Emery, the specification
112-448: The conventions of its design viewpoint. IEEE 1016 defines the following design viewpoints for use: In addition, users of the standard are not limited to these viewpoints but may define their own. IEEE 1016-2009 is currently listed as 'Inactive - Reserved'. IEEE 1471 IEEE 1471 is a superseded IEEE standard for describing the architecture of a "software-intensive system", also known as software architecture . In 2011 it
126-460: The digestive tract in medicine Topics referred to by the same term [REDACTED] This disambiguation page lists articles associated with the title SDD . If an internal link led you here, you may wish to change the link to point directly to the intended article. Retrieved from " https://en.wikipedia.org/w/index.php?title=SDD&oldid=1223970997 " Category : Disambiguation pages Hidden categories: Short description
140-478: The first to be compromised under the pressures of development. IEEE 1471 was created to provide a basis for thinking about the architecture of software-intensive systems. IEEE 1471's contributions can be summarised as follows (in this list, items in italics are terms defined by and used in the standard): IEEE 1471 provides informative annexes that relate its concepts to architecture concepts in other standards, including RM-ODP and IEEE 12207 . In August 1995,
154-444: Was adopted by ISO/IEC JTC1/SC7 as ISO/IEC 42010:2007 , Systems and Software Engineering -- Recommended practice for architectural description of software-intensive systems . It has long been recognized that "architecture" has a strong influence over the life cycle of a system. However, until relatively recently, hardware issues have tended to dominate architectural thinking, and software aspects, when considered at all, were often
SECTION 10
#1732845112208168-487: Was edited by Rich Hilliard. The AWG had 25 members. Drafts of the specification were balloted and commented on by 130 international reviewers. In September 2000, the IEEE-SA Standards Board approved the specification as IEEE Std 1471-2000. In 2006, ISO/IEC Joint Technical Committee 1 (JTC1), Information technology/Subcommittee SC 7, Software and systems engineering, adopted the specification as ISO/IEC 42010, under
182-460: Was modeled after IEEE Std 1471-2000 , Recommended Practice for Architectural Description of Software-intensive Systems , extending the concepts of view, viewpoint, stakeholder, and concern from architecture description to support documentation of high-level and detailed design and construction of software. [IEEE 1016, Introduction ] Following the IEEE 1016 conceptual model, an SDD is organized into one or more design views. Each design view follows
196-491: Was superseded by ISO/IEC/IEEE 42010 , Systems and software engineering — Architecture description . IEEE 1471 is the short name for a standard formally known as ANSI/IEEE 1471-2000, Recommended Practice for Architecture Description of Software-Intensive Systems. Within Institute of Electrical and Electronics Engineers (IEEE) parlance, this is a "recommended practice", the least normative of its standards. In 2007 this standard
#207792