Structured analysis: Difference between revisions

Revision as of 12:42, 18 January 2017

Revision as of 12:50, 18 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 '''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.

Line 15 ⟶ 14:

== History ==

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. In this timeframe most commercial programming was done in [[Cobol]] and [[Fortran]], then [[C (programming language)|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."<ref name="DL00">Dave Levitt (2000):[http://faculty.inverhills.edu/dlevitt/CS%202000%20(FP)/Introduction%20to%20Structured%20Analysis%20and%20Design.pdf "Introduction to Structured Analysis and Design]." at ''faculty.inverhills.edu/dlevitt''. Retrieved 21 Sep 2008. No longer online 2017.</ref>

As a way to help manage large and complex software, the following structured methods emerged since the end of the 1960s :<ref name="DL00"/>