Structured analysis and design techniques are fundamental tools of [[systems analysis]], and developed from classical systems analysis of the 1960s and 1970s.<ref>[[Edward Yourdon]] (1986). ''Managing the Structured Techniques: Strategies for Software Development in the 1990s''. Yourdon Press. p.35.</ref>
== Objectives of Structuredstructured Analysisanalysis ==
Structured Analysisanalysis became popular in the 1980s and is still used by many. {{Citation needed|date=March 2016}} The analysis consists of interpreting the [[system]] concept (or real world situations) into data and control terminology represented by [[data flow diagram]]s. The flow of data and control from bubble to data store to bubble can be very hard to track and the number of bubbles can get to be extremely large. One approach is to first define events from the outside world that require the system to react, then assign a bubble to that event, bubbles that need to interact are then connected until the system is defined. Bubbles are usually grouped into higher level bubbles to decrease complexity. [[Data dictionary|Data dictionaries]] are needed to describe the data and command flows, and a process specification is needed to capture the transaction/transformation information.<ref name="FAA00">FAA (2000). [http://www.faa.gov/regulations_policies/handbooks_manuals/aviation/risk_management/ss_handbook/media/app_d_1200.pdf ''FAA System Safety Handbook, Appendix D'']. December 30, 2000.</ref>
SA and SD were accompanied by notation methods including [[structure chart]]s, [[data flow diagram]]s and [[data model diagram]]s, of which there were many variations, including those developed by [[Tom DeMarco]], [[Ken Orr]], [[Larry Constantine]], [[Vaughn Frick]], [[Ed Yourdon]], Steven Ward, [[Peter Chen]], and others.
