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. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.
Architecture • A system architecture is the conceptual design that defines the structure and/or behavior of a system • There is no universally agreed definition • Systems architecture can best be thought of as a representation • Maybe expressed in hardware, software, or organizational management • It is also a process because a sequence of steps • It can also be a discipline
Past Implementations Community Organizational Federated Department
New(er) Implementations Mash Up Multiple Client Platforms Feeds SOA
SOA - Packaging functionality as a suite of interoperable services that can be used within multiple separate systems from several business domains. Web Web Client Enterprise Service Bus HighestPointService Point-to-Point Services Services Oriented Architecture (SOA) Web Client • Interconnected • Interoperable • Integrative • Dynamic Highest Point Service Terrain Service Loosely Coupled and Orchestrated Services
Mash Up GIS with Other Web Services Web Browser “Mash-Up” content ArcGIS Server Internet ArcGIS Servers & ArcGIS Online User Data Google Maps/Virtual Earth/…
Serve and Consume Information Feeds • Feed Types: • RSS • GeoRSS • CAP • KML • SensorML • Video • Produce: • Mobile Clients • In-situ sensors • Consume: • Visualize • Analyze
Many Client Platforms Mobile Devices Web Map Viewers 2D / 3D Explorers Open APIs Desktops Manage-Serve Management Find-Integrate-Use Author Visualization Desktop GIS Analysis ArcGIS Server
FederatedSOA? Federated Architecture (FA) allows interoperability and information sharing between semi-autonomous de-centrally organized lines of business (LOBs). SOA - Packaging functionality as a suite of interoperable services that can be used within multiple separate systems from several business domains.
Tomlinson’s 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
Software selection • Summarize the function requirements
Views of a System Architecture • ISO Reference Model of Open Distributed Processing (RM-ODP) • Enterprise Viewpoint: • It is directed to the needs of the users of an information system. • Information Viewpoint: • It focuses on the information content of the enterprise. • Computational Viewpoint: • It deals with the logical partitioning of the distributed applications independent of any specific distributed environment on which they run. • Engineering Viewpoint: • It addresses the issues of system support (platform) for distributed applications. • Technology Viewpoint: • The technology model identifies possible technical artifacts for the engineering mechanisms, computational structures, information structures, and enterprise structures.
. Architecture Development
Steps • Defining Architecture Requirements. • to enable the system to meet the community’s goals and objectives. • Defining a Candidate Architectures. • to evolve an architecture gradually. • Defining Enterprise Architecture. • integrate it into an enterprise architecture model. • Defining Reference Architecture. • a working example designed and proven for use in by the participants • Validating a Reference Architecture.