Click for next page ( 32


The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement



Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 31
Defining the System 31 Reporting Although reporting may seem a minimal design consideration, it has the potential to be one of the items most responsible for project creep. You will want to define the critical documents and reports that are necessary for your business activities and ensure these are included in the technical design. You will also want to create a running collection of desired reports that you identify during the implementation process and after the system is in place. The 8-55A logical model does not explicitly address reporting although it does include required documents as identified in the FHWA Project Development Guide.