Overview of Enterprise Architecture Artifacts

Rob Byrd rob.byrd@austintexas.gov

EA Identifies Common Elements

<<goal>>

Optimize Operations <<goal>>

Respond to Customer Needs <<goal>>

Define Mobile User Processes

<<goal>>

Sustain Environment <<goal>>

Integrate Case and Asset Management

<<goal>>

Increase Revenue

<<goal>>

Conserve Water Resources

<<capability>>

Safe Public

<<capability>>

Manage Infrastructure <<capability>>

Clean Water <<capability>>

Equal Opportunities

<<capability>>

Reliable Energy <<capability>>

Healthy Community

<<capability>>

Healthy Economy

<<capability>>

Mobile Community

<<vision>>

Best Managed City

Identify Common Capabilities

Identify Common Goals

To

p D

ow

n –

Bott

om

Up

Goal setting… Concentration and Dependency Analysis

Has the greatest need

Significantly contributes to goal

Provides the greatest solution

Requirements Analysis Example 1

Requirements Analysis Example 2

<Depends On>

Requirements Analysis Example 3 <

Dep

en

ds O

n>

EA – Part of Governance

Business Need Statement

establishes

consists of

Identifying Common Process

Use Case

Dependency due to the need for meta-data necessary for analysis

Use Case Diagram

Use Case Specification

Use Case Realization

Interface Development

Arrow points to responsible entity (not necessarily information flow)

Interface Realization and Specification Development

Makes service request

System Functional Requirements (example)

Identify Capability Interfaces

Functional Requirements

Reviewer ensures adequate response

Example UML/UPIA System Diagram

Data Dictionary

Follow link to the Austin Data Dictionary

Summary

Strategic Viewpoints provide a means to understand complex relationships – assists in decision-making – identifies measurable goals and milestones

The Use Case provides a process to perform business analysis to derive business needs, identify interfaces and develop system solutions

EA provides a comprehensive critical mass of understanding to maintain project momentum