Skip to main content

Survey Automation Report and Workshop Proceedings (2003) / Chapter Skim
Currently Skimming:

Dealing with Complexity: Broadening the Concept of Documentation
Pages 22-27

The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.


From page 22...
... Second, implementing automated testing will be difficult given its novelty in the survey field; however, that difficulty does not outweigh the need for more rigorous testing than near-exclusive dependence on manual testing permits. Finally, a comprehensive CAPI test suite must always include checks of screen interface, usability, grammar, and other human interface features that are not amenable to automated testing.
Read the entire page →
From page 23...
... A first step in assessing complexity is to visualize computer code as a directed graph (flowgraph) , wherein statements, decision points, and other pieces of code are designated as nodes and the links between them are edges (this graph of the functioning of the software is a much more code-dependent and detailed representation of the functioning of a software system than the graphical model that underlies model-based testing, described earlier)
Read the entire page →
From page 24...
... Develop Prototype Complexity Measures for Existing Surveys The software tools developed by McCabe and his former company act as parsers for a series of common languages, processing code and extracting the flowgraph and complexity measures. Of course, no premade software generates such measures for CASES or Blaise instruments, since those languages being confined to the survey research arena have a relatively small user base.
Read the entire page →
From page 25...
... Complexity in the Code Versus Complexity in the Survey Developing diagnostic measures may help manage the complexity that is due to automation of a survey, the complexity of the underlying computer code. However, coming to terms with complexity in modern surveys also requires serious thought about managing the complexity inherent to the survey itself.
Read the entire page →
From page 26...
... Shown here are schematic diagrams with dots representing specific pieces of node individual lines of code or subroutines and the lines connecting them are function calls or links from routine to routine. The two diagrams differ by only one logical connection; however, the left graph has cyclomatic complexity 10 and essential complexity 1 (perfectly modular in structure)
Read the entire page →
From page 27...
... McCabe's illustrations suggest that mathematical complexity can be increased dramatically by even the smallest of changes in a piece of code. For example, Figure I-4 depicts a schematic piece of code for which adding a single link turns perfectly modularized code into a nearly intractable logical mess.
Read the entire page →

Key Terms

  • cyclomatic complexity
  • complexity measures
  • essential complexity
  • completion times
  • automated testing

  • computer code
  • graphical model
  • survey instruments
  • survey research
  • automated documentation

  • complexity assessment
  • processing code
  • purchase data
  • include checks
  • suggest intriguing

  • logically confounded
  • statistical agencies
  • separate tests
  • single link
  • wherein statements

  • screen interface
  • estimated time
  • dots representing
  • customizable versus
  • decision nodes

  • developing diagnostic
  • useful feedback
  • thomas mccabe
  • individual modules
  • consumer expenditure


    • This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
    More information on Chapter Skim is available.