1. Tomlinson’s “System” Design Requirements

2. 10 Stages Stage 1: Strategic purpose Stage 2: Plan for planning Stage 3: Technology seminar Stage 4: Describe information products Stage 5: Define system scope Stage 6: Create the data design Stage 7: Choose the logical model Stage 8: Determine system requirements Stage 9: Cost benefit Stage 10: Plan for implementation

3. Software selection Summarize the function requirements

4. Emerging Technologies Feeds Structured and unstructured metadata SOA Mash Up Multiple Client Platforms Business Modeling http://feeds.feedburner.com/TheNsgicBlog

5. WebClient Enterprise Service Bus TerrainService HighestPointService Loosely Coupled and Orchestrated Services Services Oriented Architecture (SOA) InterconnectedInterconnected InteroperableInteroperable IntegrativeIntegrative DynamicDynamic WebClient Web 1.0 Point-to-Point Services Highest Point Service SOA – a Framework for Integration

6. Google Maps/Virtual Earth/… Internet User Data Web Browser ArcGIS Server “Mash-Up” content ArcGIS Servers & ArcGIS Online Mash Up ArcGIS with Other Web Services

7. Serve and Consume Information Feeds Feed Types: RSS GeoRSS CAP KML SensorML Video Produce: Mobile Clients In-situ sensors Consume: Visualize Analyze

8. Expect Many Client Platforms Web Map Viewers Desktops 2D / 3D Explorers MobileDevices Open APIs ArcGIS Desktop Author Management Visualization Analysis ArcGIS Server Manage-Serve Find-Integrate-Use

9. Apply Enterprise Business Models Enterprise GIS requires Enterprise Business Models: –Inventory Management (Metadata) –Production Planning (Who, What, When) –Supply Chain Management (TFTN/TNM) Rationalization for efficiency and use Consolidation, Integration, Acquisition, and Support © Booz Allen Hamilton http://www.3gerp.org ArcGIS JTX – Geospatial Workflows

10. Build on What You Have …. … SOA Is Evolutionary, Not Revolutionary Implementing SOA Requires Multiple Initiatives Understand Business Processes –Distill Processes –Define Services Construct Common Services Develop Applications –Rapid Prototyping –Understand/engage Mission Consider SOA Platform Implement Web Service Standards –WSDL, UDDI, XML, SOAP Service Connectors Existing Capabilities Service Enabled Components Legacy Legacy Legacy Deactivate COTS-BasedCapability COTS-BasedReplacement Legacy Replace Wrap Connect Legacy Retire Enterprise Service Bus Three Migration Approaches

11. Kentucky Watershed Modeling Information Portal

12. ESRI (c) 200712 Derive elevation Query National Grid Derive Elevation Profile Delineate Watershed Boundary Avian Flue Cluster Analysis Earthquake Prediction Hurricane Path Prediction … Authentication Access Control Thesaurus ArcXML, KML WMS, WFS, WCS OpenLS REST, SOAP … CS-W UDDI Service Monitoring … Server Caching High Performance Thematic Base Maps Integrated content … Services Architecture for SDI OGC Compliant Mobile Desktop GIS 2-D & 3-D “Science Viewers” Use Environment GIS Portals Custom Applications 3-D Base Map 2-D Base Map OGC Services Tracking Services GIS Data Data Streams Catalog Services Metadata Geo- processing Services Geospatial Web Services PlatformCatalogData Warehouse Supporting Services GIS Data Authentication Services Places Addresses Location Services Extraction Services Development API SOAP/REST GIS Data Thesaurus Services

13. Interface & Communicati0ons System interface Network Architecture –Central file server –Central DBMS –Centralized application processing –Web transactions

14. Interface and Communications Reqt’s Wait tolerance Data location User Sites/workflows Current configuration

15. Other factors Distributed GIS & Web Services Platform sizing and bandwidth