model runway, part 3 design best practices at blue cross blueshield

1

Good Design is Good Business Series (developerWorks)

“Model Runway: Part 3” Design Best Practices at BlueCross BlueShield Guest Speaker: Arman AtashiSenior Application ArchitectBlueCross BlueShield of North Carolinaarman.atashi@bcbsnc.com

Host: Roger Snook IBM, Rational softwareWorldWide Enablement Leader, Mobile, Design, Agile, SOA +1.703.943.1170, RCSnook@us.ibm.com2013 January 25 http://ibm.co/MEABT1

2

Agenda

• BRIEF Session 1, 2 Recap• M3 & TOGAF

– Synergy– Concept Mapping– RSA Template

• M3 Webstore Architecture Specification– Business Architecture– Information Architecture– Application Architecture

• Framework Summary

3

Application - Description • Problem Statement

– A hosted eCommerce solution that provides product owners the tools they need to build an online business and sell their products online

• Functional Requirements– System must allow customers to manage their product inventory– Customers make online purchases and products are delivered to the desired destination– System can only be accessed by authorized users – System must maintain information about products, customers, billing/shipping, & orders

• M3 Webstore M3 Models– CIM

• Domain Model• Use Case Model

– PIM• Type Model• Component Model

– PSM• Runtime Model

4

Application – M3 Workflows

5

Application - Framework Components

Modeling Workflow

Integration Model

View Aggregation

Modeling Notation

Modeling Environment

™

MDA Principles and Disciplines Context for Enterprise ModelingContext for Enterprise Modeling

M3 Framework

Components

6

Agenda

• Session 2 Recap• M3 & TOGAF

– Synergy– Concept Mapping– RSA Template

• M3 Webstore Architecture Specification– Business Architecture– Information Architecture– Application Architecture

• Framework Summary

7

Synergy TOGAF (The Open Group Architecture Framework) is a framework for developing

an enterprise architecture

TOGAF supports four architecture domains; Business, Data, Application, and Technology

TOGAF ADM (Architecture Development Method) is a process for developing architectures and identifies eight phases/cycles

8

Synergy M3 and TOGAF ADM complement each other in key areas

The resources (models/views and framework) can be mapped to produce different types of architecture describing an overall Enterprise Architecture

M3 models and views map on to the first four phases of ADM; A, B, C, and D

9

Concept Mapping M3 View Aggregation M3 UML package compositions constitute a generic model for enterprise

architecture domains 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

10

Concept Mapping Enterprise Architecture Domains

ArchitectureVision

Business Architecture

Information Systems Architectures

Applications Architecture

Technology Architecture

TOGAF Enterprise Architecture

Segment Architecture(s)

Opportunities and Solutions

Strategic ArchitectureCapability Architecture(s)

Data Architecture

M3 Generic Enterprise Architecture Domains

11

Concept Mapping M3 Models & TOGAF ADM• Architecture Vision

– Defines relevant stakeholders, key business requirements and the scope of architecture, and demonstrates how the vision responds to the requirements

– Includes high-level M3 CIM and PIM Models

• Business Architecture– Defines key business processes, business requirements ,and service strategy– Includes M3 CIM Models

• Information Systems Architectures (Applications and Data)– Provides the blueprint for deployed systems showing their interactions and describes the

structure of logical and physical data resources– Includes M3 PIM and PSM Models

• Technology Architecture– Describes software and hardware infrastructure required to support the deployed

application(s)– Includes M3 PSM Models

12

Concept Mapping Reference Guide

TOGAF Enterprise Architecture

CIM PIM PSM Reference Architecture

Architecture Vision Use Case Model[high-level]

Component Model[high-level]

Business Context

Business Architecture Domain ModelActivity Model

Use Case Model

Service Model Domain Interaction Context

Information System ArchitectureApplications Architecture

Component ModelService Model

Run Time Model Implementation Context

Information System ArchitectureData Architecture

Domain Model Type Model Data Model Entity Context

Technology Architecture Run Time ModelDeployment Model

Technical Context

13

RSA Template Model Composition Similar to the other M3 RSA templates, M3 TOGAF is a distinct model (emx file) in

RSA

It consists of five UML packages reflecting the first four phases of TOGAF ADM

14

RSA Template Model Navigation

Each M3 TOGAF UML package includes a TOGAF right navigation bar

Information Systems Architecture is further divided into its perspective domains

Requirements Management may be linked to the requirements repository and/or documents

15

