Skip to main content

Innovations in Software Engineering for Defense Systems (2003) / Chapter Skim
Currently Skimming:

Executive Summary
Pages 1-4

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 1...
... DoD software engineers and test and evaluation officials may not be fully aware of a range of available techniques, because of both the recent development of these techniques and their origination from an orientation somewhat removed from software engineering, i.e., from a statistical perspectlve. The panel's charge therefore was to convene a workshop to identify statistical software engineering techniques that could have applicability to DoD systems in development.
Read the entire page →
From page 2...
... The workshop sessions on specification of requirements focused on software cost reduction and sequence-based software specification. The sessions on test design addressed Markov chain usage testing and combinatorial design testing.
Read the entire page →
From page 3...
... Recommendation 3: Each service's operational or developmental test agency should evaluate the advantages of the use of state-ofthe-art procedures to check the specification of requirements for a relatively complex defense software-intensive system. One effective way of carrying out this evaluation would be to develop specifications in parallel, using the service's current procedures, so that quality metric comparisons can be made.
Read the entire page →
From page 4...
... Recommendation 5: DoD should allocate general research and development funds to support pilot and demonstration projects of the sort recommended in this report in order to identify methods in software engineering that are effective for defense software systems in development. The panel notes that constraints hinder DoD from imposing on its contractors specific state-of-the-art techniques in software engineering and development that are external to the technical considerations of the costs and benefits of the implementation of the techniques themselves.
Read the entire page →

Key Terms

  • test agency
  • developmental test
  • evaluation officials
  • test agencies
  • service test

  • initial steps
  • contractors specific
  • engineering techniques
  • sort recommended
  • addressed markov

  • guide data
  • process improvement
  • root cause
  • training required
  • turnaround rate

  • fault times
  • include fault
  • nor considered
  • constraints hinder
  • throughout development

  • design testing
  • testing methods
  • discussed risk
  • experimental design
  • software evaluation

  • fault types
  • widespread imple
  • identify statistical
  • recent development
  • software developers


    • 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.