Innovate2011_MAC-1597A

June 5–9 Orlando, Florida
Developing Enterprise
Component, Service, and
Integration Architectures
Based on Open Industry
Standards
Arman Atashi
Senior Application Architect
BlueCross BlueShield of North Carolina
arman.atashi@bcbsnc.com
MAC-1597A

The Premier Event for Software and Systems Innovation
2 © 2011 IBM Corporation
 Introduction
 Modeling Framework
 MDA & UML Usage
 Modeling Workflow
 Modeling Environment
 Context for Enterprise Modeling
 Summary & Vision
 Walkthrough
Agenda

Introduction
 This session provides an insight into M3 (Modeling at 3 levels), a disciplined agile
system modeling framework and workflow based on Object Management Group
model driven architecture guidelines and unified modeling language notation and
utilizing IBM Rational Software Architect, IBM Rational Team Concert, and IBM
Rational Asset Manager
 M3 modeling methodology has been created around three broad strategies:
Apply fundamentals of model driven service-oriented architecture and unified modeling
language to modeling enterprise software architecture
Address the increasing complexity in enterprise integration architecture and business
capabilities
Support both top-down and bottom-up approaches and manage and reuse architectural
models and assets throughout their lifecycle

MODELING FRAMEWORK
3
3
™

M3 Framework
 M3 framework identifies five components necessary for developing and
maintaining enterprise models
Modeling
Workflow
M3
Framework
Components Integration
Model
View
Aggregation
Modeling
Notation
Modeling
Environment
3
3
™

Framework Components
 Modeling Notation
Unified Modeling Language (UML) standard notation and its
profile based extensions such as Service oriented architecture
Modeling Language (SoaML) for visualizing, modeling,
communicating, and specifying system models
Models are constructed from UML elements that are used in
structural and behavioral diagrams
M3 uses a subset of UML diagrams and elements
Other diagrams and elements may be used as needed

 Modeling Workflow
Based on Model Driven Architecture (MDA) principles and
disciplines, models are constructed at 3 levels:
 The Outside: Computation Independent Model (CIM)
 The Edge: Platform Independent Model (PIM)
 The Inside: Platform Specific Model (PSM)
The Outside - CIM
The Inside - PSM
The Edge - PIM
Guiding Principles
 Consistent Model Structure: Cross-model
interrelationships, which form the basis of consistent model
structures, must be adhered to
 Recursive Decomposition / Refinement: Models must
provide an increase in the level of details with vertical model
transformation (Outside  Edge  Inside)
 Semantic Meaning: Models must be expressed at similar
levels of precision at each modeling level

 Integration Model
M3 extends MDA’s standard viewpoints and defines
Integration Specific Model (ISM), subset of the other three
viewpoints but not adhering to cross-model interrelationships
guiding principle
ISM captures and reflects the supported integration levels
and views as modeled in CIM, PIM and PSM
ISM adheres to the standard Enterprise Integration
patterns/solutions
Client models will only need to access/include ISM when
modeling integration solutions
CIM
PIM
PSM
ISM
dependency
Client
Model

 View Aggregation
M3 modeling framework imposes cross-model
interrelationships, which form the basis of coherent and
consistent model structures
The cross-model interrelationships (defined UML packages)
are organized to further facilitate the creation of
specialized/extended views by view aggregation
Specialized views represent different scopes of enterprise
architecture representation including:
 Business
 Information
 Application
 Technical
CIM
PIM
PSM
Specialized
View

 Modeling Environment
M3 modeling lifecycle management is realized by utilizing key
IBM Rational tools, enabling early reviews of the developed
models and promoting team collaboration and model reuse
Model Construction
 Rational Software Architect (RSA)
Model Life Cycle Management
 Rational Team Concert (RTC)
Model Reuse
 Rational Asset Manager (RAM) M3
Models
RSA
RTC RAM

MDA & UML USAGE
3
3
™

MDA Usage
 Model Driven Architecture is a model-based business-focused software
architecture that calls for the development of a number of architectural models in
order to effectively describe the architecture
MDA System Model
Computation Independent Model (CIM)
Platform Independent Model (PIM)
Platform Specific Model (PSM)
CIM captures business
requirements in the language
that is familiar to the end user of
the solution and the business
domain expert
PIM specifies the solution that is
not tied to the choice of a specific
computing platform
PSM adds the details to PIM for
a specific computing platform
and specifies how that system
uses the selected platform
Models are the views of the
system from one of the three
viewpoints

