Structured analysis and design technique: Difference between revisions

Revision as of 19:17, 25 November 2008

Revision as of 18:52, 5 March 2009

Line 5:

== Overview ==

Structured Analysis and Design Technique (SADT) is a [[diagram]]matic notation for constructing a sketch for ana 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>

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>

Line 12:

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 [[EdgarEdsger DykstraW. Dijkstra]].

* [[Structured Design]] around 1975 with [[Larry Constantine]] and [[Ed Yourdon]]

* [[Structured Analysis]] in circa 1978 with [[Tom DeMarco]], Yourdon, Gane & Sarson, McMenamin & Palmer.