In software engineering, structured analysis and structured design are methods for analyzing business requirements and developing specifications for converting practices into computer programs, hardware configurations, and related manual procedures.
| FactSnippet No. 687,301 |
Structured analysis became popular in the 1980s and is still in use today.
| FactSnippet No. 687,302 |
Structured analysis 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.
| FactSnippet No. 687,303 |
Structured analysis typically creates a hierarchy employing a single abstraction mechanism.
| FactSnippet No. 687,304 |
One reason for the popularity of structured analysis is its intuitive ability to communicate high-level processes and concepts, whether in single system or enterprise levels.
| FactSnippet No. 687,305 |
Structured analysis takes advantage of information hiding through successive decomposition analysis.
| FactSnippet No. 687,306 |
The result of structured analysis is a set of related graphical diagrams, process descriptions, and data definitions.
| FactSnippet No. 687,307 |
Structure charts are used in structured analysis to specify the high-level design, or architecture, of a computer program.
| FactSnippet No. 687,308 |
Structured analysis design is concerned with the development of modules and the synthesis of these modules in a so-called "module hierarchy".
| FactSnippet No. 687,309 |
Structured analysis design was developed by Larry Constantine in the late 1960s, then refined and published with collaborators in the 1970s; see Larry Constantine: structured design for details.
| FactSnippet No. 687,310 |