Structured analysis and design technique: Difference between revisions

Revision as of 22:50, 20 January 2015

Revision as of 14:04, 24 November 2015

Line 2:

[[File:SADT.svg|thumb|240px|right|SADT basis element.]]

'''Structured Analysis and Design Technique''' ('''SADT''') is a [[systems engineering]] and [[software engineering methodology]] for describing [[system]]s as a hierarchy of functions. SADT is a [[structured analysis]] modelling language, which uses two types of diagrams: [[activity model]]s and [[data model]]s. It is developed since the late 1960s by [[Douglas T. Ross]], and further formalized and published as [[IDEF0]] in 1981.

==Overview==

Line 10:

SADT has been developed and field-tested during the period of 1969 to 1973 by [[Douglas T. Ross]] and [[SofTech, Inc.]].<ref name="sadt"/><ref name="ross1977">D. T. Ross: Structured Analysis (SA): A Language for Communicating Ideas. IEEE Transactions on Software Engineering, SE-3(1), pp. 16-34. [http://ieeexplore.ieee.org/xpls/abs_all.jsp?isnumber=35896&arnumber=1702399&count=9&index=1 Abstract]</ref> The methodology was used in the MIT [[APT (programming language)|Automatic Programming Tool]] (APT) project. It received extensive use starting in 1973 by the US Air Force [[Integrated Computer Aided Manufacturing]] program.

According to Levitt (2000) SADT is "part of a series of structured methods, that represent a collection of analysis, design, and programming techniques that were developed in response to the problems facing the software world from the 1960s to the 1980s. In this timeframe most commercial programming was done in [[COBOL]] and [[Fortran]], then [[C (programming language)|C]] and [[BASIC]]. There was little guidance on “good” design and programming techniques, and there were no standard techniques for documenting requirements and designs. Systems were getting larger and more complex, and the information system development became harder and harder to do so. As a way to help manage large and complex software.<ref name="DL00" >Dave Levitt (2000):[http://faculty.inverhills.edu/dlevitt/CS%202000%20(FP)/Introduction%20to%20Structured%20Analysis%20and%20Design.pdf Introduction to Structured Analysis and Design]. Retrieved 21 September 2008.</ref>

SADT was among a series of similar structured methods, which had emerged since the 1960 such as:

Line 47:

=== Roles ===

According theto Mylopoulos (2004) in the software development process multiple roles can or should be distinguished:<ref name ="JM04"/>

* Author or developer of the SADT models

* Commenters, who review the author's work

Line 59:

== Usage ==

SADT is used as diagrammatic notation in conceptual design of software engineering and systems engineering to sketch applications,<ref name ="JM04"/> for more detailed structured analysis, for requirements definition,<ref>Ross, Douglas T., and Kenneth E. Schoman Jr. "Structured analysis for requirements definition." Software Engineering, IEEE Transactions on 1 (1977): 6-15.</ref> and structured design.

==See also==