Presentation is loading. Please wait.

Presentation is loading. Please wait.

Semantic Formalisms 2: Software Components Eric Madelaine INRIA Sophia-Antipolis Oasis team UNICE – EdStic Mastère Réseaux.

Published byJayden Fisher Modified over 10 years ago

Similar presentations

Presentation on theme: "Semantic Formalisms 2: Software Components Eric Madelaine INRIA Sophia-Antipolis Oasis team UNICE – EdStic Mastère Réseaux."— Presentation transcript:

1 Semantic Formalisms 2: Software Components Eric Madelaine eric.madelaine@sophia.inria.fr INRIA Sophia-Antipolis Oasis team UNICE – EdStic Mastère Réseaux et Systèmes Distribués TC4 Formal Methods Operational Semantics: CCS, Bisimulations Software Components Fractal : hierarchical components Deployment, transformations Specification of components Application to distributed applications Active object and distributed components Behaviour models An analysis and verification platform

2 Mastère RSD - TC4 oct/nov 20062 Program of the course: 1: Software Components Fractal : hierarchical components –Specification of Component Systems –Modelling with UML diagrams Specification and verification of behaviours –Generating non-functional controllers –Expressing and proving properties

3 Mastère RSD - TC4 oct/nov 20063 Fractives components FRACTAL : Component* model specification, implemented using ProActive : Java library for distributed applications = Fractive Features: –Hierarchical Component Model –Separation of functionality / control –ADL description (Fractals XML Schema/DTD) –Distributed components (from distributed objects) –Asynchronous method calls (non-blocking) –Strong Formal Semantics => properties and guarantees * Component : self-contained entity, with well-defined interfaces, reusable, composable (hierarchically)

4 Mastère RSD - TC4 oct/nov 20064 ATTRIBUTEBINDINGLIFE CYCLECONTENT Content Fractals Components Membrane Functional interfaces Non-functional interfaces

5 Mastère RSD - TC4 oct/nov 20065 Content Fractals Components : Architecture Primitive Component Composite Component Provide interface (server role) Require interfaces (client role) Delegates Binding

6 Mastère RSD - TC4 oct/nov 20066 Fractals Components Non-functional interfaces ATTRIBUTEBINDINGLIFE CYCLECONTENT Life-cycle : start / stop the component Binding : bind / unbind a connection between interfaces Content : add / remove sub-components Attribute : get set the value of attribute values

7 Mastère RSD - TC4 oct/nov 20067 Component System Specification 1.Architecture Description (ADL): Primitive components, Composite components, Bindings 2.Interface Description (IDL): –Will be a Java specification in the case of ProActive 3.Behaviour Description: Any process language: LTS, CCS, value-passing CCS, Lotos…

8 Mastère RSD - TC4 oct/nov 20068 Buffer System example <component name="BufferSystem" definition="components.BufferSystem(3)"> <interface name="alarm" role="client" signature="components.AlarmInterface"/> <interface name="alarm" role="server" signature="components.AlarmInterface"/> <behaviour file="AlarmBehav" format="FC2Param"/> <binding client="BufferSystem.alarm" server="Alarm.alarm"/> <component name="BufferSystem" definition="components.BufferSystem(3)"> <interface name="alarm" role="client" signature="components.AlarmInterface"/> <interface name="alarm" role="server" signature="components.AlarmInterface"/> <behaviour file="AlarmBehav" format="FC2Param"/> <binding client="BufferSystem.alarm" server="Alarm.alarm"/>

9 Mastère RSD - TC4 oct/nov 20069 Buffer System example <component name="BufferSystem" definition="components.BufferSystem(3)"> <interface name="alarm" role="client" signature="components.AlarmInterface"/> <interface name="alarm" role="server" signature="components.AlarmInterface"/> <behaviour file="AlarmBehav" format="FC2Param"/> <binding client="BufferSystem.alarm" server="Alarm.alarm"/> <component name="BufferSystem" definition="components.BufferSystem(3)"> <interface name="alarm" role="client" signature="components.AlarmInterface"/> <interface name="alarm" role="server" signature="components.AlarmInterface"/> <behaviour file="AlarmBehav" format="FC2Param"/> <binding client="BufferSystem.alarm" server="Alarm.alarm"/>

10 Mastère RSD - TC4 oct/nov 200610 UML diagrams, modelling tools We use UML 2.0 diagrams as a (simple) language for describing both the architecture and the behaviour. Architecture : Composite structures –Hierarchy of boxes, ports/interfaces, interface descriptions, connexions Behaviour: State machines –States (with state variables), control structures (tests, loops), transitions, communication events.

