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 14
14 CHAPTER 3 DESIGN AND TESTING OF PROTOTYPES INTRODUCTION 3. Develop the design specifications, expanding the basic requirements collected at focus group and NCHRP panel As noted in Chapter 2, the focus group and the NCHRP meetings. panel recommended advancing the development of two pro- totypes: the HPST and ECREL. In order to finish the design of the prototypes, it was important to understand the ways Develop in which the prototypes might be used within the existing resource evaluation process. The Business Case document 4. Develop the evaluation criteria and test plans (i.e., the (Appendix A), originally developed for the focus group, pro- surveys or other instruments that will be used to evalu- vided background information on this process. The process ate the prototype). that CRM professionals normally use (or should be using, 5. Develop the prototype, and test the prototype using based on the Secretary of the Interior's Standards for Historic URS team members (i.e., URS and SRI Foundation Preservation Planning and National Register guidance) was personnel). analyzed in the Business Case. The goal of the two proto- types is to help CRM professionals determine whether or not a property is eligible for listing in the National Register. By Verify focusing on how the two tools might be used to streamline and improve the existing evaluation process, the design team 6. Develop a draft user guide, and have the state CRM pro- was more likely to create usable products. fessional from the design team test the system (i.e., Table 2 describes the current process and shows how the acceptance testing). When the CRM professionals (from two prototypes might be used to facilitate and improve the URS and the state) have signed off on the prototype, the evaluation process. It is important to note that no attempt was verification process is complete. The verification process made to re-engineer or improve the current business process. certifies that the design requirements have been met. (A The reports created from the HPST are not intended to replace verification and validation plan was developed as part National Register nomination forms. The HPST reports are of the design process [see Appendix B].) to be used to communicate the results of an evaluation among consultants, DOTs, SHPOs, and other Section 106 consult- ing parties. Validate 7. Deliver the final products to the test state(s), providing OVERVIEW OF DESIGN AND TESTING PROCESS an evaluation form. 8. Have the test states evaluate the prototype and send The general approach used to create the two prototypes their responses back to URS. was design, develop, verify, and validate. The steps for each are listed below. The specifics of how each step was executed for each of the prototypes are described below. During the design and validation stages, it was difficult to obtain the hoped for level Design of state involvement. Several focus group members provided some input into the ECREL design process, but the HPST 1. Identify a state that will participate in the design process. design was completed only with URS staff. In large part, this Work with URS CRM professionals, IT professionals, occurred because ECREL is web based, allowing the design and a state CRM professional to design each prototype. team to display interim products over the web for review. 2. Identify the state(s) that will evaluate the prototype, and The HPST is a desktop system and requires that the design- secure their agreement to participate. ers be in the same place to work with the developers. In order