Evolution and Integration Command Center

1
Evolution and Integration Command Center •Enable “go/no-go” decision for re-configuration tasks onitor “live” evolution of system as you would monitor network •Rapid hypothesis testing •FlexML event description •Generate verification gauges •Dynamic probing of components and connectors •Architectural Models show how to develop testing regiment for verifying that components behave as expected during dynamic system evolution, integration, and re-configuration Goal Method Technical Basis “monitor average server HTTP response time as the new database back-end engine is brought on- line” A2 D1 C22 L9 E3 Insert probes based on Architectural Mod Generate gauges e1 e2 e3 e4 e5 e6 e7 e8 e9 Expected low high “Does replacement component L9 use more disk resources than its predecessor?” FlexML Event Representation •Standard lexical syntax •Partially ordered streams rather than fixed-le •Composed/interleaved tag sets rather than rigi •Supports dynamic composition of sophisticated •Gauges as active connectors •Gaugents as feedback controllers Event Stream

description

Evolution and Integration Command Center. Enable “go/no-go” decision for re-configuration tasks Monitor “live” evolution of system as you would monitor network. “monitor average server HTTP response time as the new database back-end engine is brought on-line”. - PowerPoint PPT Presentation

Transcript of Evolution and Integration Command Center

Page 1: Evolution and Integration Command Center

Evolution and Integration Command Center

•Enable “go/no-go” decision forre-configuration tasks

•Monitor “live” evolution of systemas you would monitor network

•Enable “go/no-go” decision forre-configuration tasks

•Monitor “live” evolution of systemas you would monitor network

•Rapid hypothesis testing•FlexML event description

•Generate verification gauges•Dynamic probing of components

and connectors

•Rapid hypothesis testing•FlexML event description

•Generate verification gauges•Dynamic probing of components

and connectors

•Architectural Models showhow to develop testing regiment

for verifying that componentsbehave as expected duringdynamic system evolution,

integration, and re-configuration

•Architectural Models showhow to develop testing regiment

for verifying that componentsbehave as expected duringdynamic system evolution,

integration, and re-configuration

Go

alM

eth

od

Tec

hn

ical

Bas

is

“monitor average server HTTP response time as the new database back-end engine is brought on-line”

A2

D1

C22

L9

E3

Insert probes basedon Architectural ModelGenerate gauges

e1 e2 e3 e4 e5 e6 e7 e8 e9 …… Expected

low

high

“Does replacementcomponent L9 usemore disk resourcesthan its predecessor?”

FlexML Event Representation•Standard lexical syntax•Partially ordered streams rather than fixed-length documents•Composed/interleaved tag sets rather than rigid DTD•Supports dynamic composition of sophisticated processors•Gauges as active connectors•Gaugents as feedback controllers

Event Stream