Docstoc

UML2ComponentModel-RTQoS-CEA-LIST

Document Sample
UML2ComponentModel-RTQoS-CEA-LIST Powered By Docstoc
					    UML 2: Component model & RT
     feedback 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)   1
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)   2
The project partners

   End-Users                        Academics                                Editors
    PRIME




      SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP)   3
 The AIT-WOODDES platform
             Development                                                  Validation

                   Objecteering                          Internal
                                                        exchange
             Accord                                       format
                                                                                Agatha

       XMI




                                                         Model
Rose                                                   exchange
                                                                                UPPAAL
                                                        via XML
                                 XMI


       XMI
                                                          Internal
                                                         exchange
                                                           format
                           Rhapsody                                         ModelChecker



               SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP)   4
  Case study of PSA-MECEL

       GSM/GPRS/UMTS
                                                            Routing system
GPS
                                      Evaluate project results on:
                                                                           Methodology
                                                           RT Profile adequation
                   Internet
                              Service provider
                                                                       Tools efficiency
                                                                     Model exchange
                                                                    Code generation
                                                           Validation capabilities




       SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP)   5
The UML 2.0 component concept


 A component is modeled throughout the
  development life cycle and successively
  refined into deployment and run-time

 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)



         SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP)   6
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 precisely
    by making dynamic constraints in the sequence
    of 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)   7
  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)


  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, ... )

 still under construction …
                 … and should be completely
                 revisited in incoming version !
            SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP)   8
     Structure of the ACCORD/UML Methodology

                                                              OMG’ Standard
                                                                profiles !!!



SPT profile   AL profile   SPE profile
                                                                                                     !
                                                              ACCORD/UML
                                                              Methodology
                                     defined by

                                        relizes
                                                                     +
                                                                                                     user
       ACCORD/UML Profile


                                                            Modelling tools




                   SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP)          9
            Details of ACCORD/UML models
                                                                                                                  theSystem
                                                                                                                              1
                                                                                                                                  Class
                                                theSystem
                                                                                        Use Case                    envElt
                                 ucDiag                              describedBy                                                          RT_QoS
                                                                               *        Diagr am                              * Actor
                                      1
                                           Use Cases Model                                                            envElt
                                                                                                                          * Use CaseRT_QoS

                                                                                                     RT_QoS
                                                                                             theSystem
                                           dico                                                           Possible Scénario
            Preliminary Analysis
                                            1                                                             1..*
                         Model
                                                  Dictionary
                                                                                    High-Level Scenarios Models


                                                                                         RT_QoS
                                                  interView
Analysis Model                                                 1
                                                               Detailed Scenarios Model

                                                                        A       B
                                                                                               RT_QoS
                                                structView
                                                               1                C




                 Detailed Analysis                                 Structural Model
                      Model
                                             behavView                                    RT_QoS
                                                               1

                                                               Behavioural          Model


                              SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP)                                      10
               Decomposition heuristics & component model

                           Sub-system Model                             ER2       Component Model

                ER1                                                     «parts»      C_Sub-Syst_1             C_Sub-Syst_3
                             Sub-Syst_1                    Sub-Syst_2
  Initial       «refine»
  Model
ACCORD/UML                                                                           C_Sub-Syst_2
                                              Sub-Syst_3
(PAM ou DAM)




 ER1 = Heuristics to ease decomposition of                                    Component definition
 a system into a sub-systems model                                                   2 possible views:
                                                                              -“Black box” (= external view)
 ER2 = Model mappings to transform resulting                                      set of interfaces
 sub-systems model into component model
                                                                              -“White box” (= internal view)
            - required & offered interface
                                                                                  sub-system
            - component connexions / association links
            -…

                                SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP)              11
  The ACCORD/UML RT-Component Model

  • ACCORD/UML component Model based on
            UML2 component Model + RT_QoS

    Component                               Interface


                                 BehavioralFeatures                                      RT_QoS

 Interface can have both BehavioralFeatures:
  • operations also with QoS specif.
  • receptions (signals) with QoS specif.

            SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP)   12
            Model transformation:
            sub-system identification / component defintion

                                                    SpeedRegulator                          Speedometer


                                                         SC_Manager                             SpeedSensor

                                                                                                 getSpeed( )



                                                          Regulator



       Sub-Syst_1                                                                 <<DetailledContent>>
                                         <<DetailledContent>>

-“White box”
 = internal view
-“Black box”                                         SpeedRegulator                           Speedometer
  = external view


                      C_Sub-Syst_1



                    SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP)            13
UML specialisation for components
Component Model

                   RT_QoS          RT_QoS
    C_Sub-Syst_1            C_Sub-Syst_3


                   RT_QoS
    C_Sub-Syst_2




                    SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP)   14
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)   15
     The ACCORD/UML RT-Component Model
                 based on a MDA approach…
      Sub-system Model                      RT_QoS
                                                              Component Model
                     RT_QoS                 RT_QoS
                                                                                RT_QoS           RT_QoS

        Sub-Syst_1                 Sub-Syst_2                     C_Sub-Syst_1            C_Sub-Syst_3
                                                     ER2
                                   RT_QoS
                                                                                 RT_QoS
                                                                 C_Sub-Syst_2
                      Sub-Syst_3




                                                                                                          CCM

ER2 = These mappings take into account specified RT features
of the sub-system model                         PIM-to-PIM
ER3 = Mappings definition from the RT-Component Model of
ACCORD/UML towards a platform model (e.g., RT-CCM model)
                                               PIM-to-PSM
                              SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP)   16
    ACCORD/UML: A full MDA Approach
                                                                  Modeling concepts
                                Dico
                                Xxxx
                                xxxx
                                                                          Modeling rules
                                PAM
             PIM level
                                                                    Model enrichment

                                       Régulateur    Afficheur


                                                     Capteur




                                                                                              Dico
                                                                                              Xxxx
                                                                                              xxxx


                                DAM                                         Model         Valid.
Model enrichment                                                       translation filter
   mapping                              Régulateur    Afficheur


                                                       Capteur




                                                                                      Runnable level
OS Interf. model
                                 PrM
                             PSM level                              Code generation

                  SIVOES-MONA (Dresden, October the 1st) - Pr. F. Terrier & Dr. S. Gérard (L-LSP)      17

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:6
posted:8/25/2012
language:English
pages:17