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

Slides:

Advertisements

Similar presentations

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

Advertisements

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,

Architecture Representation

European Commission Directorate-General Information Society Unit F2 – Grid Technologies INSERT PROJECT ACRONYM HERE BY EDITING THE MASTER SLIDE (VIEW.

Towards a Practical Composition Language Oscar Nierstrasz Software Composition Group University of Bern.

Denis Caromel1 Joint work with Ludovic Henrio – Eric Madelaine et. OASIS members OASIS Team INRIA -- CNRS - I3S – Univ. of Nice Sophia-Antipolis, IUF.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 8 Slide 1 System modeling 2.

©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 System models.

Architecture-driven Modeling and Analysis By David Garlan and Bradley Schmerl Presented by Charita Feldman.

Π-Method: A Model-Driven Formal Method for Architecture- Centric Software Engineering By Flavio Oquendo Presented by: Sajith Wickramaratne.

Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.

Course Instructor: Aisha Azeem

Architectural Design Establishing the overall structure of a software system Objectives To introduce architectural design and to discuss its importance.

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

Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.

©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.

02/06/05 “Investigating a Finite–State Machine Notation for Discrete–Event Systems” Nikolay Stoimenov.

The Design Discipline.

Safe composition of distributed adaptable components A distributed component model Behavioural specification and verification Ludovic Henrio and Eric Madelaine.

©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions of systems whose requirements are being.

Chapter 4 System Models A description of the various models that can be used to specify software systems.

System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.

INRIA Sophia-Antipolis, Oasis team INRIA Rhône-Alpes, Vasy team Feria–IRIT/LAAS, SVF team Toulouse GET - ENST Paris, LTCI team FIACRE Models and Tools.

The Grid Component Model: an Overview “Proposal for a Grid Component Model” DPM02 “Basic Features of the Grid Component Model (assessed)” -- DPM04 CoreGrid.

Smith’s Aerospace © P. Bailey & K. Vander Linden, 2005 Architecture: Component and Deployment Diagrams Patrick Bailey Keith Vander Linden Calvin College.

©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapter 7 Slide 1 System models l Abstract descriptions.

Formalism and Platform for Autonomous Distributed Components Bio-inspired Networks and Services A Distributed Component Model Formalisation in Isabelle.

Eric Madelaine FORTE ’04 -- Madrid sept /25 Parameterized Models for Distributed Java Objects Eric Madelaine work with Tomás Barros, Rabéa Boulifa.

Eric MadelaineOSMOSE -- WP2 -- Prague June 2004 Models for the Verification of Distributed Java Objects Eric Madelaine work with Tomás Barros, Rabéa Boulifa,

©Ian Sommerville 2006Software Engineering, 8th edition. Chapter 8 Slide 1 Object-oriented and Structured System Models.

Chapter 7 System models.

System models l Abstract descriptions of systems whose requirements are being analysed.

Modified by Juan M. Gomez Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.

Software Engineering, 8th edition Chapter 8 1 Courtesy: ©Ian Somerville 2006 April 06 th, 2009 Lecture # 13 System models.

Sommerville 2004,Mejia-Alvarez 2009Software Engineering, 7th edition. Chapter 8 Slide 1 System models.

Eric MADELAINE1 T. Barros, L. Henrio, E. Madelaine OASIS Team, INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis (FACS’05), Fractal workshop, Grenoble.

A graphical specification environment for GCM component-based applications INRIA – I3S – CNRS – University of Nice-Sophia Antipolis EPC OASIS Oleksandra.

Asynchronous Components with Futures: Semantics, Specification, and Proofs in a Theorem Prover Components (Distributed) Futures Formalisations (and proofs)

CPSC 372 John D. McGregor Module 3 Session 1 Architecture.

Behavioural Verification of Distributed Components Ludovic Henrio and Eric Madelaine ICE

Grid programming with components: an advanced COMPonent platform for an effective invisible grid © GridCOMP Grids Programming with components.

Grid programming with components: an advanced COMPonent platform for an effective invisible grid © 2006 GridCOMP Grids Programming with components. An.

FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.

Part VII: Design Continuous

1. 2 Objects to Distributed Components (1) Typed Group Java or Active Object ComponentIdentity Cpt = newActiveComponent (params); A a = Cpt ….getFcInterface.

CPSC 871 John D. McGregor Module 3 Session 1 Architecture.

1 CSCD 326 Data Structures I Software Design. 2 The Software Life Cycle 1. Specification 2. Design 3. Risk Analysis 4. Verification 5. Coding 6. Testing.

Mastère RSD - TC4 2005/20061 Distributed Components –ProActive-Fractal : main concepts –Behaviour models for components –Deployment, management, transformations.

Parameterized Models for Distributed Java Objects Tomás Barros & Rabéa Boulifa OASIS Project INRIA Sophia Antipolis April 2004.

ProActive components and legacy code Matthieu MOREL.

Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.

Chapter 19: Interfaces and Components [Arlow and Neustadt, 2005] University of Nevada, Reno Department of Computer Science & Engineering.

Eric MadelaineOSCAR Workshop -- Santiago Nov Verification of Distributed Applications Eric Madelaine work with Isabelle Attali, Tomás Barros, Rabéa.

Eric MADELAINE ---- OASIS1 E. Madelaine Oasis team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis RESECO ’08 Santiago – Nov. 24, 2008 Specification.

Eric MADELAINE1 A. Cansado, L. Henrio, E. Madelaine OASIS Team, INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis Fractal workshop, Nantes, 3 july.

RESECO - Montevideo - 22 nov 2007Reseco, Montevideo, 22 nov 2007 Eric Madelaine - OASIS Team1 Specifying and Generating Safe GCM Components INRIA – Sophia.

VERIFYING THE CORRECT COMPOSITION OF DISTRIBUTED COMPONENTS: FORMALISATION AND TOOL Ludovic Henrio 1, Oleksandra Kulankhina 1,2, Dongqian Liu 3, Eric Madelaine.

Eric MADELAINE ---- OASIS1 E. Madelaine Oasis team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis ECNU Dept of Software Engineering October 2010.

Specifying Fractal and GCM Components With UML Solange Ahumada, Ludovic Apvrille, Tomás Barros, Antonio Cansado, Eric Madelaine and Emil Salageanu SCCC.

Formal Verification. Background Information Formal verification methods based on theorem proving techniques and modelchecking –To prove the absence of.

Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 1 Behavioural Models for Hierarchical Components Tomás Barros, Ludovic Henrio and Eric Madelaine.

Distributed Components and Futures: Models and Challenges A Distributed Component Model Distributed Reconfiguration Calculi for Components and Futures.

Eric MADELAINE -- GridComp -- OASIS 1 E. Madelaine (A. Cansado) GridComp project OASIS team INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis GridComp.

Eric MADELAINE1 T. Barros, L. Henrio, E. Madelaine OASIS Team, INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis DCC, University.

1 SWE Introduction to Software Engineering Lecture 14 – System Modeling.

GCM/ProActive: a distributed component model, its implementation, and its formalisation Ludovic Henrio OASIS Team INRIA – UNS – I3S – CNRS Sophia Antipolis.

Model Generation for Distributed Java Programs Rabéa Boulifa Eric Madelaine Oasis Team INRIA, Sophia-Antipolis France, I3S, UNSA Luxembourg, November 28,

Behavioural Models for Distributed Hierarchical Components

Distributed Components and Futures: Models and Challenges

Abstract descriptions of systems whose requirements are being analysed

Presentation transcript:

Eric MADELAINE1 E. Madelaine, Antonio Cansado, Emil Salageanu OASIS Team, INRIA -- CNRS - I3S -- Univ. of Nice Sophia-Antipolis OSCAR meeting, Valparaiso, dec 2006 A UML profile for Distributed Components

Eric MADELAINE2 Motivations Vercors Platform Specification Languages UML models for distributed components TTool UML 2.0 components CTTool Towards a profile for the Grid Component Model Perspectives Agenda

Eric MADELAINE3 Definition : Software modules, composable, with well-defined interfaces, and well-defined black box behaviour Our interests : 1. Encapsulation: Black boxes, offered and required services 2. Composition Design of complex systems, hierarchical organization into sub-systems 3. Separate administration Architecture Description Language (ADL), Non-functional interfaces 4. Distribution (e.g. Computational Grid) Interaction at interfaces through asynchronous method calls Distributed Applications : ProActive implementation of the Fractal Model, Grid Component Model (GCM) Distributed Software Components

Eric MADELAINE4 The Vercors Platform Eric Madelaine Tomas Barros Christophe Massols Marcela Rivera Antonio Cansado Emil Salageanu Hejer Rejeb …

Eric MADELAINE5 The Vercors Platform : Formats 1: Architecture & Interfaces Descriptions 2: Parameterized Networks of LTSs 3 : Networks of Finite LTSs 4 : (full) Lotos Processes

Eric MADELAINE6 The Vercors Platform Mapping ??? Arguments of method calls and return values, in the interface formalism Values in Lotos data types

Eric MADELAINE7 Need for an Integrated Specification Language Examples: -Process Algebras -Java/A -ArchWare Π-ADL  Work of Antonio Cansado… Including distributed component concepts: - Request queues, futures, proxies, collective interfaces, non-functional controllers, etc.

Eric MADELAINE8 Next Step: Language for the non-expert user -Do not invent “yet another graphical specification language” -Required capacities: hierarchical component architecture, signatures of interfaces, FSM behaviour specifications -Extensibility for higher level abstractions. -Semantics in term of the specification language. => UML diagrams Specification Language Expressiveness, Completeness, Strong semantics, Calculus-level proofs…

Eric MADELAINE9 Next Step: Language for the non-expert user UML Architecture + behaviours ADL & Proactive code “correct by construction”

Eric MADELAINE10 Motivations Vercors Platform Specification Languages UML models for distributed components TTool UML 2.0 components CTTool Towards a profile for the Grid Component Model Perspectives Agenda

Eric MADELAINE11 Starting Point: TTool - Labsoc (System On Chip), ENST Sophia, Ludovic Apvrile. -UML 1.5 diagrams: -Class diagrams + Interaction diagrams / Sequence Charts + Real Time -Turtle Model: -Translation to RT-Lotos, Real-time Model-checking -Generation of Java code (simulator)

Eric MADELAINE12 Starting Point: TTool

Eric MADELAINE13 Class diagrams

Eric MADELAINE14 Activity diagrams

Eric MADELAINE15 UML 2.0 : new standard diagrams for components [ V. Mencl, M. Polak, Fractal’06 UML 2.0 Components and Fractal: An Analysis ] Component: now “as we know it” hierarchy / nested components provided and required interfaces Key concepts: StructuredClassifier functionality decomposed into parts EncapsulatedClassifier communication through Ports Port has provided and required Interfaces has multiplicity (=> collection interfaces) Component combines these features, + inherits from Class (attributes)

Eric MADELAINE16 UML 2.0 [continued] 1.As a StructuredClassifier may own parts with type, multiplicity 2. As a NameSpace may own components, classes, instanceSpecifications, interfaces But you must explicitely instanciate components.

Eric MADELAINE17 UML 2.0 [continued] : technical details 1.Connectors Cannot be linked to interfaces (only to ports) Cannot be linked to InstanceSpecifications 2. Interfaces via Ports: Only one interface per port. Position of interface client/server. Port multiplicity determines cardinality+contingency. 3. Subcomponents implemented as Component + InstanceSecification

Eric MADELAINE18 UML 2.0 [continued] 1.Full mapping Fractal/Sofa -> UML 2.0 by M. Polak (2006) 1.Prototype Implementation, using Enterprise Architect

Eric MADELAINE19 Prototype : CTTool (with Emil Salageanu) -UML 2.0 diagrams for Composite Structures + State Machines -Editor + verification environment using TTool code base => generation of Lotos code => bridges to CADP toolset -No deviance from UML 2.0 -No asynchronous components yet (common base for Oasis / Labsoc)  Prototype available: www-sop.inria.fr/oasis/Vercors Demo…

Eric MADELAINE20 Next Step : ProActive TTool ?? 1)Simplify the graphical constructions: Interface / Ports Delegate interfaces Libraries for components, interface descriptions 2)Higher level constructions Asynchronous components (future proxies, queues) Multicast and Gathercast interfaces

Eric MADELAINE21 Next Step : ProActive TTool ?? Integration in the ProActive IDE ?? -Eclipse Plugin -Fractal / GCM GUI -Early warnings / semantic information : -deadlocks, active object dependencies, etc

Eric MADELAINE22 Next Step : Graphics Keep as much as possible existing styles…: 1.UML 2.0 composite structures 2.Fractal GUI (??) 3.MARTE 4.Simulink….

Eric MADELAINE23 Muchas gracias