Content deleted Content added
m Reverted edits by 2409:40C1:1031:F9B8:8000:0:0:0 (talk) (HG) (3.4.13) |
|||
(16 intermediate revisions by 14 users not shown) | |||
Line 1:
{{Redirect|SADT|another use|Self accelerating decomposition temperature}}
[[File:SADT.svg|thumb|240px|right|SADT basis element.]]
'''Structured
==Overview==
Structured
==History==
SADT
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
SADT was among a series of similar structured methods, which had emerged since the 1960 such as:
* [[Structured programming]] in circa 1967 with [[Edsger W. Dijkstra]].
* [[Structured
* [[Structured
* [[Information
In 1981 the [[IDEF0]] formalism was published, based on SADT.<ref>Gavriel Salvendy (2001). ''Handbook of Industrial Engineering: Technology and Operations Management.''. p.508.</ref>
==SADT topics==
[[File:6 Decomposition Structure.svg|thumb|240px|right|Top down decomposition structure.]] [[File:Sadt.png|thumb|240px|right|An SADT example.]]
===Top
The structured analysis and design technique uses a decomposition with the [[Top-down and bottom-up design|top-down approach]]. This decomposition is conducted only in the physical ___domain from an axiomatic design viewpoint.<ref>Nam Pyo Suh (2007). [http://www.axiomaticdesign.com/technology/ADSChapter5.html ''Axiomatic Design - Advances and Applications'']. New York : Oxford University Press Chapter 5, pp. 239-298.</ref>
===Diagrams===
SADT uses two types of diagrams: [[activity model]]s and [[data model]]s. It uses arrows to build these diagrams.
The
* A main box where the name
* On the left-hand side of this box, incoming arrows: inputs of the action.
* On the upper part, the incoming arrows: data necessary for the action.
Line 63:
==See also==
* [[IDEF0]]
* [[Jackson
* [[Structure chart]]
* [[Structured
* [[Systems analysis]]
==References==
{{Reflist
==Further reading==
* William S. Davis (1992). ''Tools and Techniques for Structured Systems Analysis and Design''. Addison-Wesley. {{ISBN
* Marca, D.A., and C.L. McGowan. (1988). ''SADT: structured analysis and design technique''. McGraw-Hill Book Co., Inc.: New York, NY.
* Jerry FitzGerald and Ardra F. FitzGerald (1987). ''Fundamentals of Systems Analysis: Using Structured Analysis and Design Techniques''. Wiley. {{ISBN
* David A. Marca and Clement L. McGowan (1988). ''SADT: Structured Analysis and Design Technique''. McGraw-Hill. {{ISBN
* D. Millington (1981). ''Systems Analysis and Design for Computer Applications''. E. Horwood. {{ISBN
* Robertson & Robertson (1999). ''Mastering the Requirements Process''. Addison Wesley.
* James C. Wetherbe (1984). ''Systems Analysis and Design: Traditional, Structured, and Advanced Concepts and Techniques''. West Pub. Co. {{ISBN
==External links==
Line 84:
*[http://www.idef.com/idef0.htm The IDEF0 method]
*[http://www.cs.toronto.edu/~jm/2507S/Notes04/SADT.pdf A course about SADT diagrams]
▲{{Use dmy dates|date=January 2012}}
{{Authority control}}
[[Category:Systems analysis]]
|