/
index.html
372 lines (344 loc) · 18.7 KB
/
index.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
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
<!DOCTYPE html>
<html>
<head>
<title>MAIA</title>
<link rel="stylesheet" href="css/SpryAccordion.css" />
<link rel="stylesheet" href="css/smoothness/jquery-ui-1.8.16.custom.css" />
<link rel="stylesheet" href="css/jquery.multiselect.css" />
<link rel="stylesheet" href="css/layout.css" />
<link rel="stylesheet" href="css/maia.css" />
<link rel="stylesheet" href="css/tipTip.css" />
<script src="js/SpryAccordion.js" type="text/javascript"></script>
<script src="js/jquery-1.7.1.min.js"></script>
<script src="js/jquery-ui-1.8.16.custom.min.js"></script>
<script src="js/jquery.multiselect.js"></script>
<script src="js/jquery.tipTip.minified.js"></script>
<script src="js/underscore-1.2.2.js"></script>
<script src="js/backbone.js"></script>
<script src="js/backbone-localstorage.js"></script>
<script type="text/javascript" src="js/raphael-min.js"></script>
<script type="text/javascript" src="js/dracula_graffle.js"></script>
<script type="text/javascript" src="js/dracula_graph.js"></script>
<script type="text/javascript" src="js/dracula_algorithms.js"></script>
<script src="js/utils.js"></script>
<script src="js/models.js"></script>
<script src="js/data.js"></script>
<script src="js/views.js"></script>
<script src="js/export.js"></script>
<script src="js/maia.js"></script>
</head>
<body>
<div class="container">
<div class="bannerArea">
<div class="bannersubnav">
<a href="javascript:void(0)" id="savemodel">Save</a>
<span class="separator">|</span>
<a href="javascript:void(0)" id="exportxml">Export XML</a> (<a href="javascript:void(0)" id="exportxmldownload">download</a>)
<span class="separator">|</span>
<a href="#about">About</a>
</div>
<div class="toplogo">
<img src="images/MAIAlogo.gif" />
</div>
<ul class="bannerNav">
<li>
<a href="#collective">Collective Structure</a>
</li>
<li>
<a href="#constitutional">Constitutional Structure</a>
</li>
<li>
<a href="#physical">Physical Structure</a>
</li>
<li>
<a href="#operational">Operational Structure</a>
</li>
<li>
<a href="#evaluative">Evaluative Structure</a>
</li>
</ul>
</div>
<div class="contentArea" id="about">
<div class="contentleft">
<h1>
MAIA
</h1>
<p>
MAIA is a conceptualization tool for developing agent-based models. The meta-model of this software is based on the Institutional Analysis and Development framework (IAD) by Ellinor Ostrom.
</p>
<p>
MAIA is aimed at socially complex systems. Following the sequence of tabs you will eventually have a conceptual model which you will be able to save for documentation and an XML file that you can use to produce Java code.
</p>
</div>
</div>
<div class="contentArea" id="constitutional">
<div id="SpryAccordion1" class="Accordion" tabindex="0">
<div class="AccordionPanel AccordionPanelOpen">
<div class="AccordionPanelTab">
Roles
</div>
<div class="AccordionPanelContent">
<div id="roles"></div>
<p class="footnote">¹ Separate multiple values with commas.</p>
</div>
</div>
<div class="AccordionPanel AccordionPanelClosed">
<div class="AccordionPanelTab">
Institutions
</div>
<div class="AccordionPanelContent">
<div id="institutions"></div>
</div>
</div>
<div class="AccordionPanel AccordionPanelClosed">
<div class="AccordionPanelTab">
Dependencies
</div>
<div class="AccordionPanelContent">
<div id="dependencynetwork"></div>
</div>
</div>
</div>
<div class="contentleft">
<h1>
Consititutional structure
</h1>
<p>
The constitutional structure covers the social concepts of a system. This structure defines roles, institutions, and role dependencies.
</p>
</div>
<div class="contentright">
<h1>Role</h1>
<p>
A role is an abstract representation of a set of activities that take place according to some rules in order to reach social objectives. Agents which are defined separately in the collective structure, can take roles. Agents taking a certain role may behave differently according to their internal agent attributes (e.g. personal values). It is possible for an agent to take more than one role be it simultaneously or sequentially.
A role has the following properties:
</p>
<ul>
<li>Objective: The general result of a role. Agents communicate with each other based on their role objectives. The emergent interactions in the model are not necessarily consistent with the objectives of the roles. If the attributes of an agent such as his internal interests are not in line with the objectives of a role, objective inconsistencies in interactions may occur. </li>
<li>Sub-objectives: The desired intermediate states of an objective. These sub-objectives are further used to define the institutional capabilities</li>
<li>Institutional Statement: The set of rules that apply to this role (will be explained in the institution section).</li>
<li>Entry Condition: The set of conditions under which an agent can take a role. These conditions define how an agent can switch between roles or have multiple roles at the same time. </li>
<li>Institutional Capability: The functions that become available to an agent when taking a certain role. </li>
</ul>
<h1>Institutional Statement</h1>
<p>
Institutional statements are presented as ADICO sequences. An ADICO sequence consists of 5 components: Attributes, Deontic, aIm, Condition and Or else. Following this structure, there are three different types of institutional statements. If there is no `Or else' for an ADICO statement, it is considered as a norm. In other words, if an agent does not follow a norm, he may receive different reactions but there is not explicit unique sanction. A `shared strategy' is a type of institutional statement where there are no deontic type or sanctions. Agents follow institutional statements depending on the roles they are taking.
</p>
<ul>
<li>Attribute: The roles that would be using this institution as part of their definition. </li>
<li>Deontic type: An institution can be in the form of prohibition, obligation or permission.</li>
<li>aIm : The goal of the institution which may be in the form of action or outcome. If in the form of action, the aim of an institutional statement should be defined as a capability of the roles that the statement is a part of ( i.e. the attributes of the statement). The aim can also be presented an an expected outcome. The aim does not include description of when and where the action is conducted. </li>
<li>Condition: The condition for the institution to hold which may address when and where the aim should take place. The when maybe temporal or in relation to some other concept. </li>
<li>Or else: The sanction for the agent taking the role if he does not follow the institution. Agents can decide to follow rules or disobey them based on their own preferences and decision making behaviour. </li>
<li>Institutional type: Type can be formal (laws and regulations, written) or informal (not written ). </li>
</ul>
<h1>Dependencies</h1>
<p>
A dependency relation describes the fact that one role depends on another role to realize his objectives. The depender is the role with an objective. The dependee is the role that fulfils the objective of the depender
</p>
</div>
<div style="clear:both;"></div>
</div>
<div class="contentArea" id="physical">
<div id="SpryAccordion2" class="Accordion" tabindex="0">
<div class="AccordionPanel AccordionPanelClosed">
<div class="AccordionPanelTab">
Physical components
</div>
<div class="AccordionPanelContent">
<div id="components"></div>
<p class="footnote">¹ Separate multiple values with commas.</p>
</div>
</div>
<div class="AccordionPanel AccordionPanelClosed">
<div class="AccordionPanelTab">
Physical connections
</div>
<div class="AccordionPanelContent">
<div id="connectiondiagram"></div>
</div>
</div>
<div class="AccordionPanel AccordionPanelClosed">
<div class="AccordionPanelTab">
Physical composition
</div>
<div class="AccordionPanelContent">
<div id="compositiondiagram"></div>
</div>
</div>
</div>
<div class="contentleft">
<h1>
Physical Structure
</h1>
<p>
The physical structure consists of any type of entity that has a physical representation in the system.
</p>
<p>
Please use the panels above to enter the physical resources of the system.
</p>
</div>
<div class="contentright">
<h1>Physical Component</h1>
<p>
A physical component in the system is an entity that can be used/produced by different agents in the system or constraint their behaviour. A physical component may be assigned to an agent through the role he is taking or may also belong to an agent independent of his role(s). For example, in a given setting, we may define the human body as a physical component belonging to an agent.
</p>
<ul>
<li>Property: Each physical component may have properties</li>
<li>Behaviour: A physical component can have certain behaviours such as ageing.</li>
<li>Type: A component can be either open or fenced. If a property is fenced the access is restricted to those agents that have the right. Open components can also have rules that define how and when an agent can use a resource.The difference between these two types of components is most useful when defining layouts and locations for agent models. </li>
</ul>
<h1>Physical Connection</h1>
<p>
Physical components may have composite relations. For example a connection can be defined between a door and a room.
The begin node and end node of a physical connection are physical components.
</p>
<h1>Physical Composition</h1>
<p>
The composition of physical components is captured in this concept.
</p>
</div>
<div style="clear:both;"></div>
</div>
<div class="contentArea" id="collective">
<div id="SpryAccordion3" class="Accordion" tabindex="0">
<div class="AccordionPanel AccordionPanelClosed">
<div class="AccordionPanelTab">
Agents
</div>
<div class="AccordionPanelContent">
<div id="agents"></div>
<p class="footnote">¹ Separate multiple values with commas.</p>
</div>
</div>
</div>
<div class="contentleft">
<h1>
Collective Structure
</h1>
<p>
</p>
</div>
<div class="contentright">
<h1>Agent</h1>
<p>
An agent is an institution-driven entity in the system who must take roles to be able to perform tasks in a given system.
</p>
<ul>
<li>Properties: The case relevant attributes of the person represented as an agent. </li>
<li>Personal Values: The intentions of an agent which determine his decision making behaviour. </li>
<li>Information: The information available to an agent. </li>
<li>Physical components: Similar to information, agents can also possess physical components. </li>
<li>Possible Roles: The roles that the agent has the potential of taking. An agent must take a role to take part in the system. </li>
<li>Intrinsic Capabilities: The capabilities an agent has independent of the role he is taking. All the actions taking place in the system should be reflected as an intrinsic capability of an agent, an institutional capability of a role or a behaviour of a physical component. </li>
<li>Decision Making Criteria: The criteria that the agent uses to choose between a set of options. Decisions are related to actions in the action situation described later</li>
</li>
</div>
<div style="clear:both;"></div>
</div>
<div class="contentArea" id="operational">
<div id="SpryAccordion4" class="Accordion" tabindex="0">
<div class="AccordionPanel AccordionPanelClosed">
<div class="AccordionPanelTab">
Action situations
</div>
<div class="AccordionPanelContent">
<div id="actionSituations"></div>
</div>
</div>
<div class="AccordionPanel AccordionPanelClosed">
<div class="AccordionPanelTab">
Actions
</div>
<div class="AccordionPanelContent">
<div id="actions"></div>
</div>
</div>
<div class="AccordionPanel AccordionPanelClosed">
<div class="AccordionPanelTab">
Role enactments
</div>
<div class="AccordionPanelContent">
<div id="roleEnactments"></div>
</div>
</div>
</div>
<div class="contentleft">
<h1>Operational structure</h1>
<p>
The operational structure makes use of the concepts in the physical, constitutional and collective structures to provide the dynamics of the agent-based model.
</p>
</div>
<div class="contentright">
<h1>Action Situation</h1>
<p>
The action situation component defines the overall operational procedure of the system. Each action situation is the placeholder for a set of related actions. Each action contains:
</p>
<ul>
<li>Precondition</li>
<li>Action body: The intrinsic capability of an agent, the institutional capability part of the role definition, or a physical component behaviour can all be considered as the actions of an action situation. It is the creativity of the modeller to groups related actions into relatively independent actions situations. In other words, the actions in an action situation are more coupled that the actions across multiple action situations. The decision about choosing a particular event as an action situation or only one action as part of an action situation highly depends on the level of detail we are planning to give to the agent-based model. If one action is big enough to be decomposed into many individual actions, it might be considered as an action situation.However, for a given action situation, more than one agent is involved even if they are taking the same role. </li>
<li>Physical Component: In action situation some physical components may be present. </li>
<li>Institutional Statement: Institutional statements usually hold in certain situations. The agents follow the statements if they are taking specific roles. </li>
</ul>
<h1>Role Enactment</h1>
<p>
Agents can take roles in different actions. This component of the operation structure clarifies the relationship between action situations, roles and agents.
</p>
<ul>
<li>Action: Defined as a component of the operational structure. </li>
<li>Agent: The agents that are present in a given action situation.</li>
<li>Role: The roles that the agents present in the action situation have the possibility of taking. </li>
</ul>
</div>
<div style="clear:both;"></div>
</div>
<div class="contentArea" id="evaluative">
<div id="SpryAccordion5" class="Accordion" tabindex="0">
<div class="AccordionPanel AccordionPanelClosed">
<div class="AccordionPanelTab">
Validation
</div>
<div class="AccordionPanelContent">
<div id="realityCloseness"></div>
</div>
</div>
<div class="AccordionPanel AccordionPanelClosed">
<div class="AccordionPanelTab">
Domain problem
</div>
<div class="AccordionPanelContent">
<div id="scope"></div>
</div>
</div>
</div>
<div class="contentleft">
<h1>
Evaluative Structure
</h1>
<p>
This structure deals with the parameters that are to the emergent outcomes of a system. These parameters can be used for model validation (i.e. having built the right model) and also, to answer the questions that the agent-based model should have answers for.
</p>
</div>
<div class="contentright">
<h1>Validation</h1>
<ul>
<li>Validation parameter : The parameters that can be used to check the validity of the model or in other words, to check whether the model is behaving the way it should. </li>
<li>Action situation: The action situation that is related to the validation parameter. </li>
</ul>
<h1>Problem Domain </h1>
<ul>
<li>Problem domain parameters: Assigned to questions that need to be answered by the agent-based model. </li>
<li>Action situation: The action situation that is related to the validation parameter. </li>
</ul>
</div>
<div style="clear:both;"></div>
</div>
<div style="clear:both;"></div>
<div class="footerArea">
<div class="copyright">
© 2011 Energy & Industry Group, Faculty of Technology, Policy and Managment, Delft University of Technology Our Company. All rights reserved.
</div>
</div>
</div>
</body>
</html>