Comprehensive Human Factors Guidelines for Road Systems (Web-Only Document) (2005) / Chapter Skim
Currently Skimming:
Pages 9-18
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 9... ...
3.0 General Recommendations for Designing the HFG This chapter, drawn from the project Task 2 report (Lerner et al., 2002a) , summarizes the project team's understanding of what the HFG should be trying to accomplish and how to best achieve these objectives.
|
From page 10... ...
• Problem solving: identify the probable causes and countermeasures when faced with a problem related to road user characteristics • Proactive guidance to include human-centered concerns in design and planning and to avoid potential user-related problems • Promote the understanding of an appropriate road user-centered perspective of safe design • Educate about fundamental human factors principles related to highway safety • Provide a defensible basis for deviating from normal practice when that normal practice is not optimal from a road-user based, highway safety standpoint • Provide adequate documentation as a resource for defense of a design or operational decision • Provide an independent and authoritative basis to reject politically pressured inappropriate design or operational suggestions We view all of these functions as interrelated and all must be addressed to some degree by the HFG. The first two items above (problem solving and proactive design guidance)
|
From page 11... ...
Recognizing that the HFG may often serve a problem-solving need rather than an educational one, it therefore should not be assumed that users will enter the document at the beginning and read the introductory and background chapters. Users will typically enter searching for specific guidance on a particular issue.
|
From page 12... ...
advantage of the CD-ROM over hardcopy. Unfortunately, there is no standardized set of features or user interfaces common to most search engines.
|
From page 13... ...
anticipated file types (PDF, HTML, Word Processor, Database, Spreadsheet, etc.)
|
From page 14... ...
day-to-day guidance with the need for occasional access to detailed backup information and formal research citation and analysis. For purposes of understanding road user capabilities and the role of user-centered thinking in the highway safety system, it is necessary to organize some portion of the HFG around the roadway user.
|
From page 15... ...
and how to use them are not made evident. Users may not be aware of what functions they have available or exactly how they work.
|
From page 16... ...
emphasizes "thinking like a road user." It is meant to be a very "readable" chapter, without a lot of jargon, models, or data. One of the real issues for the HFG is how to motivate a practitioner to read it, other than in a very specific problem-solving mode.
|
From page 17... ...
3.5 Chapter Structure and Features The guidelines chapters (under Parts III and IV) should share a common format and a common approach to presenting the issues and guidance.
|
From page 18... ...
The project team also gave consideration to the inclusion of a decision tree or some other type of diagnostic scheme as an element of each chapter. Such tools might prove to be valuable aids to the practitioner.
|
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.