Structured analysis: Difference between revisions

Revision as of 03:42, 1 July 2017

Revision as of 20:40, 7 July 2017

Line 45:

=== Approach ===

Structured Analysis views a system from the perspective of the data flowing through it. The function of the system is described by processes that transform the data flows. Structured analysis takes advantage of information hiding through successive decomposition (or top down) analysis. This allows attention to be focused on pertinent details and avoids confusion from looking at irrelevant details. As the level of detail increases, the breadth of information is reduced. The result of structured analysis is a set of related graphical diagrams, process descriptions, and data definitions. They describe the transformations that need to take place and the data required to meet a system's [[functional requirement]]s.<ref name="HeSi86">

Alan Hecht and Andy Simmons (1986) [httphttps://ntrs.nasa.gov/archive/nasa/casi.ntrs.nasa.gov/19890006956_1989006956.pdf Integrating Automated Structured Analysis and Design with Ada Programming Support Environments] NASA 1986.</ref>

[[Image:Analysis Model Objects.jpg|thumb|320px|The structured analyse approach develops perspectives on both process objects and data objects.<ref name="HeSi86"/>]]

De Marco's approach<ref>[[Tom DeMarco]] (1978). ''Structured Analysis and System Specification''. Yourdon Press, New York, 1978.</ref> consists of the following objects (see figure):<ref name="HeSi86"/>