Background scenario drivers and critical issues with a focus on technology trends, and systems architecture

Background - Scenario Drivers and Critical Issues with a Focus on Technology Trends,

and Systems Architecture Near-Shore-Development Seminar

Barry Demchak May 19, 2009

Introduction and Projects

https://sosa.ucsd.edu/

S3EL and SAINT group at CalIT2 (UCSD)

Introduction and Projects

A Scary Number

14,000

• Supply Side– Computation– Bandwidth– Storage– Display

• Demand Side– Corporate/Scientific– Personal Business– Personal Mobile

Supply and Demand

Supply Side

• Computation– Speed (Intel 4004: .092 MIPs → Core2: 23 MIPs),

pipelining, hyperthreading, RISC/CICS, memory speeds

• Bandwidth– Speed (110 baud acoustical modem → frame relay

→ T1 → OC192 → 10Gbps Ethernet)• Storage

– Hard Disk (5MB → 1TB), Solid State• Display

– .0192Mp B/W → 4Mp Color, 6ms transitions

Demand Side• Corporate/Scientific

– Large, fixed investment; Narrow stakeholder set; Infrequent, costly deliveries; Processing: batch → real-time; Process: Waterfall

• Personal (Fat Client)– Costly software, commodity hardware; Infrequent,

cheaper deliveries; Processing: real-time; Process: Waterfall→Agile

• Personal (Thin Client)– Cheap software & hardware; Frequent, cheap

deliveries; Real-time; Process: Agile• Mobile and Embedded

– Cheap software & hardware; Infrequent, costly deliveries; Real-time; Process: Waterfall, Agile

Consequences• Complexity is Increasing

– MS-DOS OS (1985: 500K lines of code) -> Win2K (2000: 43M lines of code)

– Failure is likely– Collaboration between users is important– Collaboration between systems is important– Boundary between users and systems is blurring– ORGANIC COMPLEXITY

• Agile Development– Shorter development/release cycles– Developers closer (embedded) to customer– Risk calculation: Time to market and reactivity is most

important– Multiple imperfect substitutes negate first mover advantage– Barriers to entry still apply

Where is this Going?• Distributed Systems

– Storage placement– Computing placement– Distributed state

• Open Source Software– Commodity features, developers, development

environments, requirements management• Diverse Stakeholder Populations

– Mass customization– Information Assurance

• Communities– Cyberinfrastructures

Where is this Going?

• Loose Coupling• Late Binding• Scalability• Composition• Interoperability• Testability

Producer Database

OK

StoreData(xxx)

Tim

e

Roles and Interactions

Producer Database

Message Bus

Sto

reD

ata(

xxx)

OK

Network Implementation

Single Server, Multiple Processes

Single Application, Linked Modules

Logical Deployment

• Malleability• Manageability• Dependability• Incremental development

Service Oriented Architectures and Processes

Rich Services Architectural Pattern

Messenger

Router/Interceptor

Policy

Ser

vice

/Dat

aC

onne

ctor

Messenger

Router/Interceptor

Failure Manager

...

<<Rich Service>> S

Ser

vice

/Dat

aC

onne

ctor

...

<<Rich Service>> S.n

Service/DataConnector }<<

Rich Infrastructure

Services>>

EncryptionService/Data

Connector

LoggingService/Data

Connector

Failure Manager

Service/DataConnector

...


S.1


S.2


}<<

Rich Application Services

>>

S.n.2


S.n.m


}

<<Rich

Application Services

>>

S.n.1



Logging


Encryption


Policy ...



<<Rich

Infrastructure Services

>>}

From tightly to l o o s e l y coupled systems

a hierarchically decomposed structure supporting“horizontal” and “vertical” service integration

Rich Service Process

Rich Services Virtual Network

Rich Services

RAS4

Services

Service S 1

Roles

U1

U2

U3

U4

U5

Use Case Graph

ConcernsC1 C2 C3

C4CC1

CC2CC3

Domain Model

R1 R2

R3 R4

R5 R6

R1 R2

msg

R3

CC1CC2

Role Domain Model

R1 R2

R3 R4

R5 R6

CC1 CC2 CC3

Router/ Interceptor

Messenger /Communicator

RAS1 RAS2

CC1 CC4 CC5

Router /Interceptor

Messenger / Communicator

RAS5 RAS6RAS 3

S/D

S/D

RIS :

RIS:

Serv

ice

Elic

itat

ion

Ric

h S

ervi

ce A

rchi

tect

ure

RAS7

System of Systems Topology

H1 H2

H3

H5

H6

H7

H8

H9H4

RAS1 RAS 2 RAS3

RAS5 RAS6 RAS7

Infrastructure Mapping

H1:RAS1 H2:RAS2

H3:CC1

H5:RAS2

H6:RAS5

H7:RAS7H8:RAS7

H9:RAS6

H4:RAS3

Opt

imiz

atio

n

ImplementationRAS1 RAS 2

RAS3 RAS 4

RAS5 RAS 6

RAS7 CC1

CC2 CC3

CC4 CC5

Ana

lysis

Syn

thes

is

Ana

lysis

Iden

tific

atio

n

Def

initi

on

Con

solid

atio

n

Refinement

Hierarchic composition

Refinement

Logical Model

Syst

em A

rchi

tect

ure

Defin

ition

Logical Architecture Loop

Deployment Loop

Logical Architecture (PALMS)

Event Logger Access Policies

PALMS Integration System

Integration Adapter

Data Repository

HIPAA Policies

Service/ Data

ConnectorViewerViewer

Adapter

Consumer Systems

Service/ Data

ConnectorSensor AdapterSensor

Producer Systems

Subject Repository

Service/ Data

ConnectorAuthoringCalculation

Repository

Calculation Systems

ExecutionPrototyping

Failure Detection/Mitigation

Roles• Web 2.0

– Content, Contribution, and Community– Application authorship (e.g., Facebook, MySpace, Google Maps)– Data fusion (e.g., Mashups, Yahoo Pipes)

• Utility Providers (Platform as a Service)– Amazon S-3, Google clouds – resource-oriented– Microsoft Windows Azure Cloud – middleware-oriented– Private Clouds – trades on-demand and privacy

• Software Providers (Software as a Service)– Google Apps – Internet delivery model w/integration– Sales.com, Salesforce.com – Parametric solutions (ASPs)

• Communities– Facebook, MySpace, Wikis, Blogs– Research (CABig, PALMS)– Virtual Organizations

Crosscutting Roles

• Developers– Requirements elicitation and analysis– Architects and designers– Coders

• Infrastructure (Hardware)– Provisioners– Builders and maintainers

• Infrastructure (Software)– Policy definition and maintenance– Governance specialists– Security specialists

• Management– …

Questions

Notes

Notes leading to presentation