Agenda

• Session 2 Recap• M3 & TOGAF

– Synergy– Concept Mapping– RSA Template

• M3 Webstore Architecture Specification– Business Architecture– Information Architecture– Application Architecture

• Framework Summary

16

Business & System ActorsSource: M3 CIM Use Case Model

17

System ContextSource: M3 CIM Use Case Model

18

Key Use Cases Source: M3 CIM Use Case Model

19

Buyer Use Case Diagram Source: M3 CIM Use Case Model

20

Domain ModelSource: M3 CIM Domain Model

21

Type ModelSource: M3 PIM Type Model

22

Service Interfaces and OperationsSource: M3 PIM Component Model

23

Data Access ComponentsSource: M3 PIM Component Model

24

Service Components – External ViewSource: M3 PIM Component Model

25

Service Components – Internal ViewSource: M3 PIM Component Model

26

Deployment Module DependenciesSource: M3 PSM Runtime Model

27

Server ArchitectureSource: M3 PSM Runtime Model

28

Agenda

• Session 2 Recap• M3 & TOGAF

– Synergy– Concept Mapping– RSA Template

• M3 Webstore Architecture Specification– Business Architecture– Information Architecture– Application Architecture

• Framework Summary

29

Methodology SummaryRSA Model Project RSA Model Project

Templates 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 UML Diagrams Used in ModelsModels

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

PIM Diagrams

CIM Diagrams

CIM Diagrams

PSM Diagrams

PSM Diagrams

Roles & Roles & ResponsibilitiesResponsibilities

Collaborator OwnerRequirements Analysis Specification

Requirements Analysis Specification

Architectural Design Specification

Architectural Design Specification

Implementation Deployment Specification

Implementation Deployment Specification

Modeling Modeling WorkflowWorkflow

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

Enterprise Integration Specification

Models are subsets of CIM, PIM, PSM, and describe supported levels of integration

CIM

T

he

Ou

tsid

e L

eve

l 1

CIM

T

he

Ou

tsid

e L

eve

l 1

PIM

T

he

Ed

ge

L

eve

l 2

PIM

T

he

Ed

ge

L

eve

l 2

PS

M

Th

e I

ns

ide

L

eve

l 3

PS

M

Th

e I

ns

ide

L

eve

l 3

ISM

T

he

Ex

ten

sio

n

Inte

gra

tio

n L

ev

els

ISM

T

he

Ex

ten

sio

n

Inte

gra

tio

n L

ev

els

30

A complete framework for enterprise modeling, integration, and architecture representation

M3 MDA Models

Computation Independent Model (CIM)

Platform Independent Model (PIM)

Service Model

Platform Specific Model (PSM)

M3 Integration Model

<<Integration Level>>Business

Integration Specific Model (ISM)

3ModelingMethodolog

y

™

Enterprise Architecture

<<EA>>Business

<<EA>>Information

<<EA>>Application

<<EA>>Technical

3131

Good Design is Good Business (developerWorks) http://ibm.co/MEABT1

Thank You,

UPCOMING Webcasts Presenter DateTime (ET USA)

Good Design is Good Business: The Big Picture Roger Snook 2/7 12:15-1:15PM

Good Design is Good Business: IBM and Design Karel Vredenburg 3/7 12:15-1:15PM

Good Design is Good Business: SOA - Still Going Strong Claus Jensen, Roger Snook 4/4 12:15-1:15PM

Good Design is Good Business: Design Management: Pictures are Worth…. Jean-Louis Marechaux 5/2 12:15-1:15PM

Good Design is Good Business: DevOps: Deliver your production code faster Maneesh Goyal 6/13 12:15-1:15PM

Good Design is Good Business: Mobile and Smartphone Apps Roger Snook 7/11 12:15-1:15PM

Good Design is Good Business: Rational Software Architect Roger Snook 8/8 12:15-1:15PM

Good Design is Good Business: Industry Models Accelerate Software Nick Norris, Roger Snook 9/12 12:15-1:15PM

Good Design is Good Business: Business Design: SA and RSA Roger Snook, Steve Arnold 9/19 12:15-1:15PM

Good Design is Good Business: Smarter Devices through MDD for realitime/embedded development Manohar Rao 10/4 12:15-1:15PM

Good Design is Good Business: SysML & Industry Standards Irv Badr 11/14 12:15-1:15PM

Good Design is Good Business: Rational Rhapsody Manohar Rao 12/5 12:15-1:15PM