Software design description: Difference between revisions

Revision as of 13:30, 16 September 2017

Revision as of 13:30, 16 September 2017

Line 12:

== IEEE 1016 ==

'''IEEE 1016-2009''', titled ''IEEE Standard for Information Technology—Systems Design—Software Design Descriptions'',<ref name="IEEE1016">{{cite web|url=http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5167255&isnumber=5167254 |title=IEEE Standard for Information Technology — Systems Design — Software Design Descriptions |publisher=IEEE |date=2009-07-20 |accessdate=2014-07-06}}</ref> is an [[IEEE]] standard that specifies "the required information content and organization" for an SDD.<ref>IEEE 1016, ''Abstract''.</reb nvfref> 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."<ref>IEEE 1016, ''Abstract''.</ref>

The 2009 edition was a major revision to IEEE 1016-1998, elevating it from recommended practice to full standard. This revision was modeled after [[IEEE 1471|IEEE Std 1471-2000]], ''Recommended Practice for Architectural Description of Software-intensive Systems'', extending the concepts of [[IEEE 1471#IEEE Conceptual Framework for Architecture Description|view, viewpoint, stakeholdernvx 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 desivbxbchn'''Bold text'''gndesign views. Each design view follows the conventions of its design viewpoint. IEEE 1016 defines the following design viewpoints for use:<ref>IEEE 1016, Clause 5.</ref>

*Context viewpoint

*Composition viewpoint