Skip to main content

Advanced Engineering Environments Achieving the Vision, Phase 1 (1999) / Chapter Skim
Currently Skimming:

4 Barriers
Pages 29-33

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 29...
... Integration problems are caused by many factors, and addressing them all will not be easy. To begin with, software tools are inherently incompatible unless interoperability was a specific goal of the software development process used to create them.
Read the entire page →
From page 30...
... Although many of the organizations had documented processes for their engineering enterprise, few actually adhered to them, and there was not enough continuity or commonality among the elements of individual organizations, especially between research and operational elements. One way to create highly integrated AEEs is through the use of open architectures that allow the insertion of new elements using interfaces designed in accordance with predefined standards.
Read the entire page →
From page 31...
... For example, when Boeing upgrades its CAD software, legacy data are migrated upward into the upgraded software, but it is also retained in the original format. Retention of original data is required by the Federal Aviation Administration to enable reviews of the original product definition during accident investigations, certification of design modifications, and other purposes.
Read the entire page →
From page 32...
... Furthermore, program managers at agencies like NASA are often involved in complex first- or one-of-a-kind missions, such as the international space station or a planetary exploration mission. Using AEE simulations to replace physical tests on these missions would be especially risky without reliable methods for continuously validating the simulations.
Read the entire page →
From page 33...
... Therefore, some companies may replace comprehensive training on new tools with a strategy that trains staff to perform specific software functions only as needed. This would reduce unnecessary training, shorten the time between training and practical application, and minimize the need for retraining.
Read the entire page →

Key Terms

  • software tools
  • protect proprietary
  • software vendors
  • design process
  • proprietary data

  • configuration management
  • aee capabilities
  • labor costs
  • aee simulations
  • physical tests

  • support aee
  • design processes
  • implementing aee
  • shuttle simulators
  • aee tools

  • increasing complexity
  • technology standards
  • using aee
  • product life
  • training facilities

  • maintaining configuration
  • unauthorized users
  • aees protect
  • engineering processes
  • integrated aees

  • design modifications
  • labor force
  • securing funding
  • advanced tools
  • acquisition programs


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