Model-Driven Engineering of Workflow User Interfaces
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,350
On Slideshare
1,349
From Embeds
1
Number of Embeds
1

Actions

Shares
Downloads
14
Comments
0
Likes
1

Embeds 1

http://www.linkedin.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Model-driven Engineering of Workflow User Interfaces Josefina Guerrero, Christophe Lemaigre, Jean Vanderdonckt, Juan Manuel Gonz ález Université catholique de Louvain (UCL) Louvain School of Management (LSM) Information Systems Unit (ISYS) Place des Doyens, 1 – B-1348 Louvain-la-Neuve (Belgium) http://www.isys.ucl.ac.be/
  • 2. Outline
    • Introduction
    • Conceptual model of a workflow information system
    • A method to design workflow user interfaces
    • Case study and tool support
    • Discussion and related work
  • 3. Introduction
    • Workflow has emerged as an advantage to plan, control, and organize business process.
    • Workflow should be highly adaptable and flexible to the frequent changes, including changes on user interfaces.
  • 4. Introduction
    • Some issues encountered while deriving user interfaces from a workflow specification are:
      • User interface hand code design
      • Lack of integration models of the organization and user interface generation
      • Lack of adaptation to organizational changes
    • A model-driven engineering method is presented to systematically derive user interfaces of a workflow information system from a series of models.
  • 5. Conceptual model of a workflow information system
    • FlowiXML is a methodology for developing the various user interfaces of a workflow information system, which are advocated to automate process, following a model-driven engineering based on requirements and processes of the organization.
  • 6. A method to design workflow user interfaces
    • Simplified view decomposed according the Cameleon Reference
    • Framework and UsiXML
    taskModel Task & domain AUI level CUI level FUI level uiModel transformation Model domainModel auiModel mappingModel contextModel cuiModel Context of use
  • 7. A method to design workflow user interfaces
  • 8. Conceptual model of a workflow information system
  • 9. Conceptual model of a workflow information system
  • 10. Work list
  • 11. Conceptual model of a workflow information system
  • 12. Agenda
  • 13. Conceptual model of a workflow information system
  • 14. Task allocation
  • 15. Case study and tool support
  • 16. Case study and tool support
  • 17. Case study and tool support
  • 18. Case study and tool support
  • 19. Case study and tool support
  • 20. Case study and tool support
  • 21. Case study and tool support
  • 22. Case study and tool support
  • 23. Case study and tool support
  • 24. Discussion and related work
    • Workflow research includes
      • Graphical notations: Petri net, Statecharts, BPMN
      • Description languages: Yet Another Workflow Language (YAWL) , Exchangeable Routing Language (XRL)
      • Tools: The Progression Microsoft Windows Workflow Foundation (WWF), Flexo Business, Business Process Visual ARCHITEC (BP-VA), WebSphere® MQ Workflow [IBM], i-Flow ™, and others
      • Workflow patterns
    • We proposed a model-driven engineering approach for designing user interfaces for a workflow information system, which is decomposed into processes to end up with tasks.
  • 25. Discussion and related work
    • The characteristics of the model are:
      • It is expressed in XML-based specification language
      • Relied on Cameleon Reference Framework
      • It preserves continuity (all subsequent models are derived from previous ones) and traceability of its enactment (it is possible to trace how a particular workflow is decomposed into processes and tasks, with their corresponding user interfaces).
    • In order to partially support this method, a software tool has been developed in Java 1.5 that supports the graphical editing of the concepts introduced in an integrated way.
    • This method has been validated on 4 real-world case studies (a hospital dept., a triathlon organization, a cycling event, and personalized order of compression stockings over Internet).
  • 26. Discussion and related work
    • As future work, we will consider criteria for support group interactions:
      • Support carrying out group tasks
      • Support multiple ways to support a group task
      • Support the group evolution over time
    • Usability guidelines to design user interfaces
    • Synchronization of user interfaces
  • 27. 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! http://www.conacyt.mx Consejo Nacional de Ciencia y Tecnolog ía