1 / 14

Research Projects Symposium at MODELS’08 – Toulouse – sep. 09

FAROS Project a Composition Environment for Building Reliable Service-Oriented Architectures http://www.lifl.fr/faros. Partners : FT R&D, EDF R&D, I3S/CNRS, IRISA/INRIA, LIFL/INRIA, Alicante (subcontractor SME) Period : 2006-2008 (3 years)

dorie
Download Presentation

Research Projects Symposium at MODELS’08 – Toulouse – sep. 09

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. FAROS Projecta Composition Environment for Building Reliable Service-Oriented Architectureshttp://www.lifl.fr/faros Partners: FT R&D, EDF R&D, I3S/CNRS, IRISA/INRIA, LIFL/INRIA, Alicante (subcontractor SME) Period: 2006-2008 (3 years) Framework and funding: ANR (French National Research Agency), 0.78 M€ (total 1.2M€) Research Projects Symposium at MODELS’08 – Toulouse – sep. 09

  2. Motivations The current solutions for service integration Lack of means to express/ensure guarantees on service composition Lack of methodological guidelines to automate the provision of contracts from business requirements to execution platforms • The rise of SOA • Quickly offer new services, integrate various information systems • Various runtime supports • Architecture/infrastructure (ESB, SCA…) • Embedded/constrained envt • Guarantees (QoS…) for • Distinguish providers • Negotiate (service requirements / offers), establish responsibilities

  3. SERVICE ORIENTED CONTRACT BASED SOA DESIGN ARCHITECTURE FAROS objectives • Build a tool to design applications - through composition of services - using abstractions of a higher level than service technologies - made reliable using contracts • Demonstrate the approach on various applications and platforms (SOA/CBSE with and without contracting support) • Avoid ad hoc solutions : factorize transformations

  4. 2 1 3 3 3 A Model-Driven Project (2)

  5. 2 1 3 3 3 Case studies: 3 applications • SEDUITE : Information broadcast in schools (a running service-oriented architecture) • DMP : Access to personal medical record of a patient, in emergency and/or mobile contexts • CIRÉ : SmartBox/Meter for electrical networks, with remote management and consumption alert capabilities

  6. Info broadcast Metamodel DMP Models SEDUITE Models Business Models Activity Existing activity Input data Output data Actor Access constraint Time constraint Data constraint • Information broadcast: • Business model ≈ Pipe & Filter architecture, DataSource, Connector, Port…

  7. index m:Meter sb:SmartBox loadShedding comfort invoice am: ApplianceManager tv_hd: SmartAppliance room_1: TemperatureSensor room_2: TemperatureSensor heating_1: HeatingAppliance heating_2: HeatingAppliance pls: ProgrammableLoadShedding CIRE Metamodel oven: BasicAppliance wash: BasicAppliance CIRE Models Business Models (2) • CIRE / EDF: • Business model ≈ assembly/architecture of business entities: SmartBox, Meter, Appliance…

  8. Central Metamodel • Objectives : • Loose coupling between business and platform metamodels Approach similar to intermediate code in compilers • Make transformations reuse possible • Features : • Capability to preserve end-to-end structured information • End-to-end transformation of specific structures Coordination (orchestration), QoS dimensions • Approach : • Restrict the number of concepts (target the metamodel usage) • Master the complexity of transformations

  9. Central Metamodel (2) Central Metamodel • Contract: • Open model (Participant, Assume, Guarantee, etc.) • Types (structural, behavioral, non functional) • Expression of contractual properties • … Central Model • Structure and behavior: • Possible reification of services or components Interface, invocation,… • Focus on compositional aspects Primitive vs composite services Composite ≈ service orchestration • Execution model: • Extensible event model

  10. Execution Platforms • 5 targeted execution platforms: • Adore (weaving on SOA/BPEL) • WComp (assembly aspects on event-based mobile components) • ConFract (assertions language on hierarchical components/Fractal) • AOKell-FAC (aspects on component architectures/Fractal) • ORQOS (BPEL transformations) • Approach: • 8 patterns of typical contracts • A common event-based model for the definition of these patterns • Implementation schemes of these patterns on the 5 platforms

  11. Platforms: transformation & integration Contract elements Central model SOA / CBSE Platform model Platform model Platform model Platform model Platform model

  12. Technologies and tools Environnement Eclipse Kerméta

  13. Expected results and planning • Results • Application development process • Towards bringing component and service worlds closer • Contract integration during the whole solftware life-cycle • Contract checking in component and service platforms • Planning • Mid-2009: validation on the three applications • Currently, the metamodels are almost complete and transformations are under development with Kermeta Not enough time to assess the whole process

  14. Lessons learned • MDA/MDE and Validation • Real use cases (business models) vs. Real running applications • Difficulty to stabilize business METAmodel • (Some) possible future works • Service Component Architecture (SCA) as a target • Contract violation (autonomic computing)

More Related