UML Usage
 UML 2.3 has 14 types of diagrams
Seven diagram types represent structural information
Seven diagram types represent general types of behavior
M3 uses a subset, four structural and four behavioral diagrams
Diagram CIM PIM PSM ISM
Package    
State Machine   
Use Case  
Activity 
Class    
Sequence   
Component   
Deployment  

MODELING WORKFLOW
3
3
™

CIM: Level 1 Model
 M3 CIM captures business requirements in the language that is familiar to the end
user of the solution and the business domain experts
Use Case Model Activity ModelDomain Model
Domain Model describes the
problem domain in terms of
business concepts and reflects
a precise model of domain
vocabularies and terminologies
Use Case Model describes
functionality of a system in
terms of use cases/user
tasks/actions showing
interactions between the users
and the system
Activity Model describes
behaviors of a system in terms
of activities, actions, controls,
and data flows reflecting
organizational structures,
business processes, work flows,
and procedures

PIM: Level 2 Model
 M3 PIM specifies the solution that is not tied to the choice of a specific
computing platform; however it must comply with the system requirements
specified in the CIM
Component Model Service ModelType Model
Type Model specifies domain
objects in terms of types,
attributes, associations,
collaborations, and is used to
discover core business types
and business interfaces
Component Model specifies
the scope, responsibilities, and
supported interfaces for the
discovered components, and
the way their services are
composed to support the
system
Service Model specifies
services which provide reusable
business functionality and
includes services that are
affected by the components and
interfaces specified in the
component model

PSM: Level 3 Model
 M3 PSM specifies system implementation and design in the form of platform-
dependent model that adds details to the PIM for a specific computing platform,
and specifies how that system uses the selected platform
Runtime Model Deployment ModelData Model
Data Model represents the
structure and relationship of
data in information repositories,
and shows the persisted entities
in their corresponding domains
and the relationships amongst
persisted elements
Runtime Model illustrates the
structure of the elements that
have runtime presence such as
threads, processes, DLLs,
objects, components, etc. during
their execution and their
interactions
Deployment Model depicts
how the system is deployed to
hardware infrastructure and how
the system artifacts are
gathered in the file system
including the structure of
directories, files, etc.

M3 and Generic SDLC
M3 MDA Models
Component ModelType Model
Service Model
Platform Specific Implementation (PSI)
<<artifact>>
Script
<<artifact>>
Code
<<artifact>>
Configuration
Requirements Analysis
Specification
Architectural Design
Specification
Implementation Deployment
Specification
High Level Design Model
Construction & Assembly
Detailed Design Model
Business Requirements
Requirements Model
Test & Deployment
Implementation Artifacts

Model Ownership and Collaboration
M3 Model RSA Model Package Owner Role Collaborator Role
CIM – The Outside Activity Model
Use case Model
Domain Model
Application System Analyst Business Analyst
Project Lead Architect
PIM – The Edge Component Model
Type Model
Service Model
Project Lead Architect Domain Architect
PSM – The Inside Runtime Model
Deployment Model
Data Model
Application System Designer Project Lead Architect
Data Modeler
ISM – The Extension Business
Interface
Platform
Project Lead Architect Domain Architect

MODELING ENVIRONMENT
3
3
™

 Each M3 model is a distinct model (emx file) in RSA
 M3 model templates are managed in RAM
 M3 models are published from RSA to RAM
Modeling Environment

 RSA and RAM Integration facilitates M3 model discovery and reuse
 Models are reused by loading them from RAM to RSA workspace
 Team-based modeling using RTC Source Control Management
RSA
Create &
Refine
RAM
Publish, Discover,
& Reuse
RTC
Manage &
Collaborate

CONTEXT FOR ENTERPRISE MODELING
3
3
™

Integration Model
 M3 extends MDA viewpoints and defines an independent model, Integration
Specific Model (ISM), that has no dependencies with other three models
ISM reflects the Enterprise Integration viewpoint of the system
Models are extracted from the three M3 Models (CIM, PIM, and PSM)
 Three supported models/levels of integration are specified in ISM
