R. K. Keller, M. Cameron, R. N. Taylor, and D. B. Troup. User interface development and software environments: The Chiron-1 system. In Proc. of the Thirteenth Int. Conference on Software Engineering, pages 208--218, May 1991.  Home/Search   Document Not in Database   Summary   Related Articles   Check

....management system [31] part of the Arcadia environment [15] de nes a complex and exible model of objects as unrestricted abstract data types (ADTs) The Pleiades paper does not address integration at the presentation and control levels. However, the Chiron user interface management system [16], which is also part of Arcadia, manages presentation and control with artists, each of which handles a single abstract data type. Artists, in this model, are just as separate as tools in Field; there is no mechanism by which artists for related abstract data types may share their implementation. ....

....they apply. They are written in a simple, declarative language and each one applies to an entire document class. Limited support for multiple presentations can be found in several other systems. The SUIT user interface toolkit [24] provides multiple widgets for certain simple objects. Chiron [16] can support an arbitrary number 6 of artists for the same abstract data type. However, an artist de nes both presentation and interaction and is written in a superset of Ada. Thus, artists are more heavyweight than Ensemble presentations and are not intended for customization by end users. The ....

Rudolf K. Keller, Mary Cameron, Richard N. Taylor, and Dennis B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pages 208-218, Austin, TX, May 1991.

....textual user interfaces to ProDAG. The graphical user interface (GUI) provides graphical depictions of CFGs and DGs as well as a textual representation of the source code annotated with CFG node numbers. The depictions in Figures 3 and 4 are snapshots taken from the GUI we implemented with Chiron [KCTT91] that GUI is described in [RB93a] The GUI also allows the user to obtain various pieces of information associated with nodes and edges and provides the filtering capabilities mentioned above. The GUI is particularly useful for browsing dependences and software understanding. Dependence ....

Rudolf K. Keller, Mary Cameron, Richard N. Taylor, and Dennis B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pages 208--218, Austin, TX, May 1991.

....attribute fields with sophisticated type structure. The EDIT module also interacts with the whiteboard to guarantee that users do not attempt to edit nodes they have not previously locked. An additional reason for decomposing REBUS into modules was to allow effective interaction with the Chiron [KCTT91b] user interface development system. Chiron is designed to provide wrappers (termed artists ) around abstract data type (ADT) instances so that operations on the ADT and outputs from the ADT are mediated through Chiron to provide a consistent user display of the state of the ADT. Chiron artists ....

....system. An example screen image of the user interface to the REBUS tool is given in Figure 6, which shows a partial DAG for a Library Information System. We are currently implementing a fully interactive user interface to the REBUS tool using the Chiron user interface development system [KCTT91a, KCTT91b] Our experience with using both the REBUS formalism and the executable prototype system is summarized in the following observations: ffl REBUS has provided useful guidance and coordination in the requirements specification process, thus addressing given requirements for user interaction and ....

Rudolf K. Keller, Mary Cameron, Richard N. Taylor, and Dennis B. Troup. User interface development and software environments: The chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pages ?--?, Austin, TX, May 1991.

....benefit of the object oriented approach in Macrotec is the use of Gemstone together with its C interface which has led to an efficient database interface. To prototype the user interface of Macrotec, we ran several user interface development cycles, using tools such as HyperCard and Chiron 1 [KCTT91] The integration of several standalone tools with their own graphical user interface was an incentive to meet (or surpass) the usability criteria of each. As our system evolves, with new external tools requiring integration, we will be in a better position to determine how easily our system can ....

Rudolf K. Keller, Mary Cameron, Richard N. Taylor, and Dennis B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pages 208--218, Austin, TX, May 1991.

....interest to them. The first behavior was demonstrated in the GEM implementation discussed above. The second type of behavior is frequent in user interface applications, where it is desirable that the interface remain responsive even while engaged in lengthy service operations. 4. 3 Chiron Chiron [42, 22] is a user interface development system (UIDS) supporting the user interface needs of the Arcadia environment. It emphasizes the value of separating the application from the graphical user interface (GUI) by means of a client server split. Figure 4.10 depicts the Chiron architecture for achieving ....

Rudolf K. Keller, Mary Cameron, Richard N. Taylor, and Dennis B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pages 208--218, Austin, TX, May 1991.

....special case, providing the designer with a more versatile medium for conceiving and representing systems. The APPL A system provides a model for concurrency control lacking in the mediator approach. Marrying the strengths of these efforts is a promising research direction. 9.2. 3 Chiron Chiron 1 [Keller, Cameron, Taylor, and Troup 91] also exhibits what can be seen as a special case of the mediator method. In Chiron 1, artist objects maintain consistency between arbitrary objects and objects called abstract depictions, representations from which a concrete, graphical displays of the underlying objects can readily be ....

R.K. Keller, M. Cameron, R.N. Taylor, and D.B. Troup, "User Interface Development and Software Environments: The Chiron-1 System," Proceedings of the 13th International Conference on Software Engineering, May, 1991, Austin, Texas, pp. 208--218.

