1 / 27

GIS Architecture for the Enterprise Modeling a Technology Solution in UML

GIS Architecture for the Enterprise Modeling a Technology Solution in UML. Robert W. McKitrick Jr. NC Department of Transportation GIS Unit February 27, 2015. Why Model a GIS Technology Solution?. Communicate Design GIS Functions (Conceptual Model) GIS Infrastructure GIS Clients

nhenry
Download Presentation

GIS Architecture for the Enterprise Modeling a Technology Solution in UML

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GIS Architecture for the EnterpriseModeling a Technology Solution in UML Robert W. McKitrick Jr. NC Department of Transportation GIS Unit February 27, 2015

  2. Why Model a GIS Technology Solution? • Communicate Design • GIS Functions (Conceptual Model) • GIS Infrastructure • GIS Clients • Simplify Change • Performance Improvements • Version Upgrades • Adding Applications / Services

  3. Why Model a GIS Technology Solution? • Communicate Design • GIS Functions (Conceptual Model) • Authoring Spatial Data • Publishing Spatial Data • Using Spatial Data • GIS Infrastructure • GIS Clients

  4. Why Model a GIS Technology Solution? • Communicate Design • GIS Functions (Conceptual Model) • GIS Infrastructure • Provisioning / Deploying Servers • Application Deployment • Network Communications • GIS Clients

  5. Why Model a GIS Technology Solution? • Communicate Design • GIS Functions (Conceptual Model) • GIS Infrastructure • Provisioning / Deploying Servers • Application Deployment • Network Communications • GIS Clients

  6. Why Model a GIS Technology Solution? • Communicate Design • GIS Functions (Conceptual Model) • GIS Infrastructure • Provisioning / Deploying Servers • Application Deployment • Network Communications • GIS Clients

  7. - The System Communication Model shows inter-system communication only (no clients). - Infrastructure accessible by all servers is not shown. e.g. File servers, DNS, administrative consoles, and monitoring systems.

  8. Several layers of firewall.

  9. Note non-standard port for ArcGIS Server. Network protocol is TCP if not specified. Note UDP protocol for SQL Server.

  10. Note Stereotype of <<ServerFarm>>. “Eye glasses” indicate drill down.

  11. For calculating firewall rules, the <<ServerFarmCommunication>> aggregates all IP address/port combinations coming into the source to create rules to the target. e.g. The rules from this diagram only woud be: “GisPsProd” is the same element as the one we clicked on to get to this diagram. Any change to either element automatically shows up in both diagrams.

  12. Why Model a GIS Technology Solution? • Communicate Design • GIS Functions (Conceptual Model) • GIS Infrastructure • GIS Clients

  13. Similar to the <<ServerFarm>> we use an <<AggregateView>> stereotype to aggregate firewall rules in these client communication models.

  14. Part of one of the many client communication models. Firewall rules and who has access to what gets complicated very quickly.

  15. NCDOT GIS System - TOC - Top level view having only the initial navigation diagram. - All the diagrams so far are from the “<<system>> NCDOT EGIS” model view.

  16. NCDOT GIS System - TOC - Capturing dependents and dependencies helps to support maintenance and troubleshooting regardless of the issue.

  17. NCDOT GIS System - TOC - Very complex applications require model views of their own.

  18. NCDOT GIS System - TOC - Building blocks

  19. The “Building Blocks” Make the Model

  20. The “Building Blocks” Make the Model

  21. The “Building Blocks” Make the Model

  22. The “Building Blocks” Make the Model

  23. Summary • Using UML Stereotypes adds semantics and supports automation • Using classifiers simplifies managing changing server types • Hundreds of (organized) elements are easily managed with the UML • This model evolved over time • ROI cannot be quantified but the number of times it is used for documentation and discussion makes it feel like it is worth the work.

  24. Questions?

More Related