Business, Interface, and Platform integration models
M3 Integration
Model
<<Integration Level>>
Interface
Platform
Business
Integration Specific
Model (ISM)
Subset of the CIM, includes
business, process, and workflow
integration models
Subset of the PIM, includes
technology independent
component and service
interfaces integration models
Subset of the PSM, includes
services, distributed objects and
components, data exchange
formats, application
programming interfaces, and
data access integration models

 The model structures and cross-model interrelationships form the basis of M3 view
aggregation
 View aggregation is achieved by assembling M3 UML packages
 The aggregated views present the information in other meaningful ways to
different stakeholders reflecting four key scopes of Enterprise Architecture
View Aggregation
Business
Architecture
Information
Architecture
Application
Architecture
Technical
Architecture
Enterprise
Architecture

View Aggregation
 Enterprise Architecture M3 UML Package Composition
Enterprise
Architecture
<<CIM>>
Activity Model
<<CIM>>
Use Case Model
<<CIM>>
Domain Model
<<PIM>>
Service Model
<<PSM>>
Data Model
<<PIM>>
Type Model
<<CIM>>
Domain Model
<<PSM>>
Runtime Model
<<PSM>>
Data Model
<<PIM>>
Component Model
<<PSM>>
Deployment Model
<<PSM>>
Deployment Model
<<PSM>>
Data Model
Business
Architecture
Information
Architecture
Application
Architecture
Technical
Architecture

SUMMARY & VISION
3
3
™

M3 Modeling Methodology Summary
RSA Model Project Templates
M3 Models
Activity Model
CIM
Use Case Model
Domain Model
Component Model
PIM
Type Model
Service Model
Runtime Model
PSM
Deployment Model
Data Model
Platform
ISM
Business
Interface
UML Diagrams Used in Models
Component Class Sequence
Deployment
Class
Use Case
Class
Activity
Class
Sequence
Package
Package & State Machine
diagrams may be used in
all models
State Machine
PIM
Diagrams
CIM
Diagrams
PSM
Diagrams
Roles & Responsibilities
Collaborator Owner
Requirements Analysis
Specification
Architectural Design
Specification
Implementation
Deployment Specification
Modeling Workflow
 Models describe the problem
domain and business
requirements
 Focus is UML behavioral
modeling
 Models specify supported
and required, interfaces,
components, and services
 Focus is UML structural and
interaction modeling
 Models describe software
implementation and
deployment for the selected
computing platform
 Focus is UML structural
modeling
Enterprise Integration
Specification
 Models are subsets of CIM,
PIM, PSM, and describe
supported levels of
integration
CIMTheOutside
Level1
PIMTheEdge
Level2
PSMTheInside
Level3
ISMTheExtension
IntegrationLevels

A complete framework for enterprise modeling, integration,
and architecture representation
M3 MDA Models
Component ModelType Model
Service Model
M3 Integration
Model
Interface
Platform
Business
Integration Specific
Model (ISM)
3
3 Modeling
Methodology
™
Enterprise
Architecture
<<EA>>
Business
<<EA>>
Information
<<EA>>
Application
<<EA>>
Technical

Streamlined Integrations offered by the
Rational tools and Jazz foundation services
Jazz Technology Platform and Services
RRCRAM RTC
RSA
M3 Models and
Asset
Management
M3 Models
Collaboration and
Source Control
Requirements
Management

A complete integrated system modeling lifecycle management

www.ibm/software/rational

WALKTHROUGH
3
3
™

Daily iPod Touch giveaway
 Complete your session surveys online each day
at a conference kiosk or on your Innovate 2011 Portal!
 Each day that you complete all of that day’s session
surveys, your name will be entered to win the daily
IPOD touch!
 On Wednesday be sure to complete your full conference evaluation
to receive your free conference t-shirt!
SPONSORED BY

© Copyright IBM Corporation 2011. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of
any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to,
nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing
the use of IBM software. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release
dates and/or capabilities referenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment
to future product or feature availability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the
International Business Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.

Innovate2011_MAC-1597A

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Viewers also liked

Viewers also liked (9)

Similar to Innovate2011_MAC-1597A

Similar to Innovate2011_MAC-1597A (20)

Innovate2011_MAC-1597A