Entry Hosch:1977:WF from sigcse1970.bib

Last update: Sun Apr 22 02:03:34 MDT 2018                Valid HTML 4.0!

Index sections

Top | Symbols | Numbers | Math | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z

BibTeX entry

@Article{Hosch:1977:WF,
  author =       "Frederick A. Hosch",
  title =        "Whither flowcharting?",
  journal =      j-SIGCSE,
  volume =       "9",
  number =       "3",
  pages =        "66--73",
  month =        aug,
  year =         "1977",
  CODEN =        "SIGSD3",
  DOI =          "https://doi.org/10.1145/382175.803437",
  ISSN =         "0097-8418 (print), 2331-3927 (electronic)",
  ISSN-L =       "0097-8418",
  bibdate =      "Sun Nov 18 08:53:57 MST 2012",
  bibsource =    "http://portal.acm.org/;
                 http://www.math.utah.edu/pub/tex/bib/sigcse1970.bib",
  note =         "Special issue on the Eighth Technical Symposium on
                 Computer Science Education.",
  abstract =     "During the past few years, a growing number of authors
                 have begun to take exception to the previously
                 unquestioned use of flowcharts as a program development
                 tool. These criticisms of the traditional flowcharting
                 methodology center around the claim that flowcharts,
                 like goto's, belong to the class of objects that are
                 detrimental to good programming. Suggested alternatives
                 range from developing programs entirely in
                 well-structured high level languages to replacing
                 conventional flowcharts by some form of ``structured''
                 flowcharts. We are particularly concerned with
                 questions that have been raised regarding the value of
                 flowcharting in introductory programming classes. The
                 teaching of flowcharting as a developmental tool is
                 extremely widespread indeed. While the various methods
                 of indicating data flow, document flow, etc., are
                 certainly an important part of program development and
                 documentation, we consider here only conventional
                 ``flow of control'' flowcharts.",
  acknowledgement = ack-nhfb,
  fjournal =     "SIGCSE Bulletin (ACM Special Interest Group on
                 Computer Science Education)",
  journal-URL =  "http://portal.acm.org/browse_dl.cfm?idx=J688",
}

Related entries