Content deleted Content added
Wikification + start expanding article |
|||
Line 1:
:''For the chemical reaction SADT, see [[Self Accelerating Decomposition Temperature]]''
[[Image:SADT.svg|thumb|240px|right|SADT basis element.]]
'''Structured Analysis and Design Technique'''
==
Structured Analysis and Design Technique (SADT) is a [[diagram]]matic notation for constructing a sketch for an software application. It offers building blocks to represent entities and activities, and a variety of arrows to relate boxes. These boxes and arrows have an associated informal [[semantics]].<ref name ="JM04"> John Mylopoulos (2004). [http://www.cs.toronto.edu/~jm/2507S/Notes04/SADT.pdf Conceptual Modelling III. Structured Analysis and Design Technique (SADT)]. Retrieved 21 Sep 2008.</ref> SADT can be used as a functional analysis tool of a given process, using successive levels of details. The SADT method allows to define user needs for IT developments, which is very used in the industrial Information Systems, but also to explain and to present an activity’s manufacturing processes, procedures.<ref name="FL">[http://www.free-logistics.com/index.php/Download-document/22-SADT_eng.html SADT] at Free-logisitcs.com. Retrieved 21 Sep 2008.</ref>
SADT uses two types of diagrams: [[activity model]]s and [[data model]]s.▼
The SADT supplies a specific functional view of any enterprise by describing the functions and their relationships in a company. These functions fulfill the objectives of a company, such as sales, order planning, product design, part manufacturing, and human resource management. The SADT can depict simple functional relationships here and can reflect data and control flow relationships between different functions. The [[IDEF0]] formalism is based on SADT, developed by [[Douglas T. Ross]] in 1985.<ref>Gavriel Salvendy (2001). ''Handbook of Industrial Engineering: Technology and Operations Management.''. p.508.</ref>
== History ==
SADT has been in use since the mid-seventies, and has inspired many other commercial tools. <ref name ="JM04"/> It 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]] and [[BASIC]]. There was little guidance on “good” design and programming techniques, and there were no standard techniques for documenting requirements and designs. Systems where 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. Since the end 1960 multiple Structured Methods emerged<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 Sep 2008.</ref>
* [[Structured programming]] in circa 1967 with [[Edgar Dykstra]].
* Structured Design around 1975 with [[Larry Constantine]] and [[Ed Yourdon]]
* Structured Analysis in circa 1978 with [[Tom DeMarco]], Yourdon, Gane & Sarson, McMenamin & Palmer.
* [[Information Engineering]] in circa 1990 with [[James Martin]].
== Techniques ==
[[Image:Sadt.png|thumb|240px|right|An SADT example.]]
▲SADT uses two types of diagrams: [[activity model]]s and [[data model]]s. It uses arrows to build these diagrams.
The SADT’s representation is the following:
* A main box where is specified the name of the process or the action
* 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.
* On the bottom of the box, incoming arrows: means used for the action.
* On the right-hand side of the box, outgoing arrows: outputs of the action.
* Inputs enter from the left and represent data or consumables that are needed by the activity.
* Outputs exit from the right and represent data or products that are produced by the activity.
Line 17 ⟶ 32:
* Mechanisms identify the means, components or tools used to accomplish the activity. Represents allocation of activities.
The semantics of arrows for data:<ref name ="JM04"/>
* Inputs are activities that produce the data.
* Outputs consume the data.
* Controls influence the internal state of the data.
== References ==
{{reflist}}
== Further reading ==
* William S. Davis (1992). ''Tools and Techniques for Structured Systems Analysis and Design''. Addison-Wesley. ISBN 0201102749
* 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 0471885975
* David A. Marca and Clement L. McGowan (1988). ''SADT: Structured Analysis and Design Technique''. McGraw-Hill. ISBN 0070402353
* D. Millington (1981). ''Systems Analysis and Design for Computer Applications''. E. Horwood. ISBN 0853122490
* 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 0314778586
== External links ==
{{Commonscat|SADT}}
*[http://www.idef.com/idef0.html The IDEF0 method]
| |||