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.

Slides:



Advertisements
Similar presentations
Visio 2007 for UML Tutorial. Overview The tutorial demonstrates how to use Visio 2007 to create UML diagrams. We will focus on five most widely used UML.
Advertisements

DATA PROCESSING SYSTEMS
IFS310: Week 3 BIS310: Structured Analysis and Design 5/4/2015 Process Modeling and Data Flow Diagrams.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Systems Analysis and Design in a Changing World, Fourth Edition
Software Testing and Quality Assurance
SE 470 Software Development Processes James Nowotarski 21 April 2003.
Eduardo Miranda C. Marc Ramirez Stanford University PEER Annual Meeting - Thrust Area 1 Meeting Jan. 20 th, 2007 PEER Loss Estimation Toolbox.
1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senn’s Information Technology, 3 rd Edition Chapter 11 Creating Enterprise.
Documenting Requirements using Use Case Diagrams
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
SwE 313 Introduction to Rational Unified Process (RUP)
 Fayad SJSU -- CmpE Software System Engineering Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College of Engineering San.
Kalle Mikkolainen Presenting Flowchart POWERPOINT 2010.
Chapter 7: The Object-Oriented Approach to Requirements
Chapter 6– Artifacts of the process
Strategies for IT Adoption in the Building Industry © 2002 Prof. C.M. Eastman & Dr. R. Sacks Modeling business, engineering and management processes.
Free Mini Course: Applying SysML with MagicDraw
SOFTWARE ENGINEERING BIT-8 APRIL, 16,2008 Introduction to UML.
Class Instructor Name Date. Classroom Tips Class Roster – Please Sign In Class Roster – Please Sign In Internet Usage Internet Usage –Breaks and Lunch.
Software Inspection A basic tool for defect removal A basic tool for defect removal Urgent need for QA and removal can be supported by inspection Urgent.
ITEC 3220M Using and Designing Database Systems
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
SWE © Solomon Seifu CONSTRUCTION. SWE © Solomon Seifu Lesson 13-2 Testing.
UML The Unified Modeling Language A Practical Introduction Al-Ayham Saleh Aleppo University
Key Takeaway Points A use case is a business process; it begins with an actor, ends with the actor, and accomplishes a business task for the actor. Use.
Florida Public Hurricane Loss Model - v5.0 ( Computer Science ) Dr. Shu-Ching Chen School of Computing and Information Sciences Florida International University.
Chapter 7 System models.
Lecture 7: Requirements Engineering
Actors and Use Case Diagrams Month Day, Year. Agenda Training Plan Overview Review Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration.
Session 9 Component and Deployment. OOAD with UML / Session 9 / 2 of 17 Review State Diagrams represent the software entities in terms of their states.
Inspiration 8.0 and Webspiration: The Concept-Mapping Tools of Today Bushra Faisal April 11, 2008.
Copyright © 2013 Curt Hill UML Unified Modeling Language.
Chapter 1 Applying UML and Patterns. The Need for Software Blueprints Knowing an object-oriented language and having access to a library is necessary.
FLORIDA PUBLIC HURRICANE LOSS MODEL V6.1 Computer Science February 2-4, Dr. Shu-Ching Chen School of Computing and Information Sciences Florida.
CASE (Computer-Aided Software Engineering) Tools Software that is used to support software process activities. Provides software process support by:- –
Systems Analysis and Design in a Changing World, Fourth Edition
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Computer Applications Chapter 16. Management Information Systems Management Information Systems (MIS)- an organized system of processing and reporting.
UML - Development Process 1 Software Development Process Using UML.
UML Course Instructor: Rizwana Noor. Overview  Modeling  What is UML?  Why UML?  UML Diagrams  Use Case  Components  Relationships  Notations.
NURHALIMA 1. Identify the trade-offs when using CASE Describe organizational forces for and against adoption of CASE tools Describe the role of CASE tools.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
7 Systems Analysis – ITEC 3155 The Object Oriented Approach – Use Cases.
Engineering Quality Software Week02 J.N.Kotuba1 SYST Engineering Quality Software.
PRODUCT VERIFICATION Adapted from the NASA Systems Engineering Handbook for CSULB EE 400D by Alia Bonetti.
Appendix 2 Automated Tools for Systems Development
Component and Deployment
Chapter 5 – System Modeling
Auditing Information Technology
Recall The Team Skills Analyzing the Problem
Software Engineering Management
1.Introduction to Rational Unified Process (RUP)
Requirements: Use Case Models and Narratives
CH#3 Software Designing (Object Oriented Design)
An Introduction to Visual Basic .NET and Program Design
VISUAL BASIC – CHAPTER ONE NOTES An Introduction to Visual Basic
Software Engineering Management
UML profiles.
Analysis models and design models
Software Design Lecture : 15.
Requirements Management
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
PPT1: Basics of software engineering
Software Engineering System Modeling Chapter 5 (Part 1) Dr.Doaa Sami
PPT4: Requirement analysis
Engineering Quality Software
Chapter 6: Architectural Design
Software Development Process Using UML Recap
Presentation transcript:

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

