Structured analysis: Difference between revisions

Revision as of 12:50, 18 January 2017

Revision as of 10:00, 22 January 2017

Line 9:

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 are diplayeddisplayed with [[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.

These techniques were combined in various published [[Software development process|system development methodologies]], including [[structured systems analysis and design method]], profitable information by design (PRIDE), Nastec structured analysis & design, SDM/70 and the Spectrum structured system development methodology.