Skip to main content
  • 1858 Accesses

Abstract

Structured design has its genesis in Edsger Dijkstra’s famous 1968 letter to the Communications of the ACM, “Go To Statement Considered Harmful.” Dijkstra’s paper concludes with

The go to statement as it stands is just too primitive; it is too much an invitation to make a mess of one’s program. One can regard and appreciate the clauses considered (ed. if-then-else, switch, while-do, and do-while) as bridling its use. I do not claim that the clauses mentioned are exhaustive in the sense that they will satisfy all needs, but whatever clauses are suggested (e.g. abortion clauses) they should satisfy the requirement that a programmer independent coordinate system can be maintained to describe the process in a helpful and manageable way.2

Invest in the abstraction, not the implementation. Abstractions can survive the barrage of changes from different implementations and new technologies” —Andy Hunt and Dave Thomas

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  • Dahl, O. J., E. Dijkstra, et al. (1972). Structured Programming. (London, UK: Academic Press, 1972.)

    MATH  Google Scholar 

  • Dijkstra, E. “GoTo Statement Considered Harmful.” Communications of the ACM 11(3): 147–148. (1968)

    Article  MathSciNet  Google Scholar 

  • Hunt, A. and D. Thomas. The Pragmatic Programmer: From Journeyman to Master. (Boston, MA: Addison-Wesley, 2000.)

    Google Scholar 

  • McConnell, S. Code Complete 2. (Redmond, WA: Microsoft Press, 2004.)

    Google Scholar 

  • Miller, G. A. “The magical number seven, plus or minus two: Some limits on our capacity for processing information.” Psychological Review 63: 81–97. (1956)

    Article  Google Scholar 

  • Parnas, D. “On the Criteria to be Used in Decomposing Systems into Modules.” Communications of the ACM 15(12): 1053–1058. (1972)

    Article  Google Scholar 

  • Wikipedia. Separation of Concerns. 2009. http://en.wikipedia.org/wiki/Separation_of_concerns. Retrieved on December 7, 2009.

    Google Scholar 

  • Wirth, N. “Program Development by Stepwise Refinement.” CACM 14(4): 221–227. (1971)

    Article  MATH  Google Scholar 

Download references

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2011 John Dooley

About this chapter

Cite this chapter

Dooley, J. (2011). Structured Design. In: Software Development and Professional Practice. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4302-3802-7_7

Download citation

Publish with us

Policies and ethics