{"id":753,"date":"2013-11-18T17:16:27","date_gmt":"2013-11-18T17:16:27","guid":{"rendered":"http:\/\/poseidon.iseresearch.i3a.uclm.es\/~tesorieror\/?page_id=753"},"modified":"2013-11-18T17:16:27","modified_gmt":"2013-11-18T17:16:27","slug":"the-task-metamodel","status":"publish","type":"page","link":"https:\/\/blog.uclm.es\/ricardotesoriero\/research\/cauce-model-driven-development-of-context-aware-applications-for-ubiquitous-computing-environments\/analysis-layer-metamodels\/the-task-metamodel\/","title":{"rendered":"The Task Metamodel"},"content":{"rendered":"

The aim of the Task metamodel is the definition of a language capable of representing the relationship between task and entities that are immersed into a Context-Aware System (CAS) running in an Ubiquitous Computing Environment (UCE).<\/p>\n

The Task model is based on the Workflow definition by the Workflow Management Coalition (WMfC) [2]. The conceptual mapping between WfMC workflow concepts and the Task Metamodel concepts is depicted on the following table.<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n
Workflow concept<\/th>\nTaMM concept<\/th>\n<\/tr>\n<\/thead>\n
Task<\/td>\nSystem Task<\/td>\n<\/tr>\n
Process<\/td>\nTask Model<\/td>\n<\/tr>\n
Token<\/td>\nToken<\/td>\n<\/tr>\n
Sequential<\/td>\nRoute Task<\/td>\n<\/tr>\n
Selective<\/td>\nSplit-OR Task<\/td>\n<\/tr>\n
Iteration<\/td>\nRoute Task<\/td>\n<\/tr>\n
Parallel<\/td>\nSplit-AND Task<\/td>\n<\/tr>\n
Condition<\/td>\nCondition<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

The Task metamodel defines two types of tasks: Routing tasks and System tasks. While System tasks define the system behavior, Routing tasks define the temporal relationship among System tasks. Examples of Systemn tasks are: Get Name, Show Clients, etc. There are 4 types of Routing tasks (aka Route tasks): Split-OR tasks (to define a selection among different routes according to target Task Pre Conditions), Join-OR tasks (to define a common route for a set of tasks satisfying target task Pre Condition), Split-AND tasks (to generare threads or define parallel task execution) and Join-AND tasks (to define task synchronization).<\/p>\n

Conditions are employed to define system states. There are 4 types of Conditions: Initial Conditions (to define the initial conditions of entities that are part of the system), Pre Conditions (to define System task pre-conditions), Post Conditions (to define System task post conditions) and Final Conditions (to define final conditions of entities that are part of the system).<\/p>\n

The task Metamodel is depicted in Figure 4 and Figure 5.<\/p>\n

\"Task<\/a>
Figure 4: Task metamodel overview<\/figcaption><\/figure>\n
\"Task<\/a>
Figure 4: Task metamodel overview<\/figcaption><\/figure>\n
\"Task-Condition<\/a>
Figure 5:Task-Condition relationship<\/figcaption><\/figure>\n

Therefore, in order to build a task model, the pattern depicted on Figure 6 should be followed.<\/p>\n

\"Task<\/a>
Figure 6: Task Metamodel Pattern<\/figcaption><\/figure>\n

The Figure 7 shows a Task model for the asynchronous exchange of files.<\/p>\n

\"Asynchronous<\/a>
Figure 7: Asynchronous exhange of files<\/figcaption><\/figure>\n

As can be seen in the example, Conditions are defined by 5 types of Expressions: Social expressions (So), Task expressions (Ta), Space expressions (Sp), Logic expressions (Lo) and Data expressions. All of these expressions should be satisfied to get the Condition satisfied.<\/p>\n

References<\/h4>\n

[2] The Workflow Management Coalition (WfMC <\/a>).<\/p>\n

You can reference this work as:
\nRicardo Tesoriero, Jos\u00e9 A. Gallud, Mar\u00eda D. Lozano and V\u00edctor M. R. Penichet.\u00a0CAUCE: Model-driven Development of Context-aware Applications for Ubiquitous Computing Environments<\/strong>.\u00a0<\/span>Journal of Universal Computer Science<\/i>, \u00a0Vol. 16, \u00a0No. 15, pp. 2111-2138. 2010. Link:\u00a0http:\/\/www.jucs.org\/jucs_16_15\/cauce_model_driven_development<\/a>
\n<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"

The aim of the Task metamodel is the definition of a language capable of representing the relationship between task and entities that are immersed into a Context-Aware System (CAS) running in an Ubiquitous Computing Environment (UCE). The Task model is based on the Workflow definition by the Workflow Management Coalition (WMfC) [2]. The conceptual mapping … <\/p>\n

Continuar leyendo \u00abThe Task Metamodel\u00bb<\/span><\/a><\/p>\n","protected":false},"author":97,"featured_media":0,"parent":704,"menu_order":0,"comment_status":"closed","ping_status":"open","template":"","meta":{"footnotes":""},"class_list":["post-753","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/blog.uclm.es\/ricardotesoriero\/wp-json\/wp\/v2\/pages\/753","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.uclm.es\/ricardotesoriero\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/blog.uclm.es\/ricardotesoriero\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/blog.uclm.es\/ricardotesoriero\/wp-json\/wp\/v2\/users\/97"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.uclm.es\/ricardotesoriero\/wp-json\/wp\/v2\/comments?post=753"}],"version-history":[{"count":0,"href":"https:\/\/blog.uclm.es\/ricardotesoriero\/wp-json\/wp\/v2\/pages\/753\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/blog.uclm.es\/ricardotesoriero\/wp-json\/wp\/v2\/pages\/704"}],"wp:attachment":[{"href":"https:\/\/blog.uclm.es\/ricardotesoriero\/wp-json\/wp\/v2\/media?parent=753"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}