....have been standardized. Interface standardization enables researchers to investigate heterogeneous solutions to similar problems, to interchange component implementations, and to facilitate environment reconfiguration. As one example use of standardized interfaces in Arcadia, the Chiron UIDS [10] provides a standard interface to two different look and feel presentations: XView and Motif. Another example is the SMI storage manager interface, which provides a standard interface to various underlying storage managers, including Exodus [5] Mneme [15] and Ada s direct I O files. On the ....

R. K. Keller, M. Cameron, R. N. Taylor, and D. B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pages 208--218, Austin, TX, May 1991.

....The first behavior was demonstrated in the GEM implementation discussed above. The second type of behavior is frequent in user interface applications, where it is desirable that the interface remain responsive even while engaged in lengthy service operations. 3. 3 Experience with Version 2 Chiron [9] is a user interface development system (UIDS) supporting the user interface needs of the Arcadia environment. It emphasizes the value of separating the application from the graphical user interface (GUI) by means of a client server split. Figure 6 depicts the Chiron architecture for achieving ....

Rudolf K. Keller, Mary Cameron, Richard N. Taylor, and Dennis B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pages 208--218, Austin, TX, May 1991.

....appearing in incorrect halves of the screen. 3] IncorrectSquares Same as the CorrectSquares example except that insufficient synchronization results in the possibility of drawing non square rectangles. 3] Chiron Our implementation of an instantiation of a Chiron user interface architecture [7]. Written by the authors based on the Ada example Phil The dining philosophers example with three philosophers sitting in a circle. Each of the philosophers alternates between eating and thinking. To eat, a philosopher must acquire two forks, each of which it shares with one of its neighbors. ....

R. K. Keller, M. Cameron, R. N. Taylor, and D. B. Troup. User interface development and software environments: The chiron-1 system. In Proceedings of the 13th International Conference on Software Engineering, pages 208-- 218, October 1991.

....mentioned in the previous section shows that this promise can be realized under Interviews. However, neither system provides any support for multiple presentations. In fact, in both systems, there is little separation between the representation of an object s meaning and its appearance. The Chiron [35, 76] user interface development system does support multiple presentations. The central concept in Chiron is that of the artist, which is an agent responsible for managing the appearance of an abstract data type (ADT) and the user s interaction with the ADT. A single ADT may have any number of artists ....

....between language representations and other representations. Furthermore, what Proteus does provide (i.e. the ability to display one document in 78 a variety of styles) is not supported in any way by these multiple representation systems. Only two other interactive systems, Grif [66] and Chiron [35], actually provide general support for multiple presentations. Grif supports multiple presentations through its view mechanism. The author of a presentation schema can specify several views in that schema. Different views can have very different appearances, but some presentation rules must be ....

[Article contains additional citation context not shown here]

Rudolf K. Keller, Mary Cameron, Richard N. Taylor, and Dennis B. Troup. User interface development and software environments: The Chiron-1 system. In Thirteenth International Conference on Software Engineering, pages 208--218, Austin, TX, May 1991.

