Revision as of 04:47, 13 September 2020 edit Citation bot (talk \| contribs) Bots 5,872,784 edits Alter: url. Add: author pars. 1-1. Removed parameters. Some additions/deletions were actually parameter name changes. \| You can use this bot yourself. Report bugs here. \| Suggested by AManWithNoPlan \| All pages linked from cached copy of User:AManWithNoPlan/sandbox2 \| via #UCB_webform_linked ← Previous edit		Revision as of 18:33, 27 September 2020 edit undo Ej48467 (talk \| contribs) 2 edits No edit summary Tags: Mobile edit Mobile web edit Next edit →
Line 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). "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"/>

Structured analysis: Difference between revisions