Sabtu, 17 Oktober 2015

Proposed Case Study Format

Proposed Case Study Format
Purpose and Objective The objective of this effort is to: a) assemble an extensive set of case studies that adequately demonstrate various approaches and the value or benefit of the results of risk assessment, for various types of applications; b) make the case studies widely available, e.g., on the web site, and easy to use; and c) minimize the effort required to assemble and maintain the data base, while ensuring adequate quality and security. To facilitate their use, it would be desirable that these case studies be categorized in terms of scope, approach and application, consistent with the risk guidelines / glossary / bibliography currently being prepared. A potential problem may be the confidential nature of some projects, which would require specific measures to allow publication. It will be the author’s responsibility to obtain any client approval needed.
Background TC32 Core Members Ken Ho and Bill Roberds developed several example case studies, which were handed out at the 2003 TC32 meeting. The consensus of those at the TC32 meeting was that Ken’s example needed more information (including author / contact, categorization / keywords, and discussion of value / benefit, which in turns needs definition of criteria) and more detail (similar to the discussion of approach, including graphics, in Bill’s examples, but without commercial messages), but in any case each case study should be limited to 3 pages.
Approach To ensure completeness and uniformity, a WORD template for case studies will be developed that can be downloaded off the web site and then submitted electronically to the “gatekeeper of case studies” once completed by the author and reviewed by an independent expert (i.e., a member of TC32); the gatekeeper can arrange for a reviewer if the author can’t. The reviewer will check the case study to ensure that it is complete and appropriate (e.g., there are no commercial messages and that the author certifies that client approval has been obtained). Even so, the web site will need a disclaimer (especially with respect to client approval being the author’s responsibility, ala ASCE). The gatekeeper will be the only one who is authorized to post case studies (once submitted and reviewed) or to modify or remove case studies that have already been posted. Farrokh Nadim (NGI) will be the gatekeeper, or will delegate that responsibility.
TemplateTitle: <fill in short / concise descriptor of scope / application / approach>Contact: <fill in author’s name, affiliation, phone, email>

Tidak ada komentar: