Modeling Strategy and Mission with UML Rick Murphy Chief Architect, Blueprint Technologies rmurphy@blueprinttech.com June 8, 2004.

Modeling Strategy and Mission with UML Modeling Strategy and Mission with UML

Rick MurphyRick MurphyChief Architect, Blueprint Technologies

rmurphy@blueprinttech.com

June 8, 2004

AgendaAgenda

Aligning IT Direction with Business Strategy

Modeling Enterprise Architecture Modeling Executable Architecture Extending UML Core with Profiles Extended Profiles in the FEA

Take Away: UML is extensible into EA …

Aligning IT Direction with Business StrategyAligning IT Direction with Business Strategy

Mission alignment is the central challenge in enterprise architecture.

In a recent study of 145,000 major IT projects less than 12% fundamentally advanced the strategic goals of the enterprise. – OMG & META

One of our core competencies as enterprise architects is visual modeling on executable architectures.

Crossing levels of abstraction in modeling is complex and creates the perception that we’re all not reading the same playbook.

OMG Position on EA and MDAOMG Position on EA and MDA

We wish, however, to draw attention to the fit between the enterprise alignment strategy supported by META, and the Model Driven Architecture (MDA) recently adopted by the OMG. […] the architecture referred to in MDA can embrace all the concerns of the IT organization, including the information architecture, the technical or infrastructure architecture and the application portfolio.”

- Aligning Enterprise Architecture and IT Investments with Corporate Goals, META & OMG

Conceptual EA Alignment ProcessConceptual EA Alignment Process

Pros•Confirms shared understanding•Justifies Gap Analysis and Sequencing PlanCons•Lacks traceability to implementation•Not executable•Lacks tactical significance

… and there’s free form modeling …

Modeling Enterprise ArchitectureModeling Enterprise Architecture

Authoritative sources provide well defined semantics that justify investments by saving organizations time and money.

MDA crosses levels of abstraction with model-to-model and model-to-code transformations.

Executable architectures efficiently link business objectives with technical implementations resulting in strategic outcomes.

UML leverages consensus of software architecture community to achieve consensus on semantics for use in enterprise architecture.

Strategy DomainStrategy Domain

A Strategic Plan is a source document in every organization that contains a vision, mission, and values

Strategic Goals have objectives and strategies the outcome of which can be measured

Strategic outcomes are evaluated in a balanced scorecard

Enterprise Architecture IntegrationEnterprise Architecture Integration

•Effective integration of EA with CPIC at the select, evaluate, and control phases is essential to achieve strategic outcomes in an EA program•Effective integration of EA with the systems life cycle drives the principles of enterprise architecture into individual systems as a solution architecture

UML Value PropositionUML Value Proposition

Vendor-neutral standard and authoritative source

Best of breed solution based on natural selection

Visual representation of executable architecture

Reduce cost through round trip engineering

Traceability across levels of abstraction Extensible semantics through profiles

Modeling Executable ArchitecturesModeling Executable Architectures

Layered Approach Conceptual, logical, physical

UML Standard Artifacts Use Case, collaboration, sequence

diagrams

Model Driven Architecture Computationally independent, platform

independent, platform specific models

… and how many c-level execs are still with us …

Extending UML Core with ProfilesExtending UML Core with Profiles

Well accepted extensibility mechanism endorsed by Object Management Group (OMG)

Well supported by leading UML product vendors Well structured approach to use of stereotypes,

constraints, and tagged values Light-weight, purely additive extensibility

meaning profiles further restrict the UML reference meta-model

Leverage predefined standard model elements Simpler than developing a new Meta Object

Facility (MOF) based meta-model

Collapsing Top-down and Bottom-up Collapsing Top-down and Bottom-up

Community Collaboration EDOC Profile Web Services Choreography Service Oriented Integration Platform

Example ProfilesExample Profiles

UML 1.5 Specification UML Profile for Software Development

Process UML Profile for Business Modeling

OMG Standards Based UML Profile for EAI UML Profile for EDOC UML Profile for CORBA J2EE & .NET

Example ProfilesExample Profiles

Product Based J2EE .NET

Emerging Technology Profiles IBM Modeling of Automated Business

Process to BPEL4WS Sandpiper Profile for Web Ontology

Language (OWL)

Specifying ProfilesSpecifying Profiles

Stereotype Base Class

Use Case Model Model

Use Case System Package

Use Case Package Package

Object Model Model

… …

Organization Unit Subsystem

Worker Class

Communicate Association

Subscribe Association

StereotypesStereotypes

Semantics New class of meta model element

representing a subclass of an existing model element with the same form but a usage distinction

Notation Symbol from meta-model base element

with guilemetts around keyword <<foo>> Icons can also represent stereotyped

model elementsExample

ConstraintsConstraints

Semantics A relationship among model elements that

specifies conditions and propositions that must be maintained a true

Notation Specified in natural language and Object

Constraint Language (OCL) {condition=value;}

Example

{context Person inv:

self.jobTitle = Enterprise Architect;}

Tag Definition - Specifies the tagged values that can be attached to a kind of model element

Tagged Value – Allows information to be attached to any model element in conformance with the tagged definition

“Interpretation is intentionally beyond he scope of UML semantics” – UML 1.5 Section 2.6.2.5

Tag Definition and Tagged ValuesTag Definition and Tagged Values

Stereotype Base Class Parent Tags Constraints Description

Persistent Class N/A storageMode None Classes of this stereotype are persistent and may be stored in a variety of different modes.

Tag Stereotype Type Multiplicity

Description

storageMode Persistent StorageProfile::StorageEnum(an enumeration:{table,file,object})

* Identifies the storage mode

Modeling ProfilesModeling Profiles

Abstract Syntax representing class and stereotypes

Package specification of an extended profile

E-Government StrategyE-Government Strategy

Models simplified delivery of services to citizens “… a service is viewed as an abstract notion that

must be implemented by a concrete agent. The agent is the concrete entity (a piece of software) that sends and receives messages, while the service is the abstract set of functionality that is provided." - W3C Web Service Architecture Working Group

Based on ad-hoc stereotypes from e-gov and J2EE domains

Federal Enterprise ArchitectureFederal Enterprise Architecture

The FEA is a business and performance-based framework to support cross-agency collaboration, transformation, and government-wide improvement. It provides OMB and the Federal agencies with a new way of describing, analyzing, and improving the Federal Government and its ability to serve the citizen.

Business, performance, data, technology, and service component reference models

Taxonomy of domains, layers, and components

FEA-PMO Service Component Reference ModelFEA-PMO Service Component Reference Model

SRM Service Domain

SRM Service Type

SRM Service Component

Component Granularity

Agency Service Component

Digital Asset Services

Records Management

Digital Rights Management

Business Component

Application Submission Service

Back Office Services

Financial Management

Credit/Charge Business Component System

Application Payment Service

Support Services Security Management

Identification and Authentication, Access Control, Verification and Digital Signature

Federated Component

Single Sign-on Service

Support Services Search Query Business Component

Application Search Service

UML Component DiagramUML Component Diagram

Stereotypes communicate key abstractions from the FEA Service Component Reference Model based on component granularityStereotypes cross levels of abstraction by extending core UML semantics

Useful LinksUseful Links

EA & MDA http://www.omg.org/registration/META-OM

G-WP-Public.pdf

UML Profiles & MDA http://www.omg.org/uml

FEA Service Component Reference Model http://www.feapmo.gov/fea_downloads.asp

Additional questions? rmurphy@blueprinttech.com