11 Mastère RSD - TC4 oct/nov 200611 UML modelling tool: CTTool Derived from TTool (Turtle Toolkit) –From ENST Sophia Labsoc (Systems on chip) –Turtle = Timed UML and RT-Lotos Environment http://labsoc.comelec.enst.fr/turtle/ Adapted for Components (hierarchy, interfaces) and from UML 1.5 to UML 2.0.

12 Mastère RSD - TC4 oct/nov 200612 UML modelling tool: CTTool Introduce construction, graphically, step by step. Do it within the tool ??? Warning: preliminary, intermediate version Then speak of model generation before going to proofs. Back to the CTTool with the CADP proofs.

13 Mastère RSD - TC4 oct/nov 200613 Program of the course: 1: Software Components Fractal : hierarchical components –Specification of Component Systems –Modelling with UML diagrams Specification and verification of behaviours –Generating non-functional controllers –Expressing and proving properties

14 Mastère RSD - TC4 oct/nov 200614 Building a Fractive Behavioural model Functional behaviour is known –Given by the user –Obtained by static analysis Non-functional (& asynchronous) behaviour is automatically added from the components ADL –Automata within a synchronisation network, named controller Components behaviour is the controllers synchronisation product

15 Mastère RSD - TC4 oct/nov 200615 <interface name=alarm" role=client" signature="components.AlmInterface"/> <component name=Buffer" <interface name=get" role=server" signature="components.GetInterface"/> <interface name=put" role=server" signature="components.PutInterface"/> <interface name=alarm" role=client" signature="components.AlmInterface"/> <behaviour file="AlarmBehav" format="FC2Param"/> <component name=Consumer" <interface name=buf" role=client" signature="components.GetInterface"/> <behaviour file=ConsBehav" format="FC2Param"/> <component name=Producer" <interface name=buf" role=client" signature="components.PutInterface"/> <behaviour file=ProdBehav" format="FC2Param"/> Building the Models: Topology BufferSystem <component name=Consumer" <component name=Buffer" <component name=Producer" Buffer Consumer Producer

16 Mastère RSD - TC4 oct/nov 200616 Building the Models: Topology BufferSystem Consumer Producer Buffer <component name=Buffer" <interface name=get" role=server" signature="components.GetInterface"/> <interface name=put" role=server" signature="components.PutInterface"/> <interface name=alarm" role=client" signature="components.AlmInterface"/> <behaviour file=BufferBehav" format="FC2Param"/> <component name=Buffer" <interface name=get" role=server" signature="components.GetInterface"/> <interface name=put" role=server" signature="components.PutInterface"/> <interface name=alarm" role=client" signature="components.AlmInterface"/> <behaviour file=BufferBehav" format="FC2Param"/> ?Q_get() !R_get(x) ?Q_put(y) !Q_alarm()

17 Mastère RSD - TC4 oct/nov 200617 Building the Models: Topology BufferSystem Consumer Producer Buffer <interface name=alarm" role=client" signature="components.AlmInterface"/> <interface name=foo" role=server" signature="components.FooInterface"/> <interface name=alarm" role=client" signature="components.AlmInterface"/> <interface name=foo" role=server" signature="components.FooInterface"/> !Q_alarm() ?Q_foo()

18 Mastère RSD - TC4 oct/nov 200618 BufferSystem Building the Models: Non-Functional Behaviour Consumer Buffer ?bind(..) !bind/unbind(..) Producer ?bind(f,P.f) ?unbind(a,P.f) unbound bound !Err(unbound,Bf.a) ?bind(a,BSI.a) ?unbind(a,BSI.a) unbound bound !bind(..) !R_alarm() ?Q_foo() ?start/stop BS.foo B.alarm ?start/stop

19 Mastère RSD - TC4 oct/nov 200619 Building the Models: asynchronous behaviour Buffer Consumer Producer !bind/unbind !start/stop BufferSystem Body LF Proxy (fut) Queue ?Serve(M,…) Call(M,…) ?Requests !Response ?Response !Request Body ?Serve start/stop ?Serve bind/unbind ?Serve(M,fut,args) !fut.call(M,args) !bind/unbind !start/stop !bind/unbind!start/stop Components Controller Components Controller

20 Mastère RSD - TC4 oct/nov 200620 Static Automaton (1) Content + Controllers : Static vision of the (initial) architecture; the bindings are not yet established, the components not started, but all controllers ready to proceed. Deployment = establish the bindings, set initial values, and start (hierarchically) all components. Part of the ADL, or described in a deployment file

