Web-Based Hazus-MH. A Conceptual Approach. Mourad Bouhafs, AVP ATKINS Atlanta mourad.bouhafs@atkinsglobal.com

Transcription

1 Web-Based Hazus-MH A Conceptual Approach Mourad Bouhafs, AVP ATKINS Atlanta mourad.bouhafs@atkinsglobal.com 1

2 Outline Needs Assessment Hazus-MH and the Web Hazus-MH as a Web Service/Web API Introduction to REST Hazus-MH Web API Demo 2

3 Needs Assessment Disclaimer Nothing s wrong with current desktop-based Hazus-MH, BUT Alternate Solutions Web-based Hazus-MH Hazus-MH as a web service Hazus-MH as a web API Web API as a delivery mechanism What is it? Pros and Cons Applicability to Hazus-MH 3

4 Hazus-MH and the Web Hazus-MH functionality does not lend itself easily to a web implementation: Data size and scale Usability Hosting challenges GIS Performance and scalability Current architecture limitations Distribution model constraints 4

5 Hazus-MH as a Web-Service/Web API Source: Hazus-MH as a Platform Hazus-MH as a Service (SaaS) Hazus-MH as a Data Service 5

6 SaaS Architecture SaaS apps follow the Client-Server pattern (client makes requests to a server) A SaaS server follows the 3-tier architecture pattern (Hazus-MH implemented this since its first version after Hazus 1997/99) SaaS app code lives in the application tier. Should follow the Model-View-Controller (MVC) pattern 6

7 MVC Hierarchy Model => Active Record Pattern View => Template View Pattern Controller => REST (Representatial State Transfer) 7

8 Introduction to REST Created by Roy Fielding (doctoral dissertation) Meant to take better advantage of standards and technologies in HTTP than SOAP does Rather than creating arbitrary SOAP methods, REST encourages the use of HTTP verbs: GET, POST, PUT, DELETE REST is resource-centric: RESTful API use HTTP verbs to act on or fetch information about resources. These would be the nouns REST takes advantage of other HTTP aspects: caching, security, statelessness, network layering 8

9 REST Implementation Resources 9

10 Aggregated Data Hierarchy Level 1 (State) 10

11 Aggregated Data Hierarchy Level 2 (County) 11

12 Aggregated Data Hierarchy Level 2 (County) 12

13 Aggregated Data Hierarchy Level 3 (Tract) 13

14 Aggregated Data Hierarchy Level 3 (Tract) 14

15 Aggregated Data Hierarchy Level 4 (Block) 15

16 Aggregated Data Hierarchy Level 5 (Street Segment) 16

17 Aggregated Data Hierarchy Level 6 (Building) 17

18 API URIs (Uniform Resource Identifiers) Part 1 18

19 API URIs (Uniform Resource Identifiers) Part 2 19

20 Hazus SaaS Deployment 20

21 Hazus SaaS Customization 21

22 Web API vs 3-tier Architecture 22

23 Web API Deliverable 23

24 Demonstration 24

25 Q&A 25

26 Thank you If you d like to find out more: Mourad.Bouhafs@atkinsglobal.com