ITS: a tool for rapidly developing interactive applications

Wiecha, Charles; Bennett, William E.; Boies, Stephen J.; Gould, John; Greene, Sharon L.

doi:10.1145/98188.98194

Cited by 156 publications

(19 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Indeed, this is the result of practical experiences with this technology, e.g. ITS was used by IBM to produce the UI of the visitor information system of EXPO'92 [50,51], and FUSE has been used by Siemens to simulate an ISDN telephone.…”

Section: Discussionmentioning

confidence: 99%

“…In general, these notations have been developed specifically for the MB-UIDE. They can be completely new as in ITS's Style rules [50,51], or they can be extensions of other notations, as in MASTERMIND's MDL that is an extension of CORBA IDL [41]. The use of a single notation can be useful to describe how the models collaborate with each other.…”

Section: Model Notationsmentioning

confidence: 99%

See 1 more Smart Citation

User Interface Declarative Models and Development Environments: A Survey

Silva

2001

Interactive Systems Design, Specification, and Verification

View full text Add to dashboard Cite

Model-Based User Interface Development Environments (MB-UIDEs) provide a context within which user interface declarative models can be constructed and related, as part of the user interface design process. This paper provides a review of MB-UIDE technologies. A framework for describing the elements of a MB-UIDE is presented. A representative collection of 14 MB-UIDEs are selected, described in terms of the framework, compared and analysed from the information available in the literature. The framework can be used as an introduction to the MB-UIDE technology since it relates and provides a description for the terms used in MB-UIDE papers.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Model Notationsmentioning

confidence: 99%

User Interface Declarative Models and Development Environments: A Survey

Silva

2001

Interactive Systems Design, Specification, and Verification

View full text Add to dashboard Cite

show abstract

“…The foremost among these are HTML [28] for desktop machines, WML [26] for small hand-held devices, and VoiceXML [24] for voice-enabled devices. XML itself is a meta-language that allows the definition of other languages.…”

Section: Markup Languages and The World Wide Webmentioning

confidence: 99%

Building Multi-Platform User Interfaces with UIML

Ali

Pérez-Quiñones

Abrams

et al. 2002

Computer-Aided Design of User Interfaces III

View full text Add to dashboard Cite

There has been a widespread emergence of computing devices in the past few years that go beyond the capabilities of traditional desktop computers. However, users want to use the same kinds of applications and access the same data and information on these appliances that they can access on their desktop computers. The user interfaces for these platforms go beyond the traditional interaction metaphors. It is a challenge to build User Interfaces (UIs) for these devices of differing capabilities that allow the end users to perform the same kinds of tasks. The User Interface Markup Language (UIML) is an XML-based language that allows the canonical description of UIs for different platforms. We describe the language features of UIML that facilitate the development of multi-platform UIs. We also describe the key aspects of our approach that makes UIML succeed where previous approaches failed, namely the division in the representation of a UI, the use of a generic vocabulary, and an integrated development environment specifically designed for transformation-based UI development. Finally we describe the initial details of a multi-step usability engineering process for building multi-platform UI using UIML.Keywords: Multi-Platform User Interfaces, Transformations, UIML, Physical Model, Logical Model, Usability Engineering. INTRODUCTIONIt is difficult to develop an application for multi-platform deployment without duplicating development effort. Advances in electronics, communications, and the fast growth of the Internet have made the use of a wide variety of computing devices an everyday occurance. Furthermore, users expect to remotely access their data from any of these devices (e.g. desktop computer, laptop, handheld, phone, etc.). Developers now face the daunting task to build user interfaces that must work in multiple devices. To address the need for a uniform language for building multi-platform applications, we have developed the User Interface Markup Language (UIML). In this paper we discuss our research in creating such language, some of the support tools available, and describe our approach towards creating a new user interface design methodology to build multi-platform user interfaces.UIML is a single language for building user interfaces for any device. UIML emphasizes the separation of concerns of an interactive application in such a way that moving one program from one platform to another (see our definition of platform in the next section) might require only small or no changes at all. Furthermore, because it is based on XML, it is easy to write transformations that take the language from one abstract representation to a more concrete representation. The tools built around UIML extend the language with the use of transformations that afford the developer the creation of user interfaces with a single language that will execute in multiple platforms.The approach taken with UIML is that of building an application using a generic vocabulary that could then be rendered for multiple platforms. Using a gen...

show abstract

“…It generally consists of a hierarchical decomposition of the possible screen displays into groups of interaction objects. By definition, presentation and dialog models are closely interrelated, which is why some model-based development environments consider them together: ITS 9 typically falls in this category by providing a style library. A style is a coordinated set of decisions on presentation and dialog used consistently throughout a family of applications.…”

Section: Figure 3 Mobi-d's User-task Elicitation Stage: (A) An Informentioning

confidence: 99%

A model-based interface development environment

Puerta

1997

IEEE Softw.

174

View full text Add to dashboard Cite

Mobi-D is a highlyost interface development problems can be traced to two sources: the need for usercentered design environments and the lack of software systems that support all major development stages. Developer-centered environments, which are typical of most systems, give ample support to using and managing widgets, organizing and arranging layouts, and testing prototype interfaces, but fall short of answering key questions such as how widgets in a given dialog box can be used to accomplish a particular user task. The designer is forced to rely on her own experience to answer such questions or to distill a solution from loosely connected documentation.In this article, I describe Mobi-D 1,2 (Model-Based Interface Designer), a comprehensive environment that supports usercentered design through model-based interface development. In the Mobi-D paradigm, a series of declarative models, such as user-task, dialog, and presentation, are interrelated to provide a formal representation of an interface design. This contrasts to model-based systems, which use only one or two models in isolation and have no explicit notion as to how the various model elements are organized into an interface design. M.

show abstract

ITS: a tool for rapidly developing interactive applications

Cited by 156 publications

References 15 publications

User Interface Declarative Models and Development Environments: A Survey

User Interface Declarative Models and Development Environments: A Survey

Building Multi-Platform User Interfaces with UIML

A model-based interface development environment

Contact Info

Product

Resources

About