Abstract
Chapter 7 discussed the concept of the logical equivalent, justifying and defining it by showing a functional decomposition example using data flow diagrams. In this section, we will expand upon the capabilities of the DFD by explaining its purpose, advantages, and disadvantages (described later as the good, the bad, and the ugly) and most important: how to draw and use it.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Notes
- 1.
Yourdon (1989, pp. 134–135).
- 2.
DeMarco, Tom, Structured analysis and system specification, pp. 85–86.
- 3.
The case method should not be confused with CASE (Computer Aided Software Engineering) products, which is software used to automate and implement modeling tools and data repositories.
- 4.
Microsoft Press, Computer Dictionary, Second Edition, pg. 149.
References
DeMarco, T. (1979). Structured analysis and system specification. Englewood Cliffs, NJ: Prentice Hall.
Yourdon, E. (1989). Modern structured analysis. Englewood Cliffs, NJ: Prentice Hall.
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
Copyright information
© 2011 Springer-Verlag London Limited
About this chapter
Cite this chapter
Langer, A.M. (2011). Creating Requirement Documents Using Analysis Tools. In: Guide to Software Development. Springer, London. https://doi.org/10.1007/978-1-4471-2300-2_8
Download citation
DOI: https://doi.org/10.1007/978-1-4471-2300-2_8
Published:
Publisher Name: Springer, London
Print ISBN: 978-1-4471-2299-9
Online ISBN: 978-1-4471-2300-2
eBook Packages: Computer ScienceComputer Science (R0)