logging in or signing up uml2003workshop Sudiksha Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 41 Category: Entertainment License: All Rights Reserved Like it (0) Dislike it (0) Added: October 29, 2007 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript Slide1: The OMEGA Component Model UML2003 Workshop - San Francisco, october 21 1The General Idea: The General Idea OMEGA Component is a Module with exported and imported services Structuring of: - classes - services - associations Interaction via operation calls and signals No component instances (suite of services)The Design Idea: The Design Idea Components are Runtime Configurable Entities making possible: Aspect Oriented Programming Role Based Design A better design process: Use Cases CRC Cards Components Classes Basic Component meta model: Basic Component meta model Blackbox Component Basic Component Omega class UML class Provided Component Interface Required Component Interface UML realization relation 1 1 * * * * UML Interface UML dependency relation Component System meta model: Component System meta model Blackbox Component Component System UML Namespace Provided Component Interface Required Component Interface UML realization relation UML dependency relation 1 1 * * * * UML Interface Blackbox Component 1 *Basic Component: Basic Component is a tuple (N, C, P, R, Rel) where N: component name C: class definitions P: provided interfaces R: required interfaces allowing object creation Rel: relations including a realization relation: p C x P a dependency relation: r C x R Encapsulation: P R is type-compatible Blackbox Component: Blackbox Component is a tuple (N, P, R) where N: component name P: exported provided interfaces R: imported required interfacesComponent System: Component System is a tuple (N, I, conn, P, R) where N: system name I: set of internal blackbox components conn: R(I) P(I) where R(I)= { i.R| iI} P(I)= { i.P| iI} such that conn(r)=p implies r p P P(I) and R R(I)Reduction to the Kernel Model: Reduction to the Kernel Model Introduce a directed neighbour relation between any two classes c and c' such that c r r and c' p p conn(r)=p Component Behaviour: Trace semantics: Component Behaviour: Trace semantics Operation Call: (sender, receiver, op(parameters)) Signal Emission: (sender, receiver, signal(parameters)) Return: (sender, receiver, op.result(value))Protocol State machines: Protocol State machines Action Language: x := create(r), where r is a required interface x := expression y := x.op(parameters), where op is a required operation return(op, x, expression) where op is a provided operation triggered operations only involve provided operationsEvaluation and discussion: Evaluation and discussion Compatible with the OMEGA kernel model A higher level of abstraction Modeling (multithreading) Compositional specification and verification Programming to interfaces Compatible with UML 2.0 You do not have the permission to view this presentation. In order to view it, please contact the author of the presentation.
uml2003workshop Sudiksha Download Post to : URL : Related Presentations : Share Add to Flag Embed Email Send to Blogs and Networks Add to Channel Uploaded from authorPOINTLite Insert YouTube videos in PowerPont slides with aS Desktop Copy embed code: (To copy code, click on the text box) Embed: URL: Thumbnail: WordPress Embed Customize Embed The presentation is successfully added In Your Favorites. Views: 41 Category: Entertainment License: All Rights Reserved Like it (0) Dislike it (0) Added: October 29, 2007 This Presentation is Public Favorites: 0 Presentation Description No description available. Comments Posting comment... Premium member Presentation Transcript Slide1: The OMEGA Component Model UML2003 Workshop - San Francisco, october 21 1The General Idea: The General Idea OMEGA Component is a Module with exported and imported services Structuring of: - classes - services - associations Interaction via operation calls and signals No component instances (suite of services)The Design Idea: The Design Idea Components are Runtime Configurable Entities making possible: Aspect Oriented Programming Role Based Design A better design process: Use Cases CRC Cards Components Classes Basic Component meta model: Basic Component meta model Blackbox Component Basic Component Omega class UML class Provided Component Interface Required Component Interface UML realization relation 1 1 * * * * UML Interface UML dependency relation Component System meta model: Component System meta model Blackbox Component Component System UML Namespace Provided Component Interface Required Component Interface UML realization relation UML dependency relation 1 1 * * * * UML Interface Blackbox Component 1 *Basic Component: Basic Component is a tuple (N, C, P, R, Rel) where N: component name C: class definitions P: provided interfaces R: required interfaces allowing object creation Rel: relations including a realization relation: p C x P a dependency relation: r C x R Encapsulation: P R is type-compatible Blackbox Component: Blackbox Component is a tuple (N, P, R) where N: component name P: exported provided interfaces R: imported required interfacesComponent System: Component System is a tuple (N, I, conn, P, R) where N: system name I: set of internal blackbox components conn: R(I) P(I) where R(I)= { i.R| iI} P(I)= { i.P| iI} such that conn(r)=p implies r p P P(I) and R R(I)Reduction to the Kernel Model: Reduction to the Kernel Model Introduce a directed neighbour relation between any two classes c and c' such that c r r and c' p p conn(r)=p Component Behaviour: Trace semantics: Component Behaviour: Trace semantics Operation Call: (sender, receiver, op(parameters)) Signal Emission: (sender, receiver, signal(parameters)) Return: (sender, receiver, op.result(value))Protocol State machines: Protocol State machines Action Language: x := create(r), where r is a required interface x := expression y := x.op(parameters), where op is a required operation return(op, x, expression) where op is a provided operation triggered operations only involve provided operationsEvaluation and discussion: Evaluation and discussion Compatible with the OMEGA kernel model A higher level of abstraction Modeling (multithreading) Compositional specification and verification Programming to interfaces Compatible with UML 2.0