Essential systems analysis

Essential systems analysis was a new methodology for software specification published in 1984 by Stephen M. McMenamin and John F. Palmer for performing structured systems analysis based on the concept of event partitioning.[1] The essence of a system is "its required behavior independent of the technology used to implement the system".[2] It is an abstract model of what the system must do without describing how it will do it.[2]

The methodology[1] proposed that finding the true requirements for an information system entails the development of an essential model for the system, based on the concepts of a perfect internal technology, composed of:

* a perfect memory, that is infinitely fast and big, and
* a perfect processor, that is infinitely potent and fast.

Edward Yourdon later adapted it to develop modern structured analysis.[3]

The main result was a new and more systematic way to develop the data-flow diagrams, which are the most characteristic tool of structured analysis.

Essential analysis, as adopted in Yourdon's modern structured analysis, was the main software development methodology until object-oriented analysis became mainstream.

## References

1. ↑ 1.0 1.1 McMenamin, Stephen M.; Palmer, John F. (1984) (in en). Essential systems analysis. Yourdon Press. ISBN 978-0-917072-30-7. https://books.google.com/books?id=9WhRAAAAMAAJ.
2. ↑ 2.0 2.1 Yourdon, Edward (2006). Just enough structured analysis. Ed Yourdon.
3. ↑ Yourdon, Edward. (1989). Modern structured analysis. Englewood Cliffs, N.J.: Yourdon Press. ISBN 0-13-598624-9. OCLC 17877629. https://archive.org/details/modernstructured00your.

* v
* t
* e

Software engineering

Fields|

* Computer programming
* Requirements engineering
* Software deployment
* Software design
* Software maintenance
* Software testing
* Systems analysis
* Formal methods

Concepts|

* Data modeling
* Enterprise architecture
* Functional specification
* Modeling language
* Orthogonality
* Programming paradigm
* Software
* Software archaeology
* Software architecture
* Software configuration management
* Software development methodology
* Software development process
* Software quality
* Software quality assurance
* Software verification and validation
* Structured analysis

Orientations|

* Agile
* Aspect-oriented
* Object orientation
* Ontology
* Service orientation
* SDLC

Models|

| Developmental|

* Agile
* EUP
* Executable UML
* Incremental model
* Iterative model
* Prototype model
* RAD
* UP
* Scrum
* Spiral model
* V-Model
* Waterfall model
* XP

|

Other|

* SPICE
* CMMI
* Data model
* ER model
* Function model
* Information model
* Metamodeling
* Object model
* Systems model
* View model

Languages|

* IDEF
* UML
* USL
* SysML

Software
engineers

* Victor Basili
* Kent Beck
* Grady Booch
* Fred Brooks
* Barry Boehm
* Peter Chen
* Danese Cooper
* Ward Cunningham
* Tom DeMarco
* Edsger W. Dijkstra
* Delores M. Etter
* Martin Fowler
* Adele Goldstine
* Margaret Hamilton
* C. A. R. Hoare
* Lois Haibt
* Mary Jean Harrold
* Grace Hopper
* Watts Humphrey
* Michael A. Jackson
* Ivar Jacobson
* Alan Kay
* Nancy Leveson
* Stephen J. Mellor
* Bertrand Meyer
* David Parnas
* Trygve Reenskaug
* Winston W. Royce
* James Rumbaugh
* Mary Shaw
* Peri Tarr
* Elaine Weyuker
* Niklaus Wirth
* Edward Yourdon

Related fields|

* Computer science
* Computer engineering
* Project management
* Risk management
* Systems engineering

* Category
* Commons

0.00

(0 votes)

Original source: https://en.wikipedia.org/wiki/Essential systems analysis. Read more

|

Retrieved from "https://handwiki.org/wiki/index.php?title=Essential_systems_analysis&oldid=2624790"
*[v]: View this template
*[t]: Discuss this template
*[e]: Edit this template