....The structure of the system is the organization and interactions of those parts. Ossher 1987, p. 219] To give a sense of the reason for this broad definition, consider the variety of structural information in the artifacts of two example software systems the Chiron user interface system [Keller et al. 1991] and the GNU groff document formatting system. These two systems were chosen as examples for three reasons. First, the artifacts comprising the systems are publicly available. 1 Second, the systems are implemented in different programming languages; Chiron is implemented primarily in Ada [GPO ....

Keller, R., Cameron, M., Taylor, R., and Troup, D. 1991. User interface development and software environments: The Chiron-1 system. In Proceedings of the 13th International Conference on Software Engineering. IEEE Computer Society Press, Los Alamitos, CA, 208--218.

....The first behavior was demonstrated in the GEM implementation discussed above. The second type of behavior is frequent in user interface applications, where it is desirable that the interface remain responsive even while engaged in lengthy service operations. 3. 3 Experience with Version 2 Chiron [26, 11] is a user interface development system (UIDS) supporting the user interface needs of the Arcadia environment. It emphasizes the value of separating the application from the graphical user interface (GUI) by means of a client server split. Figure 6 depicts the Chiron architecture for achieving ....

Rudolf K. Keller, Mary Cameron, Richard N. Taylor, and Dennis B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pages 208--218, Austin, TX, May 1991.

....sophisticated renderings of programs, their structure must be explicitly defined by the user, rather than deduced by analysis of a text stream. Furthermore, Grif is largely limited to the textual medium and cannot be extended to support new media. The Chiron user interface development system [9, 24] is another influence on our work. A central concept in Chiron is that of the artist, which is an agent responsible for managing the appearanceof an abstract data type (ADT) The Chiron system provides a server that renders user interface objects like buttons and scroll bars and that multiplexes ....

....Some of our earlier research explored using a general purpose constraint system as the core of the presentation system. This work led us to believe that the performance of the general purpose solution is inadequate for a presentation system. Proteus bears an architectural resemblance to Chiron [9, 24]. Both systems have a centralized service that provides presentation services to clients. Both systems help clients adapt to their model by generating interfaces for them. The interface between Chiron and its artists seems to be quite similar to that between Proteus and the formatters of Ensemble. ....

Rudolf K. Keller, Mary Cameron, Richard N. Taylor, and Dennis B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the 13th International Conference on Software Engineering,pages 208--218, Austin, TX, May 1991.

....an appropriate process which can be monitored and improved on an ongoing basis. Nazim H. Madhavji from McGill University initiated the effort of defining such a process three years ago. We have joined this effort and have developed, based on our experience in software process engineering [Mad91, KCTT91] a Comprehensive Paper Process (CP process) model which we have applied, improved and validated over the past two years at CRIM and McGill University. A key aspect of this process is weekly group discussion sessions. In these sessions, software engineering papers are presented, discussed, ....

....HyperRef and discuss extensions to the system. 2 A new Approach for Paper Assessment and Documentation An appropriate way to describe our approach are process models. Such models provide a solid basis for process improvement, training, adaptation, reuse, and design of a measurement program [KCTT91] In this section, we shall first introduce the CP process model which encompasses our whole approach. Thereafter, we shall detail its core component, the PD process model. 2.1 The CP Process Model The CP process model describes the processes, products and dependencies that typically occur in a ....

Rudolf K. Keller, Mary Cameron, Richard N. Taylor, and Dennis B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pages 208--218, Austin, TX, May 1991. IEEE.

....developers to identify the appropriate tools. Moreover, despite of the host of available tools, they often do not adequately respond to the particular needs at hand. These concerns, voiced, for instance, by several members of our organization, 1 and our personal needs as tool builders and users [KCTT91, KOS94] made us start the EVODIPS project [DK93] The goals of EVODIPS are threefold. First, we want to explore the requirements for UI tools as expressed by industry and research by means of a UI tool survey. Second, we aim at providing a UI tool selection guide, which is a database containing ....

Rudolf K. Keller, Mary Cameron, Richard N. Taylor, and Dennis B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pages 208--218, Austin, TX, May 7/7 1991. IEEE.

....levels of abstraction of various tools and systems. It should teach students to build systems based on appropriate models of abstraction and to cope with various design tradeoffs. Students should get a feel for the influence of software and software architectures on the resulting user interface [2], and for the implications of technical choices on the entire system. Evolving Systems. Software evolution should be made a central topic in software engineering education. Design for reuse and evolution is difficult to teach, but the study of good examples of software architectures and design ....

R. K. Keller, M. Cameron, R. N. Taylor, and D. B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pages 208--218, Austin, TX, May 1991. IEEE.

....from deadlock and to highlight the problem of spurious error reports caused by data folding. A solution for this case, namely unrolling the loop in the butler, was analyzed. The practical potential of static analysis with Cats is demonstrated by its application to the runtime environment of Chiron [KCTT91], a highly concurrent user interface development system. These examples exercised all of the components of Cats. The dining philosophers examples used the complete system, from source code translation through error reporting. The Chiron exercise was performed before one component, TIGGER, was ....

....case when an eliminated variable was used to keep track of the states of other tasks, since the value of the variable is purely a function of those states. This is clearly the best case for selective unrolling with partial evaluation. Chiron 1.2 The Chiron 1. 2 user interface development system [KCTT91] represents a modern, moderate size system 7 . It includes a reasonably complex task structure and was not designed to be analyzed (it is not a toy example) The implementation includes two languages, Ada and C . The user interface developer builds one or more artists for the application; a ....

Rudolf K. Keller, Mary Cameron, Richard N. Taylor, and Dennis B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pages 208--218, Austin, TX, May 1991.

....and hence for process improvement, training, adaptation, reuse, and design of a measurements programme. All these issues are important in both, the paper study process as well as the software development process. As part of our research in the area of software process [Mad91, MS91, Mad92, MTH92, KCTT91, EMT93, MEB93] Madhavji initiated in June 1990, and has led the effort in institutionalising, a process for studying software process papers. A key aspect of this process is the weekly group discussion session. In these sessions software process and related papers are presented, discussed, ....

Rudolf K. Keller, Mary Cameron, Richard N. Taylor, and Dennis B. Troup. User interface development and software environments: The Chiron-1 system. In Proc.Thirteenth Intl Conference on Software Engineering, pages 208-- 218, Austin, TX, May 1991.

No context found.

R. K. Keller, M. Cameron, R. N. Taylor, and D. B. Troup. User interface development and software environments: The Chiron-1 system. In Proc. of the Thirteenth Int. Conference on Software Engineering, pages 208--218, May 1991.

No context found.

R.K. Keller, M. Cameron, R.N. Taylor, and D.B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pp. 208--218, May 1991.

No context found.

R.K. Keller, M. Cameron, R.N. Taylor, and D.B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pp. 208--218, May 1991.

No context found.

R. K. Keller, M. Cameron, R. N. Taylor, and D. B. Troup. User interface development and software environments: The Chiron-1 system. In Proceedings of the Thirteenth International Conference on Software Engineering, pages 208--218, Austin, TX, May 1991.

No context found.

Rudolf K. Keller et al. User interface development and software environments: The Chiron-1 System. In Proc. 13th International Conference on Software Engineering, 1991.

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC