Date post: | 18-Dec-2015 |
Category: |
Documents |
View: | 215 times |
Download: | 3 times |
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 1
UML 2: Component model & RTfeedback of AIT-WOODDES project
to the U2 proposal
Workshop SIVOES-MONA – UML’2002, Dresden
Pr. Francois Terrier & Dr. Sébastien Gérard
CEA – LIST / L-LSP(Francois.Terrier, Sebastien.Gerard)@cea.fr
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 2
Plan of the presentation
The AIT-WOODDES project outlines
"Component model" of the U2 group
ACCORD/UML RT- Component Model
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 3
The project partners
End-Users Academics EditorsEditors
PRIME
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 4
ValidationDevelopment
The AIT-WOODDES platformThe AIT-WOODDES platform
RhapsodyRhapsody
XMIXMI
ModelCheckerModelChecker
Internal exchange
format
UPPAALUPPAALModel
exchange via XMLRoseRose
XMI
XMI
Internal exchange
formatAgathaAgatha
ObjecteeringObjecteering
AccordAccord
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 5
Case study of PSA-MECEL
Routing system GPS
GSM/GPRS/UMTS
InternetService provider
Evaluate project results on:Methodology
RT Profile adequation
Tools efficiency
Model exchange
Code generation
Validation capabilities
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 6
The UML 2.0 component concept
It supports the specification of both• "logical" components
(e.g. business components, process components)
• "physical" components UML 1.4
(e.g. EJB components, CORBA components,
COM+ and .NET components)
A component is modeled throughout the
development life cycle and successively
refined into deployment and run-time
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 7
A two-views component model
A component has an external view(or. “black-box” view)by means of its publicly visible properties• Protocol state machine attached to ports/interfaces
may define the external view more preciselyby making dynamic constraints in the sequenceof operation calls explicit
A component also has an internal view(or “white-box” view) by means of its private properties which are its internal classifiers and how they are connected.
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 8
Today, in U2 proposal, 2 possible models
a component has Ports typed by Interface• components communicated together via messages going through
their ports (like processes in SDL or capsules of "ROOM" model)
still under construction … … and should be completely revisited in incoming version !
a component has directly Interfaces(required and provided)• components communicating also via messages but in this case,
messages go through the interfaces themselves (like usual component model, e.g. CCM-CORBA Component Model, ... )
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 9
user
!+
Structure of the ACCORD/UML Methodology
ACCORD/UMLMethodology
relizes
Modelling tools
defined by
ACCORD/UML Profile
OMG’ Standard profiles !!!
SPE profileSPT profile AL profile
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 10
Details of ACCORD/UML models
Analysis Model
Model
Structural Model
B A
C
Detailed Scenarios
Behavioural Model
interView 1
structView 1
behavView 1
Detailed Analysis
Model
Preliminary AnalysisModel
High-Level Scenarios Models Dictionary
theSystem
Use Cases Model
theSystem
theSystem Possible Scénario
1..*
ucDiag
1
dico
1
Use Case
Actor
envElt
*
1
Use Case Diagram
describedBy * envElt
*
Class
RT_QoS
RT_QoS
RT_QoS
RT_QoS
RT_QoS
RT_QoS
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 11
Decomposition heuristics & component model
Initial Model
Initial Model
ACCORD/UML
(PAM ou DAM)
ACCORD/UML
(PAM ou DAM)
Sub-system Model
Sub-Syst_1 Sub-Syst_2
Sub-Syst_3
«refine»
ER1C_Sub-Syst_1
C_Sub-Syst_2
C_Sub-Syst_3
Component Model
«parts»
ER2
ER1 = Heuristics to ease decomposition of a system into a sub-systems model
ER1 = Heuristics to ease decomposition of a system into a sub-systems model
ER2 = Model mappings to transform resulting sub-systems model into component model
- required & offered interface- component connexions / association links- …
ER2 = Model mappings to transform resulting sub-systems model into component model
- required & offered interface- component connexions / association links- …
Component definition 2 possible views:
-“Black box” (= external view) set of interfaces
-“White box” (= internal view) sub-system
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 12
Component
• ACCORD/UML component Model based onUML2 component Model + RT_QoS
The ACCORD/UML RT-Component Model
Interface
provided
required
Interface can have both BehavioralFeatures:• operations also with QoS specif.• receptions (signals) with QoS specif.
BehavioralFeatures RT_QoS
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 13
Model transformation:sub-system identification / component defintion
-“White box” = internal view
-“Black box” = external view
-“White box” = internal view
-“Black box” = external view
C_Sub-Syst_1
Sub-Syst_1
SC_Manager
Regulator
SpeedSensor
getSpeed( )
SpeedRegulator Speedometer
<<DetailledContent>><<DetailledContent>>
SpeedRegulator Speedometer
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 14
UML specialisation for components
RT_QoS
RT_QoS
RT_QoS
C_Sub-Syst_1
C_Sub-Syst_2
C_Sub-Syst_3
Component Model
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 15
Qos & components: on behavioral features
UML Profile for QoS…Required QoS Offered QoS
« rPriority »
{priorValue 5}
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 16
The ACCORD/UML RT-Component Model
based on a MDA approach…
ER3 = Mappings definition from the RT-Component Model of ACCORD/UML towards a platform model (e.g., RT-CCM model)
PIM-to-PSM
CCM
ER
3RT_QoS
RT_QoS
RT_QoS
C_Sub-Syst_1
C_Sub-Syst_2
C_Sub-Syst_3
Component Model
ER2
RT_QoS
RT_QoSSub-system Model
Sub-Syst_1 Sub-Syst_2
Sub-Syst_3
RT_QoS
RT_QoS
ER2 = These mappings take into account specified RT features of the sub-system model PIM-to-PIMER2 = These mappings take into account specified RT features of the sub-system model PIM-to-PIM
SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 17
ACCORD/UML: A full MDA Approach
PIM
level
PSM level
Régulateur Afficheur
Capteur
PrM
Régulateur Afficheur
Capteur
DAM
Runnable level
DicoXxxxxxxx
PAM
DicoXxxxxxxx
Valid.
Modeling rules
Modeling concepts
Model enrichment
Modeltranslation filterModel enrichment
mapping
OS Interf. modelCode generation