1 / 23

D . Kotowski , G. Henriques , M. G. Gillespie , H . Hlomani , D . A. Stacey

LEVERAGING USER KNOWLEDGE: Design Principles for an Intuitive User Interface for Building Workflows. D . Kotowski , G. Henriques , M. G. Gillespie , H . Hlomani , D . A. Stacey School of Computer Science University of Guelph Guelph, Ontario, Canada. Who Are We?.

kolya
Download Presentation

D . Kotowski , G. Henriques , M. G. Gillespie , H . Hlomani , D . A. Stacey

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LEVERAGING USER KNOWLEDGE:Design Principles for an Intuitive User Interface for Building Workflows D. Kotowski, G. Henriques, M. G. Gillespie, H. Hlomani, D. A. Stacey School of Computer Science University of Guelph Guelph, Ontario, Canada

  2. Who Are We? • Guelph Ontology Team (GOT) • School of Computer Science, University of Guelph • Website: http://ontology.socs.uoguelph.ca • Research Foci: • Compositional Systems • Workflow Planning • Ontology Discovery and Reuse Knowledge Engineering and Ontology Development 2011

  3. Goal of this Presentation • This paper focuses on the human issues related to developing a workflow management application. • The system metaphor embraced by the user is instrumental in determining if the system is successful. Knowledge Engineering and Ontology Development 2011

  4. Semantic Web andCompositional Systems • System Composition is the process of composing two or more previously implemented software units and/or services to create a more functional system. • Compositional Systems are expert systems that automatically or semi-automatically perform system composition. Knowledge Engineering and Ontology Development 2011

  5. Ontology Driven Compositional Systems (ODCS) • An Ontology Driven Compositional System is reasons with ontological representations to construct a resultant system composed of compositional units. Source Gillepseet. al. (2011) Knowledge Engineering and Ontology Development 2011

  6. The Human Aspect of ODCS • The main function of an ODCS is to compose software so that the user can focus on the solution that they need – the system is leveraging the knowledge of the user/expert to design domain specific solutions. • Many systems design from the bottom up and the user interface is not as well designed with regards to user expectations and need for an appropriate metaphor. Knowledge Engineering and Ontology Development 2011

  7. ODCS User Interface: System Goals • Be able to compose a system of workflows or compositional units without the need of expert software knowledge. • Ability to use on any platform or anywhere. Knowledge Engineering and Ontology Development 2011

  8. Usability Heuristics • Jakob Nielsen, one of his ten usability heuristics: “flexibility and efficiency of use” • Accommodate novice users at composing workflows or compositional units without the need of expert software knowledge • Leveraging knowledge • Bi-directional transfer of knowledge between two people • Incorporate this into the interface Knowledge Engineering and Ontology Development 2011

  9. Mind Mapping • Method developed by mathematicians to visualize difficult problems. • Excels in connecting new information with given knowledge (Brinkmann, 2003). • Mind mapping process is a logical way to represent a workflow. • It is key inspiration in our interface design. Knowledge Engineering and Ontology Development 2011

  10. Current Technologies • Triana • Problem solving environment used for composing, compiling and running applications • Galaxy • Tool and data integration framework • Yahoo Pipes • Composition tool that creates data mash-ups Knowledge Engineering and Ontology Development 2011

  11. ODCS Interface: Architecture Knowledge Engineering and Ontology Development 2011

  12. Requirements • Automatically infer semantic relationships between compositional units • E.g.Input/Output requirements • Modification of CU database should be seamless. • Should expose as much information as possible about the CU. • E.g. author of CU, other users, etc. • Allow for inexperienced users. Knowledge Engineering and Ontology Development 2011

  13. Decisions • Decided not to write a module for an IDE such as Eclipse. • Learning burden too great and too foreign for most domain experts. • Web-based tool based on mind mapping. • Focus on workflow as an approachable metaphor for most users. • Distributed architecture places small HW/SW demands on the user. Knowledge Engineering and Ontology Development 2011

  14. System Architecture • Architecture is divided into three layers. • KB: bottom layer where ODCS resides. • Middle: web service translates info from interface and presents to ODCS and conveys results from ODCS to interface. • Interface sits on top. Knowledge Engineering and Ontology Development 2011

  15. System Architecture • Inspired by modern SOA • loosely coupled components generating a service • High portability and reuse • Knowledge base can be switched out as long as it adheres to the communication layer interface • Interface can be changed Knowledge Engineering and Ontology Development 2011

  16. Interface Components – WireIt! • An open source Javascript library used to create “wireable” interfaces (Abouaf 2010). • Adopted as the interface due to the flexibility and adaptability exhibited by the libraries. • WireIt! wiring editor used as the basis for our interface. • Wirable I/O containers used as the main representation for CUs. Knowledge Engineering and Ontology Development 2011

  17. Full Interface Knowledge Engineering and Ontology Development 2011

  18. Interface Header • Manages workflows • A workflow is loaded from an XML file which is passed from the ODCS through the web service. • User never sees the XML. • Templates are available. Knowledge Engineering and Ontology Development 2011

  19. Interface Left Menu • Manages presentation of the CU modules collection. • CUs are categorized and sorted. • Interface can access any number of different sets of CUs. • User has access to information about the CUs without the need to understand the underlying software. Knowledge Engineering and Ontology Development 2011

  20. Interface Workflow Area Knowledge Engineering and Ontology Development 2011

  21. Interface Workflow Area • Mind Mapping Model • I/O Container • Representation of CU. • Contains a set of I/O terminals that display CU parameters. • Wires • Connect the I/O containers. • A wire can only connect Output to Input terminals. Knowledge Engineering and Ontology Development 2011

  22. Interface Right Menu • Information • Information about workflow builder • Properties • Displays information about CU semantics • Semantics include: Trust, Quality and Functionality • Workflow Map • Displays mini-map of current workflow • Allows for navigation of the workflow Knowledge Engineering and Ontology Development 2011

  23. Discussion • Mind mapping metaphor for workflow building. • Highly adaptable system - can be applied to multiple Compositional Systems. • Considers usability of the system as ODCSs bring new and unique challenges to the end user. • Brings together users of all expertise levels. • Cost efficient. Knowledge Engineering and Ontology Development 2011

More Related