Usability-Driven Mobile Application Development

Recently,a specific interest is being taken in the development of mobile application(app)via Model-Based User Interface Development(MBUID)approach.MBUID allows the generation of mobile apps in the target platform(s)from conceptual models.As such it simplified the development process of mobile app.However,the interest is only focused on the functional aspects of the mobile app while neglecting the non-functional aspects,such as usability.The latter is largely considered as the main factor leading to the success or failure of any software system.This paper aims at addressing non-functional aspects of mobile apps generated using MBUID approach.As such,we propose a usability-driven approach for the development of mobile apps.The main stages of the proposed approach are defined in a generic way so that they can be integrated with any MBUID method.A case study is presented,in the paper,with the aim of illustrating the feasibility of this approach.

Leveraging React Components in Business Process Management (BPM) Applications

As organizations increasingly embrace digital transformation, the integration of modern web technologies like React.js with Business Process Management (BPM) applications has become essential. React components offer flexibility, reusability, and scalability, making them ideal for enhancing user interfaces and driving user engagement within BPM environments. This article explores the benefits, challenges, and best practices of leveraging React components in BPM applications, along with real-world examples of successful implementations.

User Interface Development Based on Ontologies

The user interface is a central component of any mo de rn application program. It determines how well end users accept, learn, and effi ciently work with the application program. The user interface is very difficult to design, to implement, to modify. It takes approximately 70% of the time requ ired for designing an application program. All the existing tools for user interface design can be divided into two basic c ategories-Interface Builders and Model-based Interface development tools, whic h trace their roots from user interface management systems. Interface Builders a re the most widespread and excellent to create layouts and manipulate widgets. H owever, Interface Builders have the follow demerits. An interface designed using Interface Builders can contain hundreds of procedures. Interface Builders give us no possibility to develop different pieces of the same interface separately. They do not help us in managing user tasks and can be used only by programmers. Model-based interface development tools have attracted a high degree of interes t in last few years. The basic premise of model based technology is that the interface development can be fully supported by declarative models of all user interface characteristics such as their presen tation, dialogue, domain of application etc, and then the user interface develop ment can be centered around such models. The high potential of this technology has not been realized yet. This fact has the following reasons. The known interface models are partial representations of interfaces. They cannot be readily modified by developers, and are not publicly available to the HCI community. The central ingredient for success in model-ba sed systems is a declarative, complete, versatile interface model that can expre ss a wide variety of interface designs. Therefore tool developers have to avoid the following disadvantages of current interface models: inflexibility, system- dependence, and incompleteness. The main idea to achieve these model character istics mention above is to use ontologies. This broadened interest in ontologies is based on the fact that they provide ma chine-understandable representation of semantics for information, and a shared and common understanding of a domain that can be communicated between people and across application systems. Support in data, information, and knowledge exchang e becomes the key issue in current computer technology. At the moment we are on the brink of the second Web generation called Semantic Web or Knowledgeable Web. Given the increasing amount of information available on-line, this kind of sup port is becoming more important day by day. The main idea of the proposed approach is to replace interface models by appropr iate ontologies. Some parts of these ontologies will be available from the Inter net; the other parts will be built by developers. As a result of the Semantic We b development we will have increasing the number of ontologies formally describe d in the Internet. The terminology and content of these ontologies will be inter nationally standardized. Reusing these ontologies will bring down the cost of de velopment and improve the quality of user interface. The parts of a user interface model are-a domain ontology model, a dialog ontol ogy model, presentation ontology model, "business- logic" variable ontology mod el and correspondences between these parts. Thus, the user interface development based on ontologies is an evolution of th e model-based approach, where appropriate ontologies are used instead of models .

A Domain Knowledge Driven Approach for User Interface Software Development

A domain knowledge driven user interface development approach is described.As a conceptual de- sign of the user interface,the domain knowledge defines the user interface in terms of objects,actions and their relationships that the user would use to interact with the application system.It also serves as input to a user interface management system(UIMS)and is the kernel of the target user interface. The principal ideas and the implementation techniques of the approach is discussed.The user interface model,user interface designer oriented high-level specification notation,and the transformation algorithms on domain knowledge are presented.