The VTI National Transport Library Catalogue

Bridge software : Validation guidelines and examples Michael Baker Jr. Inc. et al

By: Michael Baker Jr. IncPublication details: Washington DC National Cooperative Highway Research Program, 2003; NCHRP report 485, Description: 23 s. + bil, 2 CD-skivor CDISBN: 0309068118Subject(s): USA | Bridge | | Calculation | | Specifications | 35Online resources: Publikation/Publication Bibl.nr: VTI P0409:485Location: Abstract: Computer software is needed to permit a full adoption of the AASHTO LRFD Bridge Design Specifications as the standard specification. AASHTO is addressing this issue through joint development of AASHTOWare BridgeWare Products, and others are also developing software systems. Because of the complexity of the specifications, designers and bridge owners need a way to ensure that the software is valid and reliable. A standard validation process is needed to achieve this goal. The objective of this project was to develop a methodology for bridge-design software validation. This objective has been achieved with the development of "Process 12-50," a systematic method of comparing and evaluating bridge design and analysis software. Process 12-50 also provides a standardized report format for presenting and comparing results for a specific bridge design and a powerful method for formally reviewing specification changes.
Item type: Reports, conferences, monographs
Holdings: VTI P0409:485

Computer software is needed to permit a full adoption of the AASHTO LRFD Bridge Design Specifications as the standard specification. AASHTO is addressing this issue through joint development of AASHTOWare BridgeWare Products, and others are also developing software systems. Because of the complexity of the specifications, designers and bridge owners need a way to ensure that the software is valid and reliable. A standard validation process is needed to achieve this goal. The objective of this project was to develop a methodology for bridge-design software validation. This objective has been achieved with the development of "Process 12-50," a systematic method of comparing and evaluating bridge design and analysis software. Process 12-50 also provides a standardized report format for presenting and comparing results for a specific bridge design and a powerful method for formally reviewing specification changes.

Powered by Koha