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

Department

CommunityOrganizational

Federated

New(er) Implementations

Feeds

SOA

Mash Up Multiple ClientPlatforms

WebClient

Enterprise Service Bus

Terrain

Service

Highest

Point

Service

Loosely Coupled and Orchestrated Services

Services Oriented Architecture (SOA)

• Interconnected• Interoperable• Integrative• Dynamic

WebClient

Web

Point-to-Point Services

Highest Point Service

SOA - Packaging functionality as a suite of interoperable services that can be used within multiple separate systems from several business

domains.

Google Maps/Virtual Earth/…

Internet

User Data

Web Browser

ArcGIS Server

“Mash-Up” content

ArcGIS Servers & ArcGIS Online

Mash Up GIS with Other Web Services

Serve and Consume Information Feeds

Feed Types:• RSS• GeoRSS• CAP• KML• SensorML• VideoProduce:• Mobile Clients• In-situ sensorsConsume:• Visualize• Analyze

Many Client Platforms

Web MapViewers

Desktops

2D / 3DExplorers

MobileDevices

OpenAPIs

DesktopGIS

Author

Management

Visualization

Analysis

ArcGIS Server

Manage-Serve

Find-Integrate-Use

Federated SOA?

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.

Keep those thoughts!

New Thoughts

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.