Projet

Général

Profil

MAY Terminology » Historique » Version 7

Anonyme, 10/10/2014 15:13

1 1 Anonyme
h1. SpeADL Terminology
2
3
{{>toc}}
4
5 2 Anonyme
h2. MAY
6
7
MAY is a tool to build software components with SpeADL and Java.
8
9 1 Anonyme
h2. Software Component
10
11 6 Anonyme
A software component is at the same time the type of a component, an implementation of this type and an instance of the implementation that exposes the type.
12 1 Anonyme
13 2 Anonyme
h3. Component Class
14
15 1 Anonyme
A component class is at the same time a type and an implementation.
16 4 Anonyme
17
h3. Component Instance
18
19 5 Anonyme
A component instance is a runtime entity that exposes the type of its class and realise this type using the implementation of its class.
20 2 Anonyme
21
h2. Interface
22
23 1 Anonyme
In Java, interfaces are collections of methods.
24 7 Anonyme
An interface has a name and is located in a Java package.
25 1 Anonyme
26 7 Anonyme
h2. Namespace
27
28
A namespace plays the exact same role as a package in Java.
29
30 1 Anonyme
h2. SpeADL Component
31
32 7 Anonyme
With MAY, a component class is made of a SpeADL definition and a Java implementation.
33
It is located in a namespace.
34 1 Anonyme
35 2 Anonyme
h2. SpeADL Component Definition
36
37
A component definition is a SpeADL definition of a component type and optionally of a component implementation in the form of a configuration.
38
39 1 Anonyme
h3. Component Type
40
41
A component type has a name and a collection of ports.
42 2 Anonyme
It represents a component from the exterior: this is all that can be externally accessed from a component instance.
43 1 Anonyme
44 2 Anonyme
h3. Component Port
45 1 Anonyme
46 2 Anonyme
A port in a component has a name and an interface.
47
If it is provided, it must answer call to the operations of the interface.
48
If it is required, it can be used from within the component to call operations of the interfaces without knowing who provides them.
49 1 Anonyme
50
h3. Configuration
51
52
A configuration is a composition of component parts.
53
A configuration acts as an implementation for a component.
54
A configuration is valid when all the required ports of its part are connected to ports with the correct interface.
55
56 2 Anonyme
h3. Component Part
57 1 Anonyme
58 2 Anonyme
A part is a member of a component and that is itself a component.
59 1 Anonyme
60 2 Anonyme
It has a name and component type.
61
Its required ports must be connected to a port providing the interface, and its provided ports are available from within the containing component.
62 1 Anonyme
63 2 Anonyme
h2. Component Java Implementation
64 1 Anonyme
65
A component implementation is a Java implementation of a component definition.
66 2 Anonyme
It contains implementations for the provided ports, definitions of the Java implementations for the parts and optionally implementation of the initialisation of the component.
67 1 Anonyme
68 2 Anonyme
h2. Component Instance
69 1 Anonyme
70 2 Anonyme
A component instance is a runtime entity that exposes the type of its class and realise this type using the implementation of its class.
71
A component instance contains a component instance for each of its parts.
72
73 1 Anonyme
A component instance is created from the component implementation.
74
75
h2. Ecosystem
76
77
An ecosystem is a component with species.
78
79
h3. Ecosystem Definition
80
81 2 Anonyme
See [[SpeADL Terminology#Component Definition|Component Definition]].
82 1 Anonyme
On top of that, it contains also species.
83
84
h3. Ecosystem Java Implementation
85
86
See [[SpeADL Terminology#Component Java Implementation|Component Java Implementation]].
87 2 Anonyme
On top of that it contains definitions of the Java implementations for the species.
88 1 Anonyme
89
h2. Species
90
91
A species is a component that can only be defined inside an ecosystem.
92
93
h3. Species Definition
94
95 2 Anonyme
See [[SpeADL Terminology#Component Definition|Component Definition]].
96
On top of that, it can have parameters (separated by commas) and contain uses.
97
98
h3. Species Parameter
99
100
A species parameter has a name and a Java type.
101
102
h3. Use
103
104
A use is a part that can only be defined inside a species.
105
A use has a name but the only component type it can have must be a species declared in one of the parts of the ecosystem containing its species.
106
If the type of the use has parameters, then arguments for these parameters must be passed to it.
107
108 1 Anonyme
h3. Species Implementation
109
110 2 Anonyme
See [[SpeADL Terminology#Component Java Implementation|Component Java Implementation]].
111
Contrary to parts, a use implementation don't have to be defined as they are already defined in the implementation of the ecosystem containing the species of the use.
112
113 1 Anonyme
h3. Species Instance
114 2 Anonyme
115
A species can be instantiated only from within the ecosystem that defines it.