21 Mastère RSD - TC4 oct/nov 200621 Static Automaton (2) O D = {deployment actions} Static automaton = ( Controller || Deployment ) Missing Start transition here Deployment automaton :

22 Mastère RSD - TC4 oct/nov 200622 (1) Absence of errors during deployment (checked on the static automaton) O E = {error actions} Property (ACTL) : Properties e.g. imagine a faulty deployment specification : -> start Buffer without linking the alarm Resulting Static automaton :

23 Mastère RSD - TC4 oct/nov 200623 (2) Functional behaviour (checked on the static automaton) –Get from the buffer eventually gives an answer Properties Property ( regular -calculus) : [ true*.Q_get() ] X. ( true [ R_get() ] X )

24 Mastère RSD - TC4 oct/nov 200624 (3) Functional behaviour under reconfiguration –Selected reconfiguration actions are allowed after deployment Properties

25 Mastère RSD - TC4 oct/nov 200625 (3) Functional behaviour under reconfiguration –Future update (once the method served) independent of life-cycle or bindings reconfigurations –E.g (regular -calculus) : –With C T {, } Properties [ true*. Q_get() ] X. ( true [ R_get() ] X )

26 Mastère RSD - TC4 oct/nov 200626 Vercors Platform Tool set : –CTTool: Architecture and behaviour specification (prototype) –Code analysis (prototype) –ADL2N: Model generation (available) –Bridges with model-checking and verification tools (available) Supported by FIACRE An ACI-Security action of the French research ministry

27 Mastère RSD - TC4 oct/nov 200627 Vercors Platform Code analysis Model generation Verification CTTool Modelization.lotos

28 Mastère RSD - TC4 oct/nov 200628 Tools: Pragmatics Development of Tools: –Use standard, efficient, verification engines. –Parameterized, synchronized networks of automata as a compact interface format. –Optimizations of state-space. –Hide the complexity to final users. Avoiding state explosion 1.Distributed model generation (distributor, CADP) 2.Reduced controllers based on deployment 3.On-the-fly mixed with compositional hiding and minimisation Avoiding state explosion 1.Distributed model generation (distributor, CADP) 2.Reduced controllers based on deployment 3.On-the-fly mixed with compositional hiding and minimisation

29 Mastère RSD - TC4 oct/nov 200629 Home Work : play with CTTool 1.Lancement de CTTool –Dans le répertoire http://www-sop.inria.fr/oasis/Eric.Madelaine/Teaching/RSD2006/CTTool –récupérez le logiciel CTTool (CTTool.jar et config.xml); installez-les chez vous dans le même répertoire. –récupérez la doc (CTToolReport.pdf) –récupérez les fichiers d'exemples: ConsumerProducer.xml et car1.xml –Lancez CTTool (attention java 1.5 seulement): java -jar CTTool.jar -lotos - proactive 2.Exemple du Consumer / Producer –Ouvrez le fichier ConsumerProducer.xml: (Dans l'éditeur CTTool, File->Open- >... ) –Étudiez le diagramme de composants et les diagrammes des machines d'état. Pour mieux comprendre, voir CTToolReport Chapter5. 3.Exemple d'un Système de contrôle de boite de vitesse : Utilisation des outils CTTool / CADP Correction semaine prochaine.

30 Mastère RSD - TC4 oct/nov 200630 Next course 3) Application to distributed applications –ProActive : active object and distributed components –Behaviour models –Case-study –Tools : build an analysis and verification platform www-sop.inria.fr/oasis/Eric.Madelaine Teaching/RSD-2006

Download ppt "Semantic Formalisms 2: Software Components Eric Madelaine INRIA Sophia-Antipolis Oasis team UNICE – EdStic Mastère Réseaux."

Similar presentations

3° Workshop Nazionale del Gruppo di Interesse in Ingegneria del Software Genova, 2-3 ottobre 2006 CASE – Libera Università di Bolzano-Bozen RCOST – Università

3° Workshop Nazionale del Gruppo di Interesse in Ingegneria del Software Genova, 2-3 ottobre 2006 CASE – Libera Università di Bolzano-Bozen RCOST – Università
November 20GEOINFO 20061/25 A Robust Strategy for Handling Linear Features in Topologically Consistent Polyline Simplification Department of Computer Engineering.

November 20GEOINFO 20061/25 A Robust Strategy for Handling Linear Features in Topologically Consistent Polyline Simplification Department of Computer Engineering.
Elton Mathias and Jean Michael Legait 1 Elton Mathias, Jean Michael Legait, Denis Caromel, et al. OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis,

Elton Mathias and Jean Michael Legait 1 Elton Mathias, Jean Michael Legait, Denis Caromel, et al. OASIS Team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis,
CACORE TOOLS FEATURES. caCORE SDK Features caCORE Workbench Plugin EA/ArgoUML Plug-in development Integrated support of semantic integration in the plugin.

CACORE TOOLS FEATURES. caCORE SDK Features caCORE Workbench Plugin EA/ArgoUML Plug-in development Integrated support of semantic integration in the plugin.
1 23 maart 2006 Surface construction techniques for volumetric objects How to maintain convex and concave features? Eddy Loke and Erik Jansen.

1 23 maart 2006 Surface construction techniques for volumetric objects How to maintain convex and concave features? Eddy Loke and Erik Jansen.
EAR-BASED AMENDMENT FORUM. September 20062 Sponsored by the Pinellas Planning Council September 12 & 13, 2006 Harborview Center Clearwater.

EAR-BASED AMENDMENT FORUM. September Sponsored by the Pinellas Planning Council September 12 & 13, 2006 Harborview Center Clearwater.
THHGCS07B Coordinate Marketing Activities Lecture 2.

THHGCS07B Coordinate Marketing Activities Lecture 2.
Data accreditation standard for the IM&T DES12 Sept 20061 The IM&T DES Using the tools that support e- audit John Williams & James Barrett.

Data accreditation standard for the IM&T DES12 Sept The IM&T DES Using the tools that support e- audit John Williams & James Barrett.
A Stepwise Modeling Approach for Individual Media Semantics Annett Mitschick, Klaus Meißner TU Dresden, Department of Computer Science, Multimedia Technology.

A Stepwise Modeling Approach for Individual Media Semantics Annett Mitschick, Klaus Meißner TU Dresden, Department of Computer Science, Multimedia Technology.
Component Oriented Programming 1 Chapter 2 Theory of Components.

Component Oriented Programming 1 Chapter 2 Theory of Components.
European Commission Directorate-General Information Society Unit F2 – Grid Technologies INSERT PROJECT ACRONYM HERE BY EDITING THE MASTER SLIDE (VIEW.

European Commission Directorate-General Information Society Unit F2 – Grid Technologies INSERT PROJECT ACRONYM HERE BY EDITING THE MASTER SLIDE (VIEW.
1 Statecharts for the many: Algebraic State Transition Diagrams Marc Frappier GRIL – Groupe de recherche en ingénierie du logiciel.

1 Statecharts for the many: Algebraic State Transition Diagrams Marc Frappier GRIL – Groupe de recherche en ingénierie du logiciel.
Background information Formal verification methods based on theorem proving techniques and model­checking –to prove the absence of errors (in the formal.

Background information Formal verification methods based on theorem proving techniques and model­checking –to prove the absence of errors (in the formal.
Eric MADELAINE1 E. Madelaine, Antonio Cansado, Emil Salageanu OASIS Team, INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis OSCAR meeting, Valparaiso,

Eric MADELAINE1 E. Madelaine, Antonio Cansado, Emil Salageanu OASIS Team, INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis OSCAR meeting, Valparaiso,
Introduction To System Analysis and Design

Introduction To System Analysis and Design
Component Models and Technology Component-based Software Engineering

Component Models and Technology Component-based Software Engineering
Component-Interaction Automata for Specification and Verification of Component Interactions P. Vařeková and B. Zimmerova Masaryk University in Brno Czech.

Component-Interaction Automata for Specification and Verification of Component Interactions P. Vařeková and B. Zimmerova Masaryk University in Brno Czech.
Software Engineering, COMP201 Slide 1 Protocol Engineering Protocol Specification using CFSM model Lecture 30.

Software Engineering, COMP201 Slide 1 Protocol Engineering Protocol Specification using CFSM model Lecture 30.
1 IFM 2005 – November 30, 2005 EXP.OPEN 2.0 A flexible tool integrating partial order, compositional, and on-the-fly verification methods Frédéric Lang.

1 IFM 2005 – November 30, 2005 EXP.OPEN 2.0 A flexible tool integrating partial order, compositional, and on-the-fly verification methods Frédéric Lang.
Optimisation of behaviour of component-based distributed systems INRIA - I3S - CNRS – University of Nice Sophia-Antipolis EPC SCALE Galyna Zholtkevych.

Optimisation of behaviour of component-based distributed systems INRIA - I3S - CNRS – University of Nice Sophia-Antipolis EPC SCALE Galyna Zholtkevych.

Similar presentations

Ads by Google