SOFA 2 Component Model Tomáš Bureš, Petr Hnětynka, František Plášil CHARLES UNIVERSITY PRAGUE Faculty of Mathematics and Physics Czech Republic.

Slides:



Advertisements
Similar presentations
Verification/Simulati on –GUI for simulation and formal verification –Simulator: Exploration of dynamic behavior Checking.
Advertisements

® IBM Software Group © 2006 IBM Corporation Rational Software France Object-Oriented Analysis and Design with UML2 and Rational Software Modeler 04. Other.
Page 1 Building Reliable Component-based Systems Chapter 16 - Component based embedded systems Chapter 16 Component based embedded systems.
Component Models and Technology Component-based Software Engineering
1 © Wolfgang Pelz UML3 UML 3 Notations describe how to use reusable software. Package Component Deployment Node.
Presented by IBM developer Works ibm.com/developerworks/ 2006 January – April © 2006 IBM Corporation. Making the most of Creating Eclipse plug-ins.
JSLEE. What is JSLEE ? is an event oriented application middleware. Its main job is to receive events from external resources and deliver these events.
Software Engineering Module 1 -Components Teaching unit 3 – Advanced development Ernesto Damiani Free University of Bozen - Bolzano Lesson 2 – Components.
WebDynpro for ABAP Short introduction.
Page 1, July 3, 2015 CBSE – graduate course Component-Based Software Engineering Building reliable component-based systems Overview
Institute for Software Research©2001, University of California, Irvine Product-Line Architectures André van der Hoek Institute for Software Research University.
QoS-enabled middleware by Saltanat Mashirova. Distributed applications Distributed applications have distinctly different characteristics than conventional.
February Semantion Privately owned, founded in 2000 First commercial implementation of OASIS ebXML Registry and Repository.
THE GITB TESTING FRAMEWORK Jacques Durand, Fujitsu America | December 1, 2011 GITB |
Introduction to MDA (Model Driven Architecture) CYT.
2nd TTCN-3 User Conference, June The TTCN-3 Metamodel – A Basis for Tool Integration Ina Schieferdecker TU Berlin/Fraunhofer Fokus Hajo Eichler,
Contents 1.Introduction, architecture 2.Live demonstration 3.Extensibility.
Comparing JavaBeans and OSGi Towards an Integration of Two Complementary Component Models HUMBERTO CERVANTES JEAN-MARIE FAVRE 09/02.
Component frameworks Roy Kensmil. Historical trens in software development. ABSTRACT INTERACTIONS COMPONENT BUS COMPONENT GLUE THIRD-PARTY BINDING.
Slide title In CAPITALS 50 pt Slide subtitle 32 pt Model based development for the RUNES component middleware platform Gabor Batori
Performance evaluation of component-based software systems Seminar of Component Engineering course Rofideh hadighi 7 Jan 2010.
TAL7011 – Lecture 4 UML for Architecture Modeling.
07/09/04 Johan Muskens ( TU/e Computer Science, System Architecture and Networking.
Grid programming with components: an advanced COMPonent platform for an effective invisible grid © 2006 GridCOMP Grids Programming with components. An.
Distribution and components. 2 What is the problem? Enterprise computing is Large scale & complex: It supports large scale and complex organisations Spanning.
1. 2 Objects to Distributed Components (1) Typed Group Java or Active Object ComponentIdentity Cpt = newActiveComponent (params); A a = Cpt ….getFcInterface.
Page 1, December 8, 2015 CBSE – graduate course Component-Based Software Engineering Building reliable component-based systems Overview
ProActive components and legacy code Matthieu MOREL.
1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.
Tomás BarrosMonday, April 18, 2005FIACRE Toulouse p. 1 Behavioural Models for Hierarchical Components Tomás Barros, Ludovic Henrio and Eric Madelaine.
1 Introduction to Service Component Architecture Feature Pack for WebSphere Application Server & SCA Tooling in RAD Mike Edwards and Sara Mitchell - IBM.
Software Reuse. Objectives l To explain the benefits of software reuse and some reuse problems l To discuss several different ways to implement software.
UML Diagrams By Daniel Damaris Novarianto S..
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Self Healing and Dynamic Construction Framework:
SysML v2 Formalism: Requirements & Benefits
Overall Architecture and Component Model
The GEMBus Architecture and Core Components
Behavioural Models for Distributed Hierarchical Components
Software Reuse ©Ian Sommerville 2006.
Distribution and components
UML Diagrams Jung Woo.
Flexible Extensible Digital Object Repository Architecture
Flexible Extensible Digital Object Repository Architecture
Presented by Jinpeng Zhou
Krishnakumar Balasubramanian
The Extensible Tool-chain for Evaluation of Architectural Models
Applying Domain-Specific Modeling Languages to Develop DRE Systems
Component-Based Software Engineering: Technologies, Development Frameworks, and Quality Assurance Schemes X. Cai, M. R. Lyu, K.F. Wong, R. Ko.
Component-Based Software Engineering
Distributed System Using Java 2 Enterprise Edition (J2EE)
SwE 455 Tutorial.
Tools for Composing and Deploying Grid Middleware Web Services
System Concept Simulation for Concurrent Engineering
Evaluating Compuware OptimalJ as an MDA tool
Component--based development
More Model Elements.
ESIS Consulting LLC (C) ESIS Consulting LLC. All rights reserved
Module 01 ETICS Overview ETICS Online Tutorials
JavaServer Faces: The Fundamentals
Architecture Description Languages
Constructing MDA-based Application Using Rational XDE for .NET
An Introduction to Software Architecture
Chapter 7 –Implementation Issues
MDT UML2Tools 0.8 Mini-deck
Automated Analysis and Code Generation for Domain-Specific Models
COMPONENT – BASED SOFTWARE ENGINEERING MODULE 2 – SECOND SEMESTER MKHIZE, BSC HONS COMPUTER SCIENCES, DIP IT, ICDL.
ONAP Architecture Principle Review
Software Architecture & Design
Presentation transcript:

SOFA 2 Component Model Tomáš Bureš, Petr Hnětynka, František Plášil CHARLES UNIVERSITY PRAGUE Faculty of Mathematics and Physics Czech Republic

SOFA 2 Component model Components in general ● A component ~ black-box entity ● Problem – every component system has its own definition of a component ● Component model the collection of the related abstractions, their semantics and the rules for component composition (through-out of all the component application phases) ● The concept of a “component” has always to be interpreted in the semantics of a particular component model

SOFA 2 Component model Components in general ● Key component abstractions interfaces ● provide & required bindings ● direct vs. via connectors ● Types of composition flat ● one level of nesting hierarchical ● Development lifecycle component lifecycle ● development of separated components application lifecycle ● assembling components together

SOFA 2 Component model Components in general ● Many component systems exit JavaBeans EJB CCM COM/DCOM Darwin Wright C2 ACME Koala Robocop Fractal SOFA 2 ArchJava Java/A ProCom.....

SOFA 2 Component model SOFA 2 components ● Components defined by component type (called frame) ● defines component's provided and required interfaces interfaces defined by interface types ● defines component's behavior component implementation (called architecture) ● glass-box view ● implements a frame ● either primitive or composite directly implemented or composed of other components at runtime – architectures are instantiated ● there can be multiple instances of a single architecture

SOFA 2 Component model Development with components ● Split to two parallel activities Component development ● Component types, contracts, implementations, etc. ● Components in a repository ● Multiple versions possible System development ● (Re)Use of components ● Their integration in an application Repository Development environment Adding new components Using existing components

SOFA 2 Component model SOFA 2 component/application lifecycle 1.Development (of components) composing existing components together ● components stored in the repository newly developed ones also stored in the repository 2.Assembly (of an application) subcomponents primarily defined by frames recursively replacing frames by architectures 3.Deployment and executing (of an application) where particular components have to be executed ● information stored in a deployment plan connector generation applying control aspects execution

SOFA 2 Component model Runtime environment ● Runtime environment (called SOFAnode) consists of several units repository deployment docks dock registry global connector manager Deploymen t Node 2 Repository DockA DockB DockC DockD Developing new components Uploading new components Deploymen t Node 3 Deploymen t Node 1

SOFA 2 Component model Runtime environment ● Runtime environment (called SOFAnode) consists of several units repository deployment docks dock registry global connector manager Deploymen t Node 2 Repository DockA DockB DockC DockD Developing new components Uploading new components Deploymen t Node 3 Deploymen t Node 1  Generated from the EMF meta-model  Eclipse Modeling Framework  de-facto standard for defining meta-models  Remotely accessible  Supports versioning  Used at both development time and run time

SOFA 2 Component model Runtime environment ● Runtime environment (called SOFAnode) consists of several units repository deployment docks dock registry global connector manager Deploymen t Node 2 Repository DockA DockB DockC DockD Developing new components Uploading new components Deploymen t Node 3 Deploymen t Node 1  A container executing components  Automatically downloads code of components from the repository

SOFA 2 Component model Runtime environment ● Runtime environment (called SOFAnode) consists of several units repository deployment docks dock registry global connector manager Deploymen t Node 2 Repository DockA DockB DockC DockD Developing new components Uploading new components Deploymen t Node 3 Deploymen t Node 1  Inter-component links by automatically generated connectors  Seamless distribution  Different communication styles ~ middleware

SOFA 2 Component model Runtime environment ● Runtime environment (called SOFAnode) consists of several units repository deployment docks dock registry global connector manager Deploymen t Node 2 Repository DockA DockB DockC DockD Developing new components Uploading new components Deploymen t Node 3 Deploymen t Node 1  Components' content weaved with component aspects  The way of parameterizing the runtime platform

SOFA 2 Component model Current status ● Implementation available LGPL license ● All features are implemented repository, docks,... development tools ● IDE + cmd-line

SOFA 2 Component model Future/current work ● Extra-functional properties of components performance models resource consumption Q-Impress (FP7 STREP) ● Supporting dynamic architectures i.e. changes of an architecture at run-time mainly for hierarchical component models

SOFA 2 Component model Future/current work ● SOFA “profiles” (modularization) core – determines a generic part of SOFA Component model, Control part, Assembly, Deploy, Repository specific profiles – restrict/enhance the core according to requirements of a target environment (implementation language, limited runtime,...) SOFA-HI for real-time software ● Component framework as product-line (meta- component system) configure features of component framework according to requirements on an application configure ● meta-model (via profiles) ● runtime environment ● support tools