Rbuis

Abstract

Enterprise applications such as customer relationship management (CRM) and enterprise resource planning (ERP) are very large scale, encompassing millions of linesof-code and thousands of user interfaces (UI). These applications have to be sold as feature-bloated off-the-shelf products to be used by people with diverse needs in required feature-set and layout preferences based on aspects such as skills, culture, etc. Although several approaches have been proposed for adapting UIs to various contexts-ofuse, little work has focused on simplifying enterprise application UIs through engineering adaptive behavior. We define UI simplification as a mechanism for increasing usability through adaptive behavior by providing users with a minimal feature-set and an optimal layout based on the context-of-use. In this paper we present Role-Based UI Simplification (RBUIS), a tool supported approach based on our CEDAR architecture for simplifying enterprise application UIs through engineering role-based adaptive behavior. RBUIS is integrated in our general-purpose platform for developing adaptive model-driven enterprise UIs. Our approach is validated from the technical and enduser perspectives by applying it to developing a prototype enterprise application and user-testing the outcome.

Using Cognitive Work Analysis to Develop Predictive Maintenance Tool for Vessels

“…Finally, the SOCA-CAT has allowed us to identify the possibility of separate interfaces for different user classes. A technique that has already been used in adaptive interface (Akiki, Bandara & Yu, 2013). For example, the chief engineer may need to have access to all functions and information of the entire system, when the electric team officer will only need to analyze electrical system's information.…”

Visual Simple Transformations

“…Hence, it becomes possible to define a transformation, by dragging and dropping visual constructs that are easy to understand. In a previous work, we used the Windows Workflow Foundation (WF) for adapting model-driven UIs [Akiki et al 2013b], [Akiki et al 2014]. The underlying workflow implementation of ViSiT is based on our previous experience with WF, but ViSiT is more general purpose and has visual constructs for specifying model transformations.…”