ASCoDT Component Specification: Difference between revisions

From Sccswiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 1: Line 1:
For the specification of components, ports and interfaces we use a simplified version of SIDL. The grammar for the simplified language can be downloaded from [[File:grammer.doc]]. The language in our implementation is meant only for prototyping purposes. It supports only a small set of types, which are crucial for scientific applications.  
For the specification of components, ports and interfaces we use a simplified version of SIDL. The grammar for the simplified language can be downloaded from [[File:grammer.doc]]. The language in our implementation is meant only for prototyping purposes. It supports only a small set of types, which are crucial for scientific applications.  
= SIDL - Short Introduction =
= SIDL - Short Introduction =
A component in ASCoDT is an autonomous soft-
ware entity with a state and an interface. Multiple instances of one component may
exist. Hence, a component is similar to an object of a class, and we use class as
synonym for component definitions. Our components can be distributed among different computers running in processes or applications, respectively, of their own. The
static structure of our applications consists of interfaces and classes, i.e. components
interacting due to these interfaces. Both are organised in packages mirroring the
namespace concept of C++ and Java. Interfaces prescribe a signature, i.e. comprise
methods, and they can extend other interfaces. A class implements interfaces and uses
interfaces. Whenever a class implements an interface, the class has a provides port.
The port’s type is given by the interface. Whenever a class uses another interface,
the class has a uses port. The port’s type is given by the interface. This static structure in our case is written down in a simplified scientific interface definition language
(simplified SIDL).
 
= Interfaces =
= Interfaces =
= Components =
= Components =

Revision as of 07:57, 14 September 2012

For the specification of components, ports and interfaces we use a simplified version of SIDL. The grammar for the simplified language can be downloaded from File:Grammer.doc. The language in our implementation is meant only for prototyping purposes. It supports only a small set of types, which are crucial for scientific applications.

SIDL - Short Introduction

A component in ASCoDT is an autonomous soft- ware entity with a state and an interface. Multiple instances of one component may exist. Hence, a component is similar to an object of a class, and we use class as synonym for component definitions. Our components can be distributed among different computers running in processes or applications, respectively, of their own. The static structure of our applications consists of interfaces and classes, i.e. components interacting due to these interfaces. Both are organised in packages mirroring the namespace concept of C++ and Java. Interfaces prescribe a signature, i.e. comprise methods, and they can extend other interfaces. A class implements interfaces and uses interfaces. Whenever a class implements an interface, the class has a provides port. The port’s type is given by the interface. Whenever a class uses another interface, the class has a uses port. The port’s type is given by the interface. This static structure in our case is written down in a simplified scientific interface definition language (simplified SIDL).

Interfaces

Components

Targets

Uses-ports

Provides-ports