corb-atutorial-boston2003-1199015451803822-2

8/11/2019 corb-atutorial-boston2003-1199015451803822-2

1/136

CORBA for transportation control and command systems tutorial


2/136

2

31

/03

/03

Thales Air Traffic Management

CORBA ATC use case, Note to offline reader.

! " # ! ! # "#

$% # " " ! ! & ' ( )" "# # "

% " & ! ( # #! & ! *)" "#

" ! " # ! ! %! ! ! ! "# ! ( %! #

""' # " ( (

"' " "# # " " %!#


3/136

3

31

/03

/03


The open issue :

$#

+ " " + ,

,


4/136

4

31

/03

/03


31

/03

/03

CORBA use case

Can we use CORBA in Large Distributed ControlSystem ?

What do We want !

Complex System Seamless Integration

Why CORBA ?

Object Software Bus

Design for changes

Change example : Printer

CORBA distributed polymorphism example

CORBA and Distributed Design pattern example

Procedural design versus Object design

Designing Distributed Object

Normalisation processes


5/136

5

31

/03

/03


Why CORBA ?

)" "# (" " !( ( # - "

. /

0 ! )" "# (" " # !( ( # - "

( )"


6/136

6

31

/03

/03


Practical Use Case

0 ## !

+ + #

1" + " 2( !% ,

3! !% ,

0 (,

2&


7/136

7

31

/03

/03


Complex system : ATC center

Flight PlanProcessingFlight Plan

Processing

SupervisoryControlSupervisory

Control

Simulator

Simulator

RecordingReplayRecording

Replay

controllerWorkingPosition


Radar DataProcessingRadar Data

Processing

Radar FrontProcessingRadar Front

Processing

LAN

AFTN/CIDINATFM

ADJACENTFIR'S/TWR'S

MET Centres

Voice controland

communicationsVoice control

andcommunications

Intercom Priority Public RADIO A/G



4 56


8/136

8

31

/03

/03


Object At system level ?

- " ! )" "# ( ,

! ( "" ! !

)" , !

7 ( !

# ' ! )" # (

! (


9/136

9

31

/03

/03


31

/03

/03

CORBA use case


What do We want !


Why CORBA ?

Object Software Bus

Design for changes








10/136

10

31

/03

/03


What Do We Want

& + + # "

# "#


11/136

11

31

/03

/03


++

"#

What Do We Want !

Supervision

Operator

Display

System


12/136


13/136

13

31

/03

/03


##

"#

++

What DO We Want !

Supervision

Operator

Display

System


14/136

14

31

/03

/03


We want to Increase Integrated software quality


15/136

15

31

/03

/03


31

/03

/03

CORBA use case


What do We want !


Why CORBA ?

Object Software Bus

Design for changes








16/136

16

31

/03

/03


What We expect ?

0 !

##

"#

++

Supervision

OperatorDisplay

System


17/136

17

31

/03

/03


What We expect ?

8

+#


18/136

18

31

/03

/03


What We May Have :

+(" +("

+("

+("

+(" 2


19/136

19

31

/03

/03


Spaghetti Plate Syndrome

8

"


20/136

20

31

/03

/03



+#

+ ""


21/136

21

31

/03

/03



+#

+ #


22/136

22

31

/03

/03


31

/03

/03

CORBA use case


What do We want !


Why CORBA ?

Object Software Bus

Design for changes








23/136

23

31

/03

/03


Why CORBA

0 !

( ( ! " # !

)"+! )" "

#

0 )"' " # (( " "


24/136

24

31

/03

/03


Software Component Integration Bus

Software BUS


25/136

25

31

/03

/03


ObjectSoftware Component Integration Bus

"

)"

#

99:;(

!$##Distributed

Polymorphism

Software ComponentsEvolution

And Replacement


26/136

26

31

/03

/03


31

/03

/03

CORBA use case


What do We want !


Why CORBA ?

Object Software Bus

Design for changes








27/136

27

31

/03

/03


Polymorphism

1< ' )" "# " *

( !

"

0 ! ! " =

*GoF stand for Gang of Four. It refers to the pattern seminal book of John Vlissides, Erich Gamma,Richard Helm, Ralph Johnson:

Design Patterns: Elements of Reusable Object-Oriented Software.


28/136

28

31

/03

/03



Object Software BUS


29/136

29

31

/03

/03



Object Software BUS

8!


30/136

30

31

/03

/03


Procedural versus Object

Procedural Design Object Design

Before Object After Object

CORBA use case


31/136

31

31

/03

/03


31

/03

/03

CORBA use case


What do We want !


Why CORBA ?

Object Software Bus

Design for changes








32/136

Ch S * D i D l t


33/136

33

31

/03

/03


-

"( 0 0 # 2 (

"# " "# 0

+%

0 $ B 0 "( # + ;

+ "

8


34/136

34

31

/03

/03


Object Oriented Design

# # ! " "# " ! ! "

)" #./ "-

./ "# " # "! "## "

0

" " " ! " ! "#

0

" " " ! "

Without OOD


35/136

35

31

/03

/03


Without OOD

Without OOD

Design for no Changes

Stationary System

Change management before OOD


36/136

36

31

/03

/03



#( " (

"# "

Caller called



37/136

37

31

/03

/03



0 ! " " " ( "# " " # ! " "

Caller called

No changes



38/136

38

31

/03

/03



! ' ! " " "# " " "# ! "

Caller called

Changes

Change management and code reuse before OO


39/136

39

31

/03

/03


Change management and code reuse before OO

! ' ! " " "# " " "# ! "

Caller called

System Integration is a specific change case


40/136

40

31

/03

/03


System Integration is a specific change case

+ # " "# " "# " ! "

0 ! " #

-( ! " "# "

" " "

Caller Called Caller Called


41/136

Pervasive Change


42/136

42

31

/03

/03


Pervasive Change

Replaced Module (Changed)


43/136


44/136

Pervasive Change


45/136

45

31

/03

/03


g

Several Changes Replace and Reused

Pervasive Change = Spaghetti Plate


46/136

46

31

/03

/03


g p g

+#

After Several Changes Replace and Reused

Procedural versus Object


47/136

47

31

/03

/03


Without OOD With OOD

Design For Changes

Evolutionary System

Design for no Changes

Stationary System

Change management with OO reuse


48/136

48

31

/03

/03


0 % ! " " " ! " "

Caller called

OOD

Change management with OO reuse


49/136

49

31

/03

/03


0 % ! " " " ! " "

Caller called

No changes

OOD

With OOD : Software Bus


50/136

50

31

/03

/03


CORBA use case


51/136

51

31

/03

/03


31

/03

/03

Can we use CORBA in Large Distributed Control

System ?

What do We want !


Why CORBA ?

Object Software Bus

Design for changes

Change example : Printer CORBA distributed polymorphism example


Procedural design versus Object design Designing Distributed Object


Changes example : the printer


52/136

52

31

/03

/03


Client Printing Server

From The CORBA Bible

Michi Henning

Steve Vinoski

Advanced CORBAProgramming with C++


53/136



54/136

54

31

/03

/03





55/136

55

31

/03

/03


Old Client Printing Server

New Client

Change management with OOD reuse


56/136

56

31

/03

/03


## ! "% !




57/136

57

31

/03

/03


3! "# (( ?-"%@ !"# ! " ! ! "


Change management and code reuse before OOD


58/136

58

31

/03

/03


" "#" ! ( " "#



59/136

59

31

/03

/03


# ?)"@ " ! ""# ( "

Object properties


60/136

60

31

/03

/03


?)"@ !#

2"

"

"

2&" #

" "

" ! # "#

CORBA = Distributed Polymorphism


61/136

61

31

/03

/03


)" ## "#

0 #

)" +(" .+/

CORBA use case

C CORBA i L Di t ib t d C t l


62/136

62

31

/03

/03


31

/03

/03


System ? What do We want !


Why CORBA ? Object Software Bus

Design for changes





CORBA Distributed Polymorphism examples


63/136

63

31

/03

/03


2&

! + 8# ("

2& C

# + $ " " " .1/

2& D

#

Example UML Diagram


64/136

64

31

/03

/03


Strip

Strip : string

Print()

Strip : string

Print()

Printer

Print()Print()

Print

1

ColorPrinter

Setcolor()Setcolor()

From The CORBA Bible

Michi HenningSteve Vinoski

Advanced CORBA

Programming with C++


65/136


66/136

printer


67/136

67

31

/03

/03


Printer

print()

CORBA Distributed Polymorphism example 1


68/136

68

31

/03

/03


0

-&

8#+("

Printer



69/136

69

31

/03

/03


?# ("@ " "

# (" # #" ""

8# +(" ( ! "#! " # ("

Objet Reference and Naming


70/136

70

31

/03

/03


Client NamingService Server

Server exports

IOR

Client lookupfor Interface IOR

Client submits

request to server



71/136

71

31

/03

/03


%

! ( " "#

"

8! " " ! "! " "



72/136

72

31

/03

/03


0

-&

8#+("

ColorPrinter

Printer

+" ! "#

"% 0

CORBA Distributed Polymorphism


73/136

73

31

/03

/03


0

-&

8#+("

ColorPrinter

Printer+" ! "#

printer


74/136

74

31

/03

/03


Printer

print()

Colour

set_color()

CORBA use case



75/136

75

31

/03

/03


31

/03

/03




Design for changes





We need design patterns


76/136

76

31

/03

/03


0 ( # " "- #

# " " !" "# ! " "

! %! )" ##

Distributed Pattern


77/136

77

31

/03

/03


# # .1/ )" +

# )" +! #!"

( "# " 2&" !" " ")"

! +

& ! "

+" & # ! "

& # !

The GOF Abstract Factory Design Pattern


78/136

78

31

/03

/03


*GoF stand for Gang of Four. It refers to the famous books of John Vlissides, Erich Gamma, Richard Helm,Ralph Johnson. Design Patterns: Elements of Reusable Object-Oriented Software.

Polymorphism and Factory Pattern : example 2


79/136

79

31

/03

/03


"

Life cycle


80/136

80

31

/03

/03


Printer FactoryClient Printer

Create Printer

Create Printer

Request

Printer IOR

FACTOY PATTERN (from OOC training)


81/136

81

31

/03

/03


" " ! ( ' "# !#

+"

A client is required to provide security information before thefactory object will allow the client to have access to anotherobject.

$*"#

The factory object manages a pool of objects, oftenrepresenting some limited resource, and assigns them toclients based on some utilization algorithm.

A factory object enables the use of polymorphism by returningobject references to different implementations depending onthe criteria specified by a client.

Polymorphism and Factory Pattern


82/136

82

31

/03

/03


"

Polymorphism and Factory Pattern


83/136

83

31

/03

/03


"

Factory And Code Generation


84/136

84

31

/03

/03


Printer

+print()

Black & White

+ print()



85/136

85

31

/03

/03


Printer

+print()

Black & White

+ print()

Colour

+ print()



86/136

86

31

/03

/03


Printer

+print()

Black & White

+ print()

Colour

+ print()

FAX

+ print()



87/136

87

31

/03

/03


Printer

+print()

Black & White

+ print()

Colour

+ print()

FAX

+ print()

Strip

+ print()


I t f


88/136

88

31

/03

/03


Printer

+print()

Black & White

+ print()

Colour

+ print()

FAX

+ print()

Strip

+ print()


89/136

CORBA use case


S t m ?


90/136

90

31

/03

/03


31

/03

/03




Design for changes








91/136

Why is OOD easy to change ?

)


92/136

92

31

/03

/03


" )" #" "

2" )"

"# )"

)"

""

Object collaboration


93/136

93

31

/03

/03


Why is OOD easy to change ?

+ ! "#


94/136

94

31

/03

/03


+ ! "# ! )" "# !

" " )" "#

"# "# ?@

Example 3: The problem is in the User Input


95/136

95

31

/03

/03


Exit Coordination State

A: NIL_EXIT_STATE,

B: FLIGHT_ACTIVATION_PROPOSAL,

C: FLIGHT_ACTIVATION_ALARM,

D: FLIGHT_ACTIVATION_CONFIRMED,

E: HANDOVER_TRANSFERED,F: COORDINATION_TERMINATED,

G: UNKNOWN_EXIT_STATE

Enter Exit Coordination State =>

Replace case and enum by object .


96/136

96

31

/03

/03


enum ExitCoordinationState {

NIL_EXIT_STATE,

FLIGHT_ACTIVATION_PROPOSAL,FLIGHT_ACTIVATION_ALARM,

FLIGHT_ACTIVATION_CONFIRMED,

HANDOVER_TRANSFERED,

COORDINATION_TERMINATED,

UNKNOWN_EXIT_STATE

}

Example of structural fragility : the switch

+" +!" "#


97/136

97

31

/03

/03


+" +!" "#2( "# "# "

"# ! !"

" " !"

# % "# "E

2(! ( " ""# (' ( !" ""# (

0 ( "# (

"# (! !" "

structural switch


98/136

98

31

/03

/03


static void printsStatus(int status) {

switch(status) {

case NIL_EXIT_STATE :

processing 1case FLIGHT_ACTIVATION_PROPOSAL:

processing 2case FLIGHT_ACTIVATION_ALARM:

processing 3case FLIGHT_ACTIVATION_CONFIRMED:

processing 4case HANDOVER_TRANSFERED,processing 5

case COORDINATION_TERMINATED,processing 6

caseUNKNOWN_EXIT_STATEprocessing 7

}}


99/136


100/136

The problem space and the solution space.

!" ( " &


101/136

101

31

/03

/03


!" ( " &

0 - ! " ( "#(! !" (

User Imput


102/136

102

31

/03

/03


Exit Coordination State

A: NIL_EXIT_STATE,

B: FLIGHT_ACTIVATION_PROPOSAL,

C: FLIGHT_ACTIVATION_ALARM,

D: FLIGHT_ACTIVATION_CONFIRMED,

E: HANDOVER_TRANSFERED,

F: COORDINATION_TERMINATED,

G: NewState

H: UNKNOWN_EXIT_STATE

Enter Exit Coordination State =>

Replace case and enum by object .

enum ExitCoordinationState {


103/136

103

31

/03

/03


NIL_EXIT_STATE,

FLIGHT_ACTIVATION_PROPOSAL,

FLIGHT_ACTIVATION_ALARM,FLIGHT_ACTIVATION_CONFIRMED,

HANDOVER_TRANSFERED,

COORDINATION_TERMINATED,

NewState,

UNKNOWN_EXIT_STATE

}

static void printsStatus(int status) {

switch(status) {

structural switch


104/136

104

31

/03

/03


case NIL_EXIT_STATE :

processing 1case FLIGHT_ACTIVATION_PROPOSAL:

processing 2case FLIGHT_ACTIVATION_ALARM:processing 3

case FLIGHT_ACTIVATION_CONFIRMED:

processing 4case HANDOVER_TRANSFERED,

processing 5case COORDINATION_TERMINATED,

processing 6case New_State,

processing 7

caseUNKNOWN_EXIT_STATEprocessing 8

}}


105/136

OOD hides the problem space

0 % "# " " )"


106/136

106

31

/03

/03


# )"

3! 0

0

3!

Polymorphism

StatusPrint()

Client


107/136

107

31

/03

/03


+print()

NIL_EXIT

_STATE

+ print()

FLIGHT_ACTIVATION

_PROPOSAL

+ print()

FLIGHT_ACTIVATION

_ALARM

+ print()

UNKNOWN_EXI

T_STATE

+ print()

Factory Pattern

Status


108/136

108

31

/03

/03


+print()

NIL_EXIT

_STATE

+ print()

FLIGHT_ACTIVATION

_PROPOSAL

+ print()

FLIGHT_ACTIVATION

_ALARM

+ print()

UNKNOWN_EXIT

_STATE

+ print()

StatusFactory

+ create()

Factory Pattern

!" ! )" "


109/136

109

31

/03

/03


" ! )" # (" # !" " # "

" ! " )" +

2" )" %! ! # "(" "

Factory pseudo code

static Status create(int status) {

switch(status) { New Object


110/136

110

31

/03

/03


case NIL_EXIT_STATE :return status = new nil_exit_state();

break;

case FLIGHT_ACTIVATION_PROPOSAL:

return status = new flight_activation_proposal();break;

case FLIGHT_ACTIVATION_ALARM:return status = new flight_activation_alarm();

break;

case FLIGHT_ACTIVATION_CONFIRMED:

return status = new flight_activation_confirmed();

break;

case HANDOVER_TRANSFERED,return status = new handover_transfered();

break;

case COORDINATION_TERMINATED,return status = new coordination_terminated();

break;

caseUNKNOWN_EXIT_STATEreturn status = new unknown_exit_state();

}}

Polymorphism and changes

Status


111/136

111

31

/03

/03


+print()

NIL_EXIT

_STATE

+ print()

FLIGHT_ACTIVATION

_PROPOSAL

+ print()

FLIGHT_ACTIVATION

_ALARM

+ print()

UNKNOWN_EXIT

_STATE

+ print()

NEW_STATE

+ print()

No Changes

Polymorphism and state patterns

! ( )" !" " "## ! (


112/136

112

31

/03

/03


""# )" !

+( !" ( )" "##

+" )" " "("

State Pattern (from the GoF)


113/136

113

31

/03

/03


GoF stand for Gang of Four. It refers to the famous books of Vlisside and Co.Design Patterns: Elements of Reusable Object-Oriented Software.

Object Programming

Stat1


114/136

114

31

/03

/03


State2

Stat1

State4

+ #

State5

2&+ F

G

State Pattern

"& )" "!" )"


115/136

115

31

/03

/03


)" & ' # " %! ! # ' ! " " ("


116/136

Polymorphism

Context


117/136

117

31

/03

/03


status

+print()

NIL_EXIT

_STATE

+ print()

FLIGHT_ACTIVATION

_PROPOSAL

+ print()

FLIGHT_ACTIVATION

_ALARM

+ print()

UNKNOWN_EXIT

_STATE

+ print()

Status

+print()

Concrete state

Coarse Grain Examples

& ( ' " " # " "


118/136

118

31

/03

/03


"' # ( )" #

& " # &

+ ! )" " # )"

On line coordination with CORBA Objects


119/136

119

31

/03

/03


Air Traffic Control Centre

Status

Status

Status

Status

CORBA use case




120/136

120

31

/03

/03


31

/03

/03


Why CORBA ?

Object Software Bus

Design for changes







CORBA = Coarse Grain Object

Remote ObjectLocal Object

Operation1() NO


121/136

121

31

/03

/03


p

Operation2()

Operation3()

Operation4()

Fine Grain Object

CORBA = Coarse Grain Object

Remote ObjectLocal Object

GroupOperation()

YES


122/136

122

31

/03

/03


YES

Distributed Object Patterns

FaadeLocal Object Remote Object

GetRemoteObject()


123/136

123

31

/03

/03


Operation1()

Operation2()

Operation3()

H $" "

Object By Value

Local Object Remote Object

OBV

Event Factory

$" )"


124/136

124

31

/03

/03


Operation1()

Operation2()

Operation3()

new

Event Type

CORBA use case


What do We want !

C l S S l I i


125/136

125

31

/03

/03


31

/03

/03


Why CORBA ?

Object Software Bus

Design for changes







Separation Of Concern


126/136

126

31

/03

/03


Fault

Tolerance

Printer

Load

Balancing

Printer

Transaction

Printer

Security

Printer


" " !(# " "" "


127/136

127

31

/03

/03


" )"

)"

" )"

" )"

" " ! "" )"

"



128/136

128

31

/03

/03


SecurityLoad

Balancing

Printer

TransactionFault

Tolerance


Security Load

B l iTransaction

Fault

Tolerance


129/136

129

31

/03

/03


Balancing

Printer


SecurityLoad

Balancing

Printer TransactionFault

Tolerance


130/136

130

31

/03

/03


Balancing

DomainServices

TechnicalServices

Y development cycle


131/136

131

31

/03

/03


"$ "#""

1" !

!


132/136

"

"$#"

Application Lay out


133/136

133

31

/03

/03


"$#"

"-

$#"

" "-

Application Lay out

" $#""""


134/136

134

31

/03

/03


" "-""""

Y Standardization Process

" " "# ! #


135/136

135

31

/03

/03


"" ( #" ! "

""

""

0 ( ! "% ( A

"

Y Standardization Process

Domain Logic Domain Technical


136/136

136

31

/03

/03


Domain LogicPatterns

Domain TechnicalPatterns

Transportation DTF

Documents

corb-atutorial-boston2003-1199015451803822-2