Unleash Your Potential - Namagunga Girls Coding Club
Towards a Library of Workflow User Interface Patterns
1. Towards a Library of Workflow User Interface Patterns Josefina Guerrero García 1 , Jean Vanderdonckt 1 , Juan Manuel González Calleros 1 , Marco Winckler 1,2 1 Université catholique de Louvain (UCL) Louvain School of Management (LSM) - Information Systems Unit (ISYS) Belgian Laboratory of Computer-Human Interaction (BCHI) http://www.isys.ucl.ac.be/bchi 2 IRIT, Université Toulouse 3, France, 118 route de Narbonne, F-31062 Toulouse cedex 9 (France), winckler@irit.fr – http://liihs.irit.fr/winckler/
6. Developing user interfaces for workflow information systems Task & domain level AUI level CUI level FUI level
7.
8. Workflow user interface patterns Augmented UI pattern definition Identifier Name Alias Synopsis Strengths Weakness Opportunities Threads Problem Solution Example Incorporation in the model-driven engineering method Final WUIPs Definition WUIP
9.
10.
11.
12.
13.
14. Thank you very much for your attention For more information and downloading, http://www.isys.ucl.ac.be/bchi http://www.usixml.org User Interface eXtensible Markup Language http://www.similar.cc European network on Multimodal UIs Special thanks to all members of the team!
Hinweis der Redaktion
In order to structure the development life cycle of a workflow UI, we are relying on FlowiXML, a structured method for developing UIs of a workflow information system. The underlying method is composed of four models: workflow , process , task , and organization . The workflow model is recursively decomposed into processes which are in turn decomposed into tasks. By exploiting task models UIs can be generated.
This model is based on Cameleon reference framework, which proposes 4 levels: Task and domain, AUI level, CUI level and FUI level.
Augmented UI pattern definition : from each workflow resource pattern a WUIP is created and consistently described through attributes. Incorporation in the model-driven engineering method : for each initial pattern definition resulting from the previous step, a task model has been specified. Final WUIPs : from the task model resulting from the previous steps, an abstract UI and, consequently, a concrete UI have been defined in terms of the User Interface Description Language (here, UsiXML) so as to form corresponding abstract and concrete UI models.
We can take as an example the workflow resource pattern: DIRECT ALLOCATION, which specify t he ability to specify at design time the identity of the resource that will execute a task. We observe that a task is assigned to a specific resource, then a task model is generated defining the task and after a UI is developed.
Another example is the Hierarchy level-based pattern, which specify the ability to offer or allocate instances of a tasks to resources based their position within the organization. From the definition we built the task model and consequently the AUI, CUI and FUI
In order to support the application of WUIPs, a special module has been developed and incorporated in our workflow model editor. This module enables the designer, while modeling the general workflow, to retrieve any WUIP from the library, to configure it, and to automatically incorporate it in the current model.