Lessons Learned from the Clementine Mission (1997) / Chapter Skim
Currently Skimming:
4 Conlusions
4 Conlusions
Pages 21-22
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 21... ...
An overly ambitious schedule and a slightly lean budget (meaning insufficient time for software development and testing, and leading ultimately to human exhaustion)
|
From page 22... ...
Areas where more appropriately constituted groups may be able to draw additional lessons from the Clementine mission include the following: · An accurate comparison of the cost of Clementine compared to that of a typical science mission · The use of new technology on Clementine; · The pros and cons of a technological alliance between military and civilian space organizations; and · Clementine's software development practices. in conclusion, perhaps the most basic lesson from the Clementine mission is that the ability to carry out endto-end planning and implementation of a (U.S.)
|
Key Terms
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.