Structured analysis: Difference between revisions

Revision as of 14:17, 4 January 2017

Revision as of 20:46, 9 January 2017

Line 1:

{{copyedit|date=June 2016}}

[[Image:Context diagram and Technical Criteria Derivation.jpg|thumb|320px|Example of a structured analysis approach.<ref>Tricia Gilbert (2006) [http://acast.grc.nasa.gov/wp-content/uploads/icns/2006/06_Session_B1/03-Gilbert.pdf FCS Evaluation criterea for technology assessment]</ref>]]

In [[software engineering]], '''structured analysis''' (SA) and its allied technique, '''structured design''' (SD), are methods for analyzing business [[requirements]] and developing [[specification]]s for converting practices into [[computer program]]s, hardware configurations, and related manual procedures.

Structured analysis and design techniques are fundamental tools of [[systems analysis]]. They 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>