Abstract

Business applications are difficult to use for the average user. An adaptive user interface improves employees’ productivity and is presented as a solution to this problem. However, developing user interfaces that are adapted to the needs and culture of the enterprise is time-consuming and expensive. We developed a software prototype for generating adaptive user interfaces that makes this process less time-consuming and more efficient. We propose an extension to the Cameleon Reference Framework project by Information Society Technologies, on the implementation level by adding an additional step for defining the Area of Business Operations. That way the prototype can extract business tasks for the selected industry therefore, presenting to the developer a more intelligent selection of predefined tasks. In this article, we also present a programming approach for transforming a task model, as defined by the ConcurTaskTrees notation, into an abstract user interface.

Highlights

  • An adaptive user interface is defined as a user interface that is aware of the context of use and is capable of changes according to the context (W3C Incubator Group, 2010)

  • We have developed a software prototype for generating adaptive user interfaces extending the Cameleon Reference Framework’s four levels of UI development cycle

  • As the prototype is designed for building user interfaces for business information systems, we propose a modification to the Cameleon Reference Framework (CRF) on the implementation level by adding an additional step for defining functional areas of operations (Figure 1)

Read more

Summary

Introduction

An adaptive user interface is defined as a user interface that is aware of the context of use and is capable of (automatic) changes according to the context (W3C Incubator Group, 2010). As the prototype is designed for building user interfaces for business information systems, we propose a modification to the CRF on the implementation level by adding an additional step for defining functional areas of operations (Figure 1). We describe how we implemented the transformation of the Task model into an Abstract User Interface.

Results
Conclusion
Full Text
Paper version not known

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.