| ... |
... |
@@ -11,7 +11,7 @@ |
| 11 |
11 |
|
| 12 |
12 |
==== Related work ==== |
| 13 |
13 |
|
| 14 |
|
-Welie, M. Van, Veer, G. C. Van Der, & Eliëns, A. (1998). An ontology for task world models. Design, Specification and Verification of Interactive Systems ’98, 57–70. |
|
14 |
+Welie, M. Van, Veer, G. C. Van Der, & Eliëns, A. (1998). An ontology for task world models. Design, Specification and Verification of Interactive Systems ’98, 57–70. |
| 15 |
15 |
|
| 16 |
16 |
==== Ontology design ==== |
| 17 |
17 |
|
| ... |
... |
@@ -28,6 +28,8 @@ |
| 28 |
28 |
|
| 29 |
29 |
Agent - an agent is an entity that is considered active. Usually agents are humans but groups of humans or software components may also be considered agents. Agents are not specific individuals (like Chris) but always indicate classes of individuals with certain characteristics. Attributes of the agent can include skills, attitude and other miscellaneous. Agents perform tasks and always play certain roles within the task world (Welie 98). |
| 30 |
30 |
|
|
31 |
+[[image:task.jpg]] |
|
32 |
+ |
| 31 |
31 |
**Goal** - A desired state in the task world or of the system. A goal can be reached by one or more tasks. Goals may also have sub-goals. |
| 32 |
32 |
|
| 33 |
33 |
**Object** - An object refers to a physical or non-physical entity. A non-physical entity could be anything ranging from messages, passwords or addresses to gestures and stories. Objects have attributes consisting of attribute-name and value pairs. What can be done with an object is specified by actions, for instance move, change, turn off etc. Furthermore, objects may be in a type hierarchy and can also be contained in other objects, for example a form may contain an address field, and a cinema can contain a snack bar. Objects are typically used in tasks but they can also influence the task execution sequence when they cause events to occur. |
