1. FLORIDA PUBLIC HURRICANE LOSS MODEL V6.1 Computer Science February 2-4, 2015 1 Dr. Shu-Ching Chen School of Computing and Information Sciences Florida International University

2. Extensively updated material related to the model: Adherence to a consistent flowchart standard  CS team defined a set of style guidelines for all model-related flowcharts.  Use standard flowchart symbols.  Differentiate control versus data flow diagrams.  Clearly label components.  Control flow diagrams should have starting and ending points.  Arrows should indicate flow between specific components instead of between enclosed collections of components.  Avoid overlapping arrows. When not possible, add the crossover bump at the intersection point.  Follow a consistent color scheme and style for all diagrams (e.g., always use dashed lines when grouping subcomponents).  Use joins and forks to represent concurrent processes. February 2-4, 2015. Florida International University FPHLM v6.1 2

3. Extensively updated material related to the model: Adherence to a consistent flowchart standard (continued)  CS team compiled the guidelines in a document and provided references to relevant on-line resources.  Document available for review.  CS team met with the engineering team on 6/19/2014 (via videoconference) for clarifications concerning the guidelines.  The engineering team undertook a major redesign of the engineering flowcharts to comply with the agreed-upon standard.  Ongoing process. February 2-4, 2015. Florida International University FPHLM v6.1 3

4. Extensively updated material related to the model: Adherence to a consistent flowchart standard (continued) February 2-4, 2015. Florida International University FPHLM v6.1 4 Monte Carlo Damage Model Simulation Flow Before

5. Extensively updated material related to the model: Adherence to a consistent flowchart standard (continued) February 2-4, 2015. Florida International University FPHLM v6.1 5 Monte Carlo Damage Model Simulation Flow After

6. Extensively updated material related to the model: Adherence to a consistent flowchart standard (continued) February 2-4, 2015. Florida International University FPHLM v6.1 6 MCS-MHB Program Flowchart Before

7. Extensively updated material related to the model: Adherence to a consistent flowchart standard (continued) February 2-4, 2015. Florida International University FPHLM v6.1 7 MCS-MHB Program Flowchart After

8. Extensively updated material related to the model: Adherence to a consistent flowchart standard (continued) February 2-4, 2015. Florida International University FPHLM v6.1 8 OPENINGCORRECTIONFACTOR.m Flowchart Before

9. Extensively updated material related to the model: Adherence to a consistent flowchart standard (continued) February 2-4, 2015. Florida International University FPHLM v6.1 9 OPENINGCORRECTIONFACTOR.m Flowchart After

10. Extensively updated material related to the model: Adherence to a consistent flowchart standard (continued) February 2-4, 2015. Florida International University FPHLM v6.1 10 BUILDINGDIMREASSIGNER.m Flowchart Before

11. Extensively updated material related to the model: Adherence to a consistent flowchart standard (continued) February 2-4, 2015. Florida International University FPHLM v6.1 11 BUILDINGDIMREASSIGNER.m Flowchart After

12. Consistent use of Source Versioning System by all model components.  CS team continued providing training in the use of SVN.  Training at FIT on 02/22/2014 (Minutes available for review).  Answered questions via e-mail and in-person meetings in CS lab.  Discussions with all project members during project meetings.  All teams have been using SVN consistently for managing changes to documentation, data, and source code, e.g.,  CS team managed the source codes of both the model and auxiliary software tools.  Statistics team submitted forms and standards (and their subsequent revisions) to editorial expert for inclusion in the submission document.  Engineering team kept track of source code changes in all the model types. They created branches for tests, parameter checks, and model manipulations.  Meteorology team versioned program used to convert HURDAT2 to HURDAT1 format. Committed the text-based HURDAT2 database and Rmax data sets, which were updated as part of the mandatory updates to the input data used by this model component. February 2-4, 2015. Florida International University FPHLM v6.1 12

13. Consistent use of Source Versioning System by all model components. (continued) February 2-4, 2015. Florida International University FPHLM v6.1 13

14. Consistent use of Source Versioning System by all model components. (continued) February 2-4, 2015. Florida International University FPHLM v6.1 14

15. Form A-4B Revision  There was a mistake in the generation of the commercial residential losses in Form A-4B submitted on November 1, 2014.  An outdated shell script was used to select the losses of one output file to be added into a final loss file to generate the form.  The use of the outdated script was due to a human error: the updated script was in SVN, but a file system copy was used instead.  Form A-4B (only affected form) was re-generated and re- submitted upon discovery of the mistake. February 2-4, 2015. Florida International University FPHLM v6.1 15

16. Form A-4B Revision (continued) February 2-4, 2015. Florida International University FPHLM v6.1 16 Outdated Updated

17. Form A-4B Revision (continued) February 2-4, 2015. Florida International University FPHLM v6.1 17 SVN Log

18. 31. C-1.B, p. 370: Relate the primary binder table of contents with the response to Standard G-1, Disclosure 5 (p.105-108) by demonstrating individual table item compliance with Computer Standards C-1 - C-7. Hard copy of the table with changes from the previously accepted submission to the initial submission of this year as well as with all changes since this year’s submission has been made available. Hard copy of the tables that relate the items listed in the table of changes in the model to the affected components or data related to the Computer Standards have been made available. February 2-4, 2015. Florida International University FPHLM v6.1 18

19. 32. C-2, p. 372: Provide requirements documentation that specifically relates to each model change identified in Standard G-1, Disclosure 5 (p. 105-108).  The Primary Document Binder for the FPHLM v6.1 is available for review. February 2-4, 2015. Florida International University FPHLM v6.1 19

20. 32. C-2, p. 372: Provide requirements documentation that specifically relates to each model change… (continued) February 2-4, 2015. Florida International University FPHLM v6.1 20

21. 33. C-5, p. 376-378: Provide complete and thorough verification procedures and output from the model changes identified in Standard G-1, Disclosure 5 (p. 105-108).  The Test Report is available for review. February 2-4, 2015. Florida International University FPHLM v6.1 21

22. 34. C-6.D, p. 379: Provide the model version history over the past 5 years, leading up to the version identified in the submission.  Hard copies of the FPHLM version history leading up to version 6.1 are available for review. February 2-4, 2015. Florida International University FPHLM v6.1 22