Garnet: comprehensive support for graphical, highly interactive user interfaces

Myers, Brad A.; Giuse, Dario A.; Dannenberg, Roger B.; Zanden, Brad Vander; Kosbie, David S.; Pervin, Edward; Mickish, Andrew; Marchal, Philippe

doi:10.1109/2.60882

Cited by 381 publications

(91 citation statements)

References 13 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…It also defines the collective behavior of presentation objects, specifying the control and flow of communication between the user and the system. This model (Figure 1) may be realized by the use of several toolsets and specification languages (Helander, 1988;Jacob, 1986;Myers et al, 1990). The presentation system can be created using some window-based toolset such as HyperCard (Apple Macintosh, 1987) where presentation objects are grouped onto cards which are grouped into stacks.…”

Section: Environment For Discussionmentioning

confidence: 99%

Focused interaction in dialogues

Mulvihill

McDermott

1992

International Journal of Human-Computer Interaction

View full text Add to dashboard Cite

This report addresses the dialogue support issues involved in tailoring courses to organization-specific requirements. We present a brief discussion of current dialogue support techniques and discuss their inability to facilitate focussed interfacing, a crucial element in raising the quality of service available to real-world organizations. In any real-world organization the functionality must exist to modify and refine an initial position with respect to a course. We demonstrate techniques for focusing on the task at hand and incorporating partial decision elements in the dialogue interface itself, providing an illustration of our approach.

show abstract

Section: Environment For Discussionmentioning

confidence: 99%

Focused interaction in dialogues

Mulvihill

McDermott

1992

International Journal of Human-Computer Interaction

View full text Add to dashboard Cite

show abstract

“…Reference [BFBW92] presents a formal, declarative specification of read-only annotations, adapted from formalizations of read-only annotations in committedchoice logic languages [Mah87], but the above intuitive description is sufficient for the current purpose.…”

Section: Read-only Annotationsmentioning

confidence: 99%

Specifying and Solving Constraints on Object Behavior.

Felgentreff¹,

Borning²,

Hirschfeld³

2014

JOT

View full text Add to dashboard Cite

Constraints allow developers to specify desired properties of systems in a number of domains, and have those properties be maintained automatically. This results in compact, declarative code, avoiding scattered code to check and imperatively re-satisfy invariants. Despite these advantages, constraint programming is not yet widespread, with imperative programming still the norm.There is a long history of research on integrating constraint programming with the imperative paradigm. However, this integration typically does not unify the constructs for encapsulation and abstraction from both paradigms. This impedes re-use of modules, as client code written in one paradigm can only use modules written to support that paradigm. Modules require redundant definitions if they are to be used in both paradigms.We present a language -Babelsberg -that unifies the constructs for encapsulation and abstraction by using only object-oriented method definitions for both declarative and imperative code. Our prototypeBabelsberg/R -is an extension to Ruby, and continues to support Ruby's object-oriented semantics. It allows programmers to add constraints to existing Ruby programs in incremental steps by placing them on the results of normal object-oriented message sends. It is implemented by modifying a state-of-the-art Ruby virtual machine. The performance of Ruby code without constraints is only modestly impacted, with typically less than 10% overhead compared with the unmodified virtual machine. Furthermore, our architecture for adding multiple constraint solvers allows Babelsberg to deal with constraints in a variety of domains.We argue that our approach provides a useful step toward making constraint solving a useful tool for object-oriented programmers. We also provide example applications, written in our Ruby-based implementation, which use constraints in a variety of application domains, including interactive graphics, circuit simulations, data streaming with both hard and soft constraints on performance, and configuration file management.

show abstract

“…Thus, Garnet widgets and applications do not have any window manager calls in them, only calls System to the interactors, object-oriented graphics, constraints and object system. [14] Given this analysis, we can re-draw Garnet's architecture as follows:…”

Section: Garnetmentioning

confidence: 99%

SAAM: A Method for Analyzing the Properties of Software Architectures

Kazman¹,

Bass²,

Abowd³

et al. 2007

View full text Add to dashboard Cite

IntroductionSoftware architecture is a topic of growing concern within both the academic and industrial communities. Despite the popularity of this topic, little attention focuses on methods for analyzing a software architecture to show that it satisfies certain properties. Software architectures are primarily motivated by software engineering considerations, or software quality factors, such as maintainability, portability, modularity and reusability. In this paper, we address architectural description and a method of analysis with respect to software quality. The method is demonstrated by means of a case study examining architectures for developing the user interface portion of interactive systems.Over the past decade, changes in the software architecture characterize the advances in support environments for the development of user interfaces. However, it is often difficult to assess a developer's claims of qualities inherent in a software architecture. Examples of such claims are:We have developed … user interface components that can be reconfigured with minimal effort. [20] Serpent … encourages the separation of software systems into user interface and "core" application portions, a separation which will decrease the cost of subsequent modifications to the system. [22] This Nephew UIMS/Application interface is better that [sic] traditional UIMS/Application interfaces from the modularity and code reusability point of views. [26] The difficulty in assessing the validity of these claims arises for two reasons. First, the various architectural descriptions do not use a common vocabulary. When people develop new architectures, they typically develop new terms to describe them, or use old terms in a new way. It is, therefore, difficult to compare these new architectures with existing ones-there is no level playing field. Second, it is often difficult to link architectural abstractions with system development concerns. Developers tend to concentrate on the functional features of their architectures, and seldom address the ways in which their architectures support quality concerns within the system development life cycle.The main goal of this paper, therefore, is to establish a method for describing and analyzing software architectures, called the Software Architecture Analysis Method (SAAM). Before analyzing an architecture, we must first have a way to provide a clear description of it which exposes its main features. We define three perspectives for understanding and describing architectures-functionality, structure and allocation. We also provide a simple language for describing the structural perspective. This language is important because it permits different architectures to be described consistently, forcing a common level of understanding for comparing different architectures. Rick

show abstract

Garnet: comprehensive support for graphical, highly interactive user interfaces

Cited by 381 publications

References 13 publications

Focused interaction in dialogues

Focused interaction in dialogues

Specifying and Solving Constraints on Object Behavior.

SAAM: A Method for Analyzing the Properties of Software Architectures

Contact Info

Product

Resources

About