1 / 17

Project-Team Triskell Model Driven Engineering for Component Based Software

Project-Team Triskell Model Driven Engineering for Component Based Software. Prof. Jean-Marc Jézéquel jezequel@irisa.fr http://www.irisa.fr/triskell. People (01/09/10). Scientific Leader Jean-Marc Jézéquel [Prof. Univ. Rennes 1] Permanent staff Olivier Barais [MdC Rennes I]

zea
Download Presentation

Project-Team Triskell Model Driven Engineering for Component Based Software

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project-Team TriskellModel Driven Engineering for Component Based Software Prof. Jean-Marc Jézéquel jezequel@irisa.fr http://www.irisa.fr/triskell

  2. People (01/09/10) • Scientific Leader • Jean-Marc Jézéquel [Prof. Univ. Rennes 1] • Permanent staff • Olivier Barais [MdC Rennes I] • Benoît Baudry [CR INRIA] • Johann Bourcier [MdC Rennes I] • Benoit Combemale [MdC Rennes I] • Naouel Moha [MdC Rennes I] (On leave to Montreal) • Noël Plouzeau [MdC Rennes I] • Didier Vojtisek [IR INRIA] • INRIA Delegation • Gerson Sunye [U. Nantes] • 15 PhD students • 4 Temporary Engineers & 2 Post-doc

  3. TriskellResearch Goals

  4. Versions (Time) 1.2 1.4 1.4 1.4 1.4 1.4 1.3 1.3 1.3 1.3 1.3 1.2 1.2 1.2 1.2 1.2 1.1 1.1 1.1 1.1 1.1 1.1 1.0 1.0 1.0 1.0 1.0 Variants (Functionalities) Software Intensive Systems • Importance of non-functional properties • Service/Component based systems, IoT/IoS • quality of service : security, reliability, latency, performance... • Variations in functional aspects • notion of product lines (space, time) Example : Nokia 1,5 billions phones in circulation Hundreds of networks ~10.000 variants of software 1.0

  5. UI Model QoS Model Security Model Business Model Use Case Model Object Model Platform Model Design Model tester Test Model Code Model Modeling &Weaving Abstracting an Aspect of Reality for a specific purpose • Challenges: • Product Families • Reuse of • WeavingProcess • AutomaticWeaving • DesignTime/Runtime

  6. Scientific objectives: combine formal methods & established practice Evolution • Contracts and Aspects: from Requirements to Design to Runtime • Requirements by Contract, Analysis and Design by Contract (inc. QoS) • Aspect-Oriented Requirements & Design • Integration of IoT &IoS • Model-Based Testing • requirement based testing, requirement validation • design based testing, design validation Feed-back loop Formal Aspects • Executable Meta-modeling: • tools for building tools for building software • Kernel Meta-modeling language (KerMeta), based on MOF+actions • tools for building software : see above • MDKs: frameworks written in KerMeta

  7. Highlights 2009- Kermeta 1.3.2- Models@runtime- Testing Model Transformations- 6 papers at MODELS 09

  8. Kermeta: Breathing life into Meta-Models • // MyKermetaProgram.kmt • // An E-MOF metamodel is an OO program that does nothing require "StateMachine.ecore"// to import it in Kermeta • // Kermeta lets you weave inaspects // Contracts (OCL WFR) require “StaticSemantics.ocl” // Method bodies (Dynamic semantics) require “DynamicSemantics.kmt” // Transformations Context FSM inv: ownedState->forAll(s1,s2| s1.name=s2.name implies s1=s2) aspect class FSM { operation reset() : Void { currentState := initialState }} class Minimizer { operation minimize (source: FSM):FSM {…} }

  9. Kernel Meta-modeling Language: Kermeta 1.3.2 • Kermeta is a Model-Oriented Language • based on an AO/OO executable meta-modeling paradigm • Static typing, generics, functions objects, reflection… • First language where models are first class entities • Allows interesting questions to be asked: e.g.; what is the type of a model? • Kermeta Workbench • Eclipse-based specification of abstract syntax, static semantic (OCL) and dynamic semantics, connection to the concrete syntax. • Interpreter, compiler V1 (V2 based on Scala well underway) • model transformations, design level aspect weaving

  10. Models@runtime Features Design-timeValidation Notification Procedure Metamodel Driving InOffice DerivationAOM Targetconfiguration Model@runtime RuntimeValidation ScriptGenerator Runningsystem

  11. Barriers to Systematic model transformation testing • Model transformations constitute a class of programs with unique characteristics that make testing them challenging • Complex Input and Output Data • Model Management Environments • Heterogeneity of Transformation Languages and Techniques • Various work address each issue separately • need for benchmarks and empirical comparisons • Comm. of the ACM (should appear in June 2010)

  12. TriskellValorisation

  13. Main Contracts (400-600 k€/year)

  14. TriskellPerspectives

  15. Perspectives (1/3) • Composition of models • New ways of composing software from modeling elements • at both model and meta-model levels • Unifying MDE, AOSD, SPL, Generative Programming… • ANR Movida, Artemis CHESS… • Composing models at runtime: dynamic adaptation • FP7 STREP: DiVA (03/2008-03-2011)

  16. Perspectives (2/3) • Design, Integration IoS/IoT • Handling large scale, heterogeneous systems • From Real-Time OSGI components to Web Services • Service Oriented Architecture • models for service contract definition; • evolution of SOA • prediction/monitoring/reconfiguration of SOA • Projects • FP7 S-Cube NoE (03/2008-03/2012) • FP7 NESSOS NoE (09/2010-09/2014)

  17. Perspectives (3/3) Model Driven Testing • Test and MDE • Combining proofs & tests • Test and aspects • Testing security aspects • Testing SOAs

More Related