C-3 Model Architecture and Component Design (3) diagrams illustrating model-related flow of information and its processing by modeling organization personnel or team. February 2-4, Florida International University FPHLM v6.1 2  CS team defined a set of style guidelines for all project members to follow.  Identify the data and participating actors (roles).  Number the information flow sequence.  Include brief description of the information flow being illustrated.  Add a legend if abbreviations/acronyms are used.  UML was chosen as the modeling language.  Diagrams were created using a UML stencil for Microsoft Visio, which provides standard UML 2.x symbols.  CS team provided instructions on how to download and use the template as well as provided references to online resources.

C-3 Model Architecture and Component Design (3) diagrams illustrating model-related flow of information and its processing by modeling organization personnel or team. (continued) February 2-4, Florida International University FPHLM v6.1 3

C-3 Model Architecture and Component Design (3) diagrams illustrating model-related flow of information and its processing by modeling organization personnel or team. (continued) February 2-4, Florida International University FPHLM v6.1 4

5

C-3 Model Architecture and Component Design (3) diagrams illustrating model-related flow of information and its processing by modeling organization personnel or team. (continued) February 2-4, Florida International University FPHLM v6.1 6

C-3 Model Architecture and Component Design (3) diagrams illustrating model-related flow of information and its processing by modeling organization personnel or team. (continued) 7

February 2-4, Florida International University FPHLM v6.1 8

9

C-5 Verification V erification approaches used for externally acquired data, software, and models.  Verification approaches are used for externally acquired data that is used as input or preparation for input into model. No external software or models are used as integral parts of the model.  Meteorology team:  Data is imported into GIS software for thorough inspection.  Data is cross checked with other data sources when available.  For data that is updated, numerical differences between either the raw data or a derived quantity of the updated and original data are computed.  For textual data, such as HURDAT(2), standard Unix tools are used to identify changes in the data. Data is then cross checked against other sources to determine if the changes are reasonable.  For data which are GIS layers, such as ZIP Code boundaries, updated and previous layers are overlaid to visually inspect the data. February 2-4, Florida International University FPHLM v6.1 10

C-5 Verification V erification approaches used for externally acquired data, software, and models. (continued)  Engineering team  Data obtained from county property tax appraisers databases was verified to identify flawed information: visual and graphical scanning for nonsensical data elimination of duplicates review of the consistency of the data based on engineering judgment and comparison with portfolio data. February 2-4, Florida International University FPHLM v6.1 11

C-5 Verification Fully time-stamped, documented cross-checking procedures..., including tester identification...  Compute loss costs for 2013 Form V-3.  Matrix selection of PR code was modified to accommodate special nomenclature of vulnerability matrices for Form V-3.  Program for verifying matrix assignment was coded.  MS Excel spreadsheet to cross-check MHR model calculation.  … February 2-4, Florida International University FPHLM v6.1 12