-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy patharchimate.html
309 lines (219 loc) · 14.9 KB
/
archimate.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
<!DOCTYPE html>
<html>
<head>
<title>ArchiMate Ontology</title>
<style>
body {
padding: 2em 1em 2em 70px;
margin: 0;
font-family: sans-serif;
color: black;
background: white;
background-position: top left;
background-attachment: fixed;
background-repeat: no-repeat;
}
:link { color: #00C; background: transparent }
:visited { color: #609; background: transparent }
a:active { color: #C00; background: transparent }
a:link img, a:visited img { border-style: none }
th, td { /* ns 4 */
font-family: sans-serif;
}
h1, h3, h3, h4, h5, h6 { text-align: left }
h1, h3, h3 { color: #005A9C; background: white }
h1 { font: 170% sans-serif }
h3 { font: 140% sans-serif }
h3 { font: 120% sans-serif }
h4 { font: bold 100% sans-serif }
h5 { font: italic 100% sans-serif }
h6 { font: small-caps 100% sans-serif }
.hide { display: none }
div.head { margin-bottom: 1em }
div.head h1 { margin-top: 2em; clear: both }
div.head table { margin-left: 2em; margin-top: 2em }
</style>
</head>
<body>
<div class="head">
<p>
<a href="">
<img width="" height="" alt="" src=""/>
</a>
</p>
<h1>ArchiMate Ontology</h1>
</div>
<p>This is the namespace for use with ArchiMate 3.2. Ontology</p>
<h2>Versioning</h2>
<p>Version of the ontology can be found in the OWL attribute owl:versionInfo</p>
<p>Root namespace will resolve to the latest version of the the ontology and specification. Alternative versions can be found in the following folders.</p>
<p>https://purl.org/archimate/html</p>
<p>https://purl.org/archimate/owl</p>
<p>https://purl.org/archimate/skos</p>
<h2>Vocabulary</h2>
<h3><a name="ArchiMate"></a>ArchiMate</h3>
<p>ArchiMate Enterprise Architecture modeling language, a visual language with a set of default iconography for describing, analyzing, and communicating many concerns of Enterprise Architectures as they change over time. The standard provides a set of entities and relationships with their corresponding iconography for the representation of Architecture Descriptions.</p>
<h3><a name="EnterpriseArchitecture"></a>Enterprise Architecture</h3>
<p>The practice of analyzing, designing, planning, and implementing enterprise analysis to successfully execute on business strategies.</p>
<h3><a name="VisualLanguage"></a>Visual Language</h3>
<p>A type of language that uses visual elements to convey meaning.</p>
<h3><a name="ArchiMateCoreFramework"></a>ArchiMate Core Framework</h3>
<p>A reference structure used to classify elements of the ArchiMate core language. It consists of three layers and three aspects.</p>
<h3><a name="ArchiMateCoreLanguage"></a>ArchiMate Core Language</h3>
<p>The central part of the ArchiMate language that defines the concepts to model Enterprise Architectures. It includes concepts from three layers: Business, Application, and Technology (including Physical).</p>
<h3><a name="ArchitectureView"></a>Architecture View</h3>
<p>A representation of a system from the perspective of a related set of concerns.</p>
<h3><a name="ArchitectureViewpoint"></a>Architecture Viewpoint</h3>
<p>A specification of the conventions for a particular kind of architecture view.</p>
<h3><a name="Aspect"></a>Aspect</h3>
<p>Classification of elements based on layer-independent characteristics related to the concerns of different stakeholders. Used for positioning elements in the ArchiMate metamodel.</p>
<h3><a name="Attribute"></a>Attribute</h3>
<p>A property associated with an ArchiMate language element or relationship.</p>
<h3><a name="Model"></a>Model</h3>
<p>A model contains elements and relationships within an architecture.</p>
<h3><a name="Concept"></a>Concept</h3>
<p>A conceptual entity within the ArchiMate modeling language.</p>
<h3><a name="Element"></a>Element</h3>
<p>A fundamental building block within an architecture model.</p>
<h3><a name="CompositeElement"></a>CompositeElement</h3>
<p>An element that does not necessarily fit in a single aspect of the framework but may combine two or more aspects.</p>
<h3><a name="ActiveStructure"></a>Active Structure</h3>
<p>A category of elements that perform behavior and collaborate to provide services.</p>
<h3><a name="ExternalActiveStructure"></a>External Active Structure</h3>
<p>A category of external active structure elements (also called interfaces) that perform behavior and collaborate to provide services.</p>
<h3><a name="InternalActiveStructure"></a>Internal Active Structure</h3>
<p>A category of internal elements that perform behavior and collaborate to provide services.</p>
<h3><a name="Behavior"></a>Behavior</h3>
<p>Represents elements that define the behavior performed by active structure elements.</p>
<h3><a name="ExternalBehavior"></a>External Behavior</h3>
<p>Represents external elements (also called services) that define the behavior performed by active structure elements.</p>
<h3><a name="InternalBehavior"></a>Internal Behavior</h3>
<p>Represents internal elements that define the behavior performed by active structure elements.</p>
<h3><a name="Event"></a>Event</h3>
<p>Represents elements that define the behavior performed by active structure elements.</p>
<h3><a name="PassiveStructure"></a>Passive Structure</h3>
<p>Represents structural elements that are used or produced by behavior elements.</p>
<h3><a name="Layer"></a>Layer</h3>
<p>A major division in the architecture that categorizes elements according to their scope and purpose.</p>
<h3><a name="BusinessLayer"></a>Business Layer</h3>
<p>Represents elements and relationships that describe the organization's business functions and processes.</p>
<h3><a name="ApplicationLayer"></a>Application Layer</h3>
<p>Represents elements and relationships that describe the organization's business functions and processes.</p>
<h3><a name="Relationship"></a>Relationship</h3>
<p>A relationship between two elements within an architecture model.</p>
<h3><a name="RelationshipConnector"></a>Relationship Connector</h3>
<p>A connector element that connects relationships between elements.</p>
<h3><a name="StructuralRelationship"></a>Structural Relationship</h3>
<p>A structural relationship defines the static construction or composition of concepts.</p>
<h3><a name="DependencyRelationship"></a>Dependency Relationship</h3>
<p>A dependency relationship models how elements depend on each other.</p>
<h3><a name="DynamicRelationship"></a>Dynamic Relationship</h3>
<p>A dynamic relationship models behavioral dependencies between elements.</p>
<h3><a name="OtherRelationship"></a>Other Relationship</h3>
<p>Other types of relationships not covered by structural, dependency, or dynamic relationships.</p>
<h2>Classes</h2>
<h3><a name="BusinessActor"></a>Business Actor</h3>
<p>An organizational entity that is capable of performing behavior.</p>
<h3><a name="BusinessRole"></a>Business Role</h3>
<p>The responsibility for performing specific behavior, to which an actor can be assigned.</p>
<h3><a name="BusinessCollaboration"></a>Business Collaboration</h3>
<p>An aggregate of two or more business roles that work together to perform collective behavior.</p>
<h3><a name="BusinessInterface"></a>Business Interface</h3>
<p>A point of access where a business service is made available to the environment.</p>
<h3><a name="BusinessProcess"></a>Business Process</h3>
<p>A sequence of business behaviors that achieve a specific outcome.</p>
<h3><a name="BusinessFunction"></a>Business Function</h3>
<p>A collection of business behavior based on a chosen set of criteria (typically required skills, resources, etc.) and closely aligned to an organization.</p>
<h3><a name="BusinessService"></a>Business Service</h3>
<p>An explicitly defined exposed business behavior.</p>
<h3><a name="BusinessInteraction"></a>Business Interaction</h3>
<p>A unit of collective business behavior performed by two or more business actors, business roles, or business collaborations.</p>
<h3><a name="BusinessEvent"></a>Business Event</h3>
<p>Represents a business-related state change.</p>
<h3><a name="BusinessObject"></a>Business Object</h3>
<p>Represents a concept used within a particular business domain.</p>
<h3><a name="BusinessContract"></a>Business Constract</h3>
<p>Represents a formal or informal specification of an agreement between a provider and a consumer that specifies the rights and obligations associated with a product and establishes functional and non-functional parameters for interaction.</p>
<h3><a name="Representation"></a>Representation</h3>
<p>A perceptible form of the information carried by a business object.</p>
<h3><a name="Product"></a>Product</h3>
<p>Represents a coherent collection of services and/or passive structure elements, accompanied by a contract, which is offered as a whole to (internal or external) customers.</p>
<h3><a name="ApplicationComponent"></a>Application Component</h3>
<p>An encapsulation of application functionality aligned to implementation structure, which is modular and replaceable.</p>
<h3><a name="ApplicationCollaboration"></a>Application Collaboration</h3>
<p>Represents an aggregate of two or more application internal active structure elements that work together to perform collective application behavior.</p>
<h3><a name="ApplicationInterface"></a>Application Interface</h3>
<p>Represents a point of access where application services are made available to a user, another application component, or a node.</p>
<h3><a name="ApplicationFunction"></a>Application Function</h3>
<p>Represents an automated behavior that can be performed by an application component.</p>
<h3><a name="ApplicationInteraction"></a>Application Interaction</h3>
<p>an encapsulation of application functionality aligned to implementation structure, which is modular and replaceable.</p>
<h3><a name="ApplicationProcess"></a>Application Process</h3>
<p>Addresses a set of related concerns and is tailored for specific stakeholders. A View is specified by means of a Viewpoint, which prescribes the concepts, models, analysis techniques, and visualizations that are provided by the View. The same elements from the Model Tree can be re-used multiple times in the same or different View.</p>
<h3><a name="ApplicationService"></a>Application Service</h3>
<p>represents an explicitly defined exposed application behavior.</p>
<h3><a name="DataObject"></a>Data Object</h3>
<p>Represents data structured for automated processing.</p>
<h3><a name="Node"></a>Node</h3>
<p>A computational or physical resource that hosts, manipulates, or interacts with other computational or physical resources.</p>
<h3><a name="Device"></a>Device</h3>
<p>A physical IT resource upon which system software and artifacts may be stored or deployed for execution.</p>
<h3><a name="SystemSoftware"></a>System Software</h3>
<p>Software that provides or contributes to an environment for storing, executing, and using software or data deployed within it.</p>
<h3><a name="TechnologyCollaboration"></a>Technology Collaboration</h3>
<p>An aggregate of two or more technology internal active structure elements that work together to perform collective technology behavior.</p>
<h3><a name="TechnologyInterface"></a>Technology Interface</h3>
<p>A technology collaboration represents an aggregate of two or more technology internal active structure elements that work together to perform collective technology behavior.</p>
<h3><a name="Path"></a>Path</h3>
<p>A link between two or more technology internal active structure elements, through which these elements can exchange data, energy, or material.</p>
<h3><a name="CommunicationNetwork"></a>Communication Network</h3>
<p>A set of structures that connects devices or system software for transmission, routing, and reception of data.</p>
<h3><a name="TechnologyFunction"></a>Technology Function</h3>
<p>A collection of technology behavior that can be performed by a technology internal active structure element.</p>
<h3><a name="TechnologyProcess"></a>Technology Process</h3>
<p>A sequence of technology behaviors that achieves a specific result.</p>
<h3><a name="TechnologyInteraction"></a>Technology Interaction</h3>
<p>A unit of collective technology behavior performed by (a collaboration of) two or more technology internal active structure elements.</p>
<h3><a name="TechnologyEvent"></a>Technology Event</h3>
<p>A technology event represents a technology state change.</p>
<h3><a name="TechnologyService"></a>Technology Service</h3>
<p>An explicitly defined exposed technology behavior.</p>
<h3><a name="Artifact"></a>Artifact</h3>
<p>A piece of data that is used or produced in a software development process, or by deployment and operation of an IT system.</p>
<h2>Properties</h2>
<h3><a name="Assignment"></a>Assignment</h3>
<p>Links active structure elements with units of behavior that are performed by them, or roles that are fulfilled by them.</p>
<h3><a name="Aggregation"></a>Aggregation</h3>
<p>Models a whole-part relationship between a composite and its parts.</p>
<h3><a name="Composition"></a>Composition</h3>
<p>Indicates that an element consists of one or more other elements.</p>
<h3><a name="Realization"></a>Realization</h3>
<p>Indicates that an entity (e.g., a business process or function) realizes another entity (e.g., a business service).</p>
<h3><a name="Serving"></a>Serving</h3>
<p>Models that an element provides its functionality to another element.</p>
<h3><a name="Access"></a>Access</h3>
<p>Models the access of a behavior element to a passive structure element.</p>
<h3><a name="Read"></a>Read</h3>
<p>Indicates that a behavior element reads or retrieves information from a passive structure element.</p>
<h3><a name="Write"></a>Write</h3>
<p>Indicates that a behavior element writes or modifies information in a passive structure element.</p>
<h3><a name="ReadWrite"></a>Read-Write</h3>
<p>Indicates that a behavior element both reads from and writes to a passive structure element.</p>
<h3><a name="Influence"></a>Influence</h3>
<p>Models how an element influences another element.</p>
<h3><a name="Sign"></a>Sign</h3>
<p>Indicates the sign of the influence (e.g., positive or negative).</p>
<h3><a name="Strength"></a>Strength</h3>
<p>Indicates the strength of the influence (e.g., weak, moderate, strong).</p>
<h3><a name="Association"></a>Association</h3>
<p>Models a relationship between objects that is not covered by the other relationship types.</p>
<h3><a name="Triggering"></a>Triggering</h3>
<p>Models the temporal or causal relationship between two behavior elements, where one triggers the other.</p>
<h3><a name="Flow"></a>Flow</h3>
<p>The flow relationship represents transfer from one element to another.</p>
<h3><a name="Specialization"></a>Specialization</h3>
<p>Indicates that an element is a more specific form of another element of the same type.</p>
<h3><a name="Copyright"></a>Copyright</h3>
<p>All trademarks and copyrights belong to The Open Group</p>
</body>
</html>