{"id":145,"date":"2015-09-17T14:29:11","date_gmt":"2015-09-17T12:29:11","guid":{"rendered":"https:\/\/vprojects.offis.de\/hcd\/wordpress\/?page_id=145"},"modified":"2016-04-27T14:02:51","modified_gmt":"2016-04-27T12:02:51","slug":"magicped","status":"publish","type":"page","link":"https:\/\/hce.jpo-online.de\/?page_id=145","title":{"rendered":"MagicPED"},"content":{"rendered":"

Introduction<\/h2>\n

MagicPED is a plugin for the commercial UML tool MagicDraw<\/a> by NoMagic<\/a>, that allows modelling of tasks and rules in MagicDraw.<\/p>\n

Task&Rule Modelling<\/h2>\n

In general terms, task modelling is concerned with describing how the work is performed by one or more persons to achieve a given goal. However, such a loose definition also means that a primary concern in the planning of the model is the desired level of granularity, which can go from a general level down to specific hand movements on a control panel, for instance. A modelling language is intended to express the properties of the modelled entity in a way that covers all the aspects needed to fulfil the purpose of the development work. It is therefore useful to look at what problem domains a task modelling language is expected to cover and what the models needs to express to be helpful in that domain.<\/p>\n

Task models are attempts at describing tasks, subdivisions of a sequence of activities, in such a way that they can be treated formally and provide a useful level of predictability for their intended purpose.<\/p>\n

The MagigPED\u00a0task modelling consists of two parts:
\nThe first one is based on hierarchical task modelling (HTA), especially regarding the task hierarchy. Planning (which is also a part of many HTA schemes) is supported through the use of “time constraints” between the tasks: before<\/em>, parallel<\/em>, choice<\/em> (or without any constraints it is unordered). This provides a high level of modelling capabilities, which typically encapsulates normative task knowledge. The formal structure of the models is based on the work of W3C<\/a>.\"Task\"
\nThe second part extends the modelling with a rule\u00a0level, which will provide a more descriptive modelling of the actions close to the actual physical equipment, software UI, other agents and the controlled entity. This level of the modelling is based on GSM (Goal-State-Means) modelling, to form an overall modelling framework that connects the higher-level goals of the top level model with the actual state of the environment.\"Rule\"<\/p>\n

 <\/p>\n

<\/h2>\n

Features<\/h2>\n