- About the project
- UsiXML Tools
- About us
Among all audiences for dissemination, the primary one is the industry and technology suppliers, and then, the scientific community. The aim is to promote the project and its results to facilitate a rapid and large up-take by potential industrial users and to extend the support by developers of related technologies. The second target will be the public, since UsiXML will in the longer term impact the daily life of the worker and the citizen, i.e. UsiXML will impact on UIs of professional equipment and consumer products. The information dissemination to the public will therefore focus on the potential improvement of the usability of various applications, rather than the UsiXML technology itself, which obviously will be of interest for technical experts only.
Industry: The aim is to create awareness on UsiXML developments and promote their particular added value. The success of USIXML in the long term will depend on the up-take of the MDA concepts and technology by a large number of industrial users. This will increase the credibility of this technology thanks to the references cases in practical applications in various sectors, and ensure that it will be enriched and faster achieve maturity and robustness. The aim is to reach a de facto market standard by adoption of the UsiXML technology by an important number of industrial players. This will be beneficial for all, the UsiXML partners and the European industry as a whole.
Technology suppliers: The adoption of UsiXML by the industry will in turn encourage technology suppliers to include UsiXML concepts and technology in their products and therewith further enhance the power of µ7 UIs. In order to anticipate and accelerate this evolution, UsiXML will disseminate information to companies involved in the development of adaptive multimodal interface technologies and to vendors of software development systems.
The following list gather the list of tools that will be developped during the UsiXML project:
UsiGesture: UsiXML Concrete Editor with gesture handling (here)
UsiGesture consists of an editor enabling designers, developers, or even end users to build a representation of user interfaces handling gesture commands, at a concrete level in UsiXML. In addition to the common widgets, the user of the editor is able to include special commands triggered by pen-based gestures. The representation is used by the tool to derive the UsiXML specifications independently of the programming toolkit as well as the context of use, including the user and platform and the environment.
UsiContext: The Context Model Editor (here)
The goal of the Context Model Editor is the creation, edition and validation of context models describing main characteristics of the entities that are part of the system, and affect the system context. These characteristics will describe the situation in which tasks will be performed. However, situations are not defined by the context model; they are defined in a separated editor (the Task Model Editor) because a situation affects a single task. Thus, the same context description (context model) can be reused in different task models.
The Context Model Editor was developed as an Eclipse Plug-in taking advantage of the Eclipse Modelling Framework (EMF) and the Graphical Modelling Framework (GMF). The Context Model Editor defines a set of model constraints that are defined using the Object Constraint Language (OCL). This language allows the definition of validation rules to validate the consistency of the models to be created. The distribution of Eclipse development environment that was used was the Moskitt.
UsiSketch: Multi-Agent Design Tool for Sketching User Interfaces (here)
UsiSketch consists of a multiplatform multi-agent interactive application that enables designers, developers, or even end users to sketch user interfaces with different levels of details and support for different contexts of use. The results of the sketching are then analyzed to produce interface specifications independently of any context, including user and platform. These specifications are exploited to progressively produce one or several interfaces, for one or many users, platforms, and environments.
UsiConcrete: Editor for specifying User Interfaces at UsiXML concrete level (here)
UsiConcrete consists of an editor enabling designers, developers, or even end users to build a representation of user interfaces at a concrete level in UsiXML. “Concrete” corresponds to a level of abstraction of UsiXML for which the programming toolkit is abstracted. The representation is used by the tool to derive the UsiXML specifications independently of the programming toolkit as well as the context of use, including the user and platform and the environment.
UsiAbstract: Editor for specifying User Interfaces at UsiXML abstract level (here)
UsiAbstract consists of an editor enabling designers, developers, or even end users to build a representation of user interfaces at an abstract level in UsiXML. “Abstract” corresponds to a level of abstraction of UsiXML for which the programming toolkit and the modality (i.e. graphic, vocal, haptic, etc.) is abstracted. The representation is used by the tool to derive the UsiXML specifications independently of the programming toolkit and the modality as well as the context of use, including the user and platform and the environment.
UI Prototyping: User Interface Prototyping (here):
A user interface prototype is a realistic, possibly working, simulation of the user interface. The design ideas and concepts are made more concrete, visible and tangible, resulting in low-fidelity or high-fidelity simulations of the future experience, in order to evaluate, review and refine them.
A prototype can take various forms, from a refined, detailed, though static drawing to a dynamic prototype illustrating, or animating, the behavior of (a part of) the user interface. The prototype is ideal for conducting (formative) usability tests, validate business requirements or ideas and can be used to derive service assets.
UsiWalkAlone: Tracks Creation Application (here)
This tool will enable users to create tourism tracks. The user will also have the possibility to complete the track with multimedia resources like text, audio comments, pictures and videos. With this application, everyone can create and suggest tourism tracks to other users.This application will be available on dedicated market places (App Store, Android Market, etc.)
UsiWalks: Tourism Tracks Creation Service (here)
This tool will enable tourism tracks creation, based on a GPS trace. It will also be possible to complete the tracks with multimedia resources like text, audio comments, pictures and videos. At the user side, it will be possible to filter the tracks based on criteria such as the track’s type, its theme, etc. For tourism entities, it will also be possible to add booking forms following the µ7 modality, based on the UsiForms service.
This service will be delivered as a “Pay on demand” service.
UsiForms: Form Management SaaS Service (here):
This service will be delivered as a “Pay on demand” service.
UsiCMS: Content Management Tool (here):
This tool will be based on the UsiXML technology and thus will be able of delivering web content based on the µ7 paradigm.
Abstract Interface Editor in Java/Swing (here)
The tools will belong to the UsiXML development suite and enable developers to create the main user interfaces along with the application logic.
This tool will be delivered as a “Pay to use” service.
MOM: Meaningful Objects Manager (here):
The tools package MOM (Meaningful Objects Manager) will allows the examination of each accessible object in the Graphical User Interfaces (GUI) for any Windows application. In this context, by examination we understand the dynamically interrogation of the analyzed object’s properties.
The main goal of the MOM package is to facilitate an efficient analysis of the GUIs’ accessibility, using low level techniques, down to operation system level. The involved technologies are the same as those used in the most advanced screen reader applications, Virgo and Cobra, produced by the same company – BAUM Engineering. The data about the GUIs’ objects are collected (in extreme cases) by intercepting the communication between operation system and graphic card’s driver.
In order to be accessible, any object (i.e. a button, a list element etc.) should be “visible”, meaning that the main properties of the object should be directly accessible to the screen reader. If one objects’ properties are only indirectly accessible, through the special MOM’s function, there is a risk that a less advanced screen reader would not be able to guarantee the user interaction with the application’s interface.
UsiTask: Editor for specifying User Interfaces at UsiXML task level (here):
The goal of the Task Model Editor is the creation, edition and validation of context-aware task models. In order to define the situations affecting tasks, the Task Model Editor gathers context information from a Context Model that is defined using the Context Model Editor. Thus, the same context model can be reused in different task models.
The Task Model Editor was developed as an Eclipse Plug-in taking advantage of the Eclipse Modelling Framework (EMF) and the Graphical Modelling Framework (GMF). The Task Model Editor defines a set of model constraints using the Object Constraint Language (OCL) to validate the consistency of the models to be created. The distribution of Eclipse development environment was the Moskitt.
Download all the descriptions sheet of the tools (here).