“Structured analysis and design technique”的意思、由来-开放百科全书

Structured analysis and design technique (SADT) is a systems engineering and software engineering methodology for describing systems as a hierarchy of functions. SADT is a structured analysis modelling language, which uses two types of diagrams: activity models and data models. It was developed in the late 1960s by Douglas T. Ross, and was formalized and published as IDEF0 in 1981.

Overview

Structured analysis and design technique (SADT) is a diagrammatic notation designed specifically to help people describe and understand systems.^[1] 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.^[2] SADT can be used as a functional analysis tool of a given process, using successive levels of details. The SADT method not only allows one to define user needs for IT developments, which is often used in the industrial Information Systems, but also to explain and present an activity’s manufacturing processes and procedures.^[3]

History

SADT has been developed and field-tested during the period of 1969 to 1973 by Douglas T. Ross and SofTech, Inc..^[1]^[4] The methodology was used in the MIT 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 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.^[5]

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

SADT topics

Top-down approach

The structured analysis and design technique uses a decomposition with the top-down approach. This decomposition is conducted only in the physical domain from an axiomatic design viewpoint.^[7]

Diagrams

SADT uses two types of diagrams: activity models and data models. It uses arrows to build these diagrams.

Roles

According to Mylopoulos (2004) in the software development process multiple roles can or should be distinguished:^[2]

Usage

SADT is used as diagrammatic notation in conceptual design of software engineering and systems engineering to sketch applications,^[2] for more detailed structured analysis, for requirements definition,^[8] and structured design.

See also

References

1. ^¹D. Marca, C. McGowan, Structured Analysis and Design Technique, McGraw-Hill, 1987, {{ISBN|0-07-040235-3}}
2. ^¹²³⁴John Mylopoulos (2004). Conceptual Modelling III. Structured Analysis and Design Technique (SADT). Retrieved 21 September 2008.
3. ^SADT at Free-logistics.com. Retrieved 21 September 2008.
4. ^D. T. Ross: Structured Analysis (SA): A Language for Communicating Ideas. IEEE Transactions on Software Engineering, SE-3(1), pp. 16-34. Abstract
5. ^Dave Levitt (2000):Introduction to Structured Analysis and Design {{Webarchive|url=https://web.archive.org/web/20060907132222/http://faculty.inverhills.edu/dlevitt/CS%202000%20%28FP%29/Introduction%20to%20Structured%20Analysis%20and%20Design.pdf |date=7 September 2006 }}. Retrieved 21 September 2008.
6. ^Gavriel Salvendy (2001). Handbook of Industrial Engineering: Technology and Operations Management.. p.508.
7. ^Nam Pyo Suh (2007). Axiomatic Design - Advances and Applications. New York : Oxford University Press Chapter 5, pp. 239-298.
8. ^Ross, Douglas T., and Kenneth E. Schoman Jr. "Structured analysis for requirements definition." Software Engineering, IEEE Transactions on 1 (1977): 6-15.