1 / 11

ENT: A Generic Meta-Model for the description of Component - based Applications

Jaroslav Šnajberk , Přemek Brada Computer of Computer Sciences and Engineering Faculty of Applied Sciences University of West Bohemia in Pilsen. ENT: A Generic Meta-Model for the description of Component - based Applications. Agenda. Introduction Basics of the ENT meta-model

zarita
Download Presentation

ENT: A Generic Meta-Model for the description of Component - based Applications

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. Jaroslav Šnajberk, Přemek Brada ComputerofComputerSciencesandEngineering FacultyofAppliedSciences University ofWest Bohemia in Pilsen ENT: A Generic Meta-Model forthedescriptionofComponent-basedApplications

  2. Agenda Introduction Basicsofthe ENT meta-model How to describecomponent model with ENT How to describeapplicationwith ENT

  3. Component-basedworld • Dozensofcomponentmodels • Differentapproaches to components • Generaldescriptiondoesn’t describealltheaspects • Inicializationisneeded (eg UML profiles) • Differentroles in componentdevelopmentlifecyclehavedifferentneeds

  4. The ENT meta-model Describes component model to provide meta information for description of application Description of component model is made to reflex all important information Uses classification system Enablesfutureautomatiziationoffiltering / analyzing / highlighting

  5. ENT classification Nature = {syntax, semantics, extra-functional} Kind = {operational, data} Role = {provided, required, neutral} Granularity = {item, structure, compound} Construct = {constant, instance, type} Presence = {mandatory, permanent, optional} Arity = {single, multiple} Lifecycle = {development, assembly, deployment, setup, runtime}

  6. Descriptionofcomponent model • Analyst • Has to understand CM • Evaluatesneeds • OSGi • Iscomposedfrombundles • Bundleshaveversionsanddefinitions in manifest • Communicationthroughservices

  7. Descriptionof single component Bundle-Name: cz.zcu.Addressbook Bundle-Version: 1.3.1 Require-Bundle: cz.zcu.Portal Export-Package: cz.zcu.address Import-package: org.osgi.web;version="1.2.0"

  8. Relations betweencomponents • Bindings • Element-Element • Component-Element • Component-Element • Component-Component • Subcomponents • Hierarchicaldecomposition

  9. Summary • OSGiapplicationdescribed by ENT • Anyothercomponent-basedapplicationcanbedescribed by ENT • Thefinal ENT model isreadyfor use by computer • Itcanfiltertraits by theircharacteristics • Itcanbeused in visualization, analytics, comparison

  10. Futurework • Componentapplicationvisualizer • ENT works as a data layer • Advancedvisualization style • Differentrepresentationofcomponent, relations and layout • Interactionwith user • Highlightingandfilteringbased on usersneeds • Unlimitednumberofothervisualizationstyles • Experimental

  11. Thankyou

More Related