MAY Terminology » Historique » Version 1
Anonyme, 10/10/2014 14:24
| 1 | 1 | Anonyme | h1. SpeADL Terminology |
|---|---|---|---|
| 2 | |||
| 3 | {{>toc}} |
||
| 4 | |||
| 5 | h2. Software Component |
||
| 6 | |||
| 7 | h3. Interface |
||
| 8 | |||
| 9 | An interface is a collection of operations. |
||
| 10 | In Java, interfaces are collections of methods. |
||
| 11 | They are referred to with a name. |
||
| 12 | |||
| 13 | h3. Component Port |
||
| 14 | |||
| 15 | A port in a component has a name and an interface. |
||
| 16 | If it is provided, it must answer call to the operations of the interface. |
||
| 17 | If it is required, it can be used from within the component to call operations of the interfaces without knowing who provides them. |
||
| 18 | |||
| 19 | h3. Component Type |
||
| 20 | |||
| 21 | A component type has a name and a collection of ports. |
||
| 22 | It represents a component from the exterior: this is all that can be accessed from outside the component. |
||
| 23 | |||
| 24 | h3. Component Implementation |
||
| 25 | |||
| 26 | An component implementation contains an actual realisation of the provided port of the component, potentially by using the required ports of the component. |
||
| 27 | |||
| 28 | h3. Component Part |
||
| 29 | |||
| 30 | A part is a member of a component and that is itself a component. |
||
| 31 | Its required ports must be connected to a port providing the interface, and its provided ports are available from within the containing component. |
||
| 32 | |||
| 33 | h3. Configuration |
||
| 34 | |||
| 35 | A configuration is a composition of component parts. |
||
| 36 | A configuration acts as an implementation for a component. |
||
| 37 | A configuration is valid when all the required ports of its part are connected to ports with the correct interface. |
||
| 38 | |||
| 39 | h3. Component Class |
||
| 40 | |||
| 41 | A component class is at the same time a type and an implementation. |
||
| 42 | It can sometimes be defined in multiple files (for example SpeADL and Java). |
||
| 43 | |||
| 44 | h3. Component Instance |
||
| 45 | |||
| 46 | A component instance is a runtime entity that exposes the type of its class and realise this type using the implementation of its class. |
||
| 47 | A component instance contains a component instance for each of its parts. |
||
| 48 | |||
| 49 | h2. SpeADL Component |
||
| 50 | |||
| 51 | In SpeADL, a component is made of a definition and a Java implementation |
||
| 52 | |||
| 53 | h3. Component Definition |
||
| 54 | |||
| 55 | A component definition is a SpeADL definition of a component type and optionally of a component implementation in the form of a configuration. |
||
| 56 | |||
| 57 | h3. Component Java Implementation |
||
| 58 | |||
| 59 | A component implementation is a Java implementation of a component definition. |
||
| 60 | It contains implementations for the provided ports, a definition of the Java implementation for the parts and optionally implementation of the initialisation of the component. |
||
| 61 | |||
| 62 | h3. Component Instance |
||
| 63 | |||
| 64 | A component instance is created from the component implementation. |
||
| 65 | |||
| 66 | h2. Ecosystem |
||
| 67 | |||
| 68 | An ecosystem is a component with species. |
||
| 69 | |||
| 70 | h3. Ecosystem Definition |
||
| 71 | |||
| 72 | See Component Definition. |
||
| 73 | On top of that, it contains also species. |
||
| 74 | |||
| 75 | h3. Ecosystem Java Implementation |
||
| 76 | |||
| 77 | See [[SpeADL Terminology#Component Java Implementation|Component Java Implementation]]. |
||
| 78 | |||
| 79 | h2. Species |
||
| 80 | |||
| 81 | A species is a component that can only be defined inside an ecosystem. |
||
| 82 | |||
| 83 | h3. Species |
||
| 84 | |||
| 85 | h3. Species Definition |
||
| 86 | |||
| 87 | h3. Species Implementation |
||
| 88 | |||
| 89 | h3. Species Instance |