2. SIVOES-MONA (Dresden, October the 1 st ) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 1 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

3. SIVOES-MONA (Dresden, October the 1 st ) - 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

4. SIVOES-MONA (Dresden, October the 1 st ) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 3 The project partners End-UsersAcademicsEditors PRIME

5. SIVOES-MONA (Dresden, October the 1 st ) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 4 Validation Development The AIT-WOODDES platform Rhapsody XMI ModelChecker Internal exchange format UPPAAL Model exchange via XML Rose XMI Internal exchange format Agatha Objecteering Accord

6. SIVOES-MONA (Dresden, October the 1 st ) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 5 Case study of PSA-MECEL  Routing system GPS GSM/GPRS/UMTS Internet Service provider  Evaluate project results on:  Methodology  RT Profile adequation  Tools efficiency  Model exchange  Code generation  Validation capabilities

7. SIVOES-MONA (Dresden, October the 1 st ) - 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

8. SIVOES-MONA (Dresden, October the 1 st ) - 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 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.

9. SIVOES-MONA (Dresden, October the 1 st ) - 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,... )

10. SIVOES-MONA (Dresden, October the 1 st ) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 9 user ! + Structure of the ACCORD/UML Methodology ACCORD/UML Methodology relizes Modelling tools defined by ACCORD/UML Profile OMG’ Standard profiles !!! SPE profileSPT profileAL profile

11. SIVOES-MONA (Dresden, October the 1 st ) - 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 Analysis Model High-Level Scenarios Models Dictionary theSystem Use Cases Model theSystem Possible Scénario 1..* ucDiag 1 dico 1 Use Case Actor envElt * 1 Use Case Diagram describedBy * envElt * Class RT_QoS

12. SIVOES-MONA (Dresden, October the 1 st ) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 11 Decomposition heuristics & component model Initial Model ACCORD/UML (PAM ou DAM) ACCORD/UML (PAM ou DAM) Sub-system Model Sub-Syst_1Sub-Syst_2 Sub-Syst_3 «refine» ER1 C_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 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

13. SIVOES-MONA (Dresden, October the 1 st ) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 12 Component ACCORD/UML component Model based on UML2 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

14. SIVOES-MONA (Dresden, October the 1 st ) - 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 > SpeedRegulator Speedometer

15. SIVOES-MONA (Dresden, October the 1 st ) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 14 UML specialisation for components RT_QoS C_Sub-Syst_1 C_Sub-Syst_2 C_Sub-Syst_3 Component Model

16. SIVOES-MONA (Dresden, October the 1 st ) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 15 Qos & components: on behavioral features UML Profile for QoS… Required QoSOffered QoS « rPriority » {priorValue 5}

17. SIVOES-MONA (Dresden, October the 1 st ) - 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 ER3 RT_QoS C_Sub-Syst_1 C_Sub-Syst_2 C_Sub-Syst_3 Component Model ER2 RT_QoS Sub-system Model Sub-Syst_1Sub-Syst_2 Sub-Syst_3 RT_QoS ER2 = These mappings take into account specified RT features of the sub-system model  PIM-to-PIM

18. SIVOES-MONA (Dresden, October the 1 st ) - Pr. F. Terrier & Dr. S. Gérard (L-LSP) 17 ACCORD/UML: A full MDA Approach PIM level PSM level RégulateurAfficheur Capteur PrM RégulateurAfficheur Capteur DAM Runnable level Dico Xxxx xxxx PAM Dico Xxxx xxxx Valid. Modeling rules Modeling concepts Model enrichment Model translation filter Model enrichment mapping OS Interf. model Code generation