Abstract not found

Previous research has shown that rotation and orientation of items plays three major roles during collaboration: comprehension, coordination and communication. Based on these roles of orientation and advice from kinesiology research, we have designed the Rotate’N Translate (RNT) interaction mechanism, which provides integrated control of rotation and translation using only a single touch-point for input. We present an empirical evaluation comparing RNT to a common rotation mechanism that separates control of rotation and translation. Results of this study indicate RNT is more efficient than the separate mechanism and better supports the comprehension, coordination and communication roles of orientation.

Refactoring ---transforming code while preserving behaviour --- is currently considered a key approach for improving object-oriented software systems. Unfortunately, all of the current refactoring tools depend on language-dependent refactoring engines, which prevents a smooth integration with mainstream development environments. In this paper we investigate the similarities between refactorings for Smalltalk and Java, derive a language-independent meta-model and show that it is feasible to build a languageindependent refactoring engine on top of this meta-model. Our feasibility study is validated by means of a tool prototype which uses the same engine to refactor both Smalltalk and Java code. Using our approach we minimize the language -dependent part of refactoring tools, providing a standard way for programmers and tools to perform refactorings no matter what language they work in. 1. Introduction Refactoring is defined as "changing a system to improve its internal structure withou...

In this paper, we present a collection of aspect-oriented refactorings covering both the extraction of aspects from objectoriented legacy code and the subsequent tidying up of the resulting aspects. In some cases, this tidying up entails the replacement of the original implementation with a different, centralized design, made possible by modularization. The collection of refactorings includes the extraction of common code in various aspects into abstract superaspects. We review the traditional object-oriented code smells in the light of aspectorientation and propose some new smells for the detection of crosscutting concerns. In addition, we propose a new code smell that is specific to aspects.

Test-driven development creates software in very short iterations with minimal upfront design. Poised for widespread adoption, TDD has become the focus of an increasing number of researchers and developers.

In the past, architectures of Augmented Reality systems have been widely different and taylored to specific tasks. In this paper, we use the example of the SHEEP game to show how the structural flexibility of DWARF, our componentbased Distributed Wearable Augmented Reality Framework, facilitates a rapid prototyping and online development process for building, debugging and altering a complex, distributed, highly interactive AR system.

This paper examines the use of the Unified Modeling Language (UML) as a representation for interaction design. We discuss the trade-offs related to applying UML outside its intended application domain and the suitability of UML components for modeling various aspects of interaction: representing user requirements, early envisionment of interaction, task modeling, navigation and detailed interaction specification. Where appropriate we propose and illustrate the combination of UML with purpose-specific notations.

Fourth year students run their own software house which involves them in carrying out real projects for real business clients. This year we have introduced them to extreme programming and we examine the initial impact that this has had on their business. The philosophy has been adopted with much enthusiasm and seems to have delivered in a variety of contexts, including maintenance and new projects. Some plans for a more rigorous experiment looking at the possible benefits of XP are also described.

This paper presents a single case study reporting the experiences of introducing extreme programming (XP) in a small development project at Online Telemarketing in Lund, Sweden. The project was a success despite the fact that the customer had a poor idea of the system required at the start of the development. This success is partly due to the introduction of practically all of the XP practices. The practices that worked best were the planning game, collective ownership and customer on site. The practices that were found hard to introduce and not so successful were small releases and testing.

Industrial practice in software engineering has developed in recent years from rigid heavyweight document-based development techniques, such as the Rational Unified Process, to incorporate more agile, iterative, communication-centric approaches such as Extreme Programming. This shift has created a need for a similar shift in software engineering education. We report our experience of incorporating an Extreme Programming option into an existing document-centric software project course. While students taking the option were generally positive about Extreme Programming, the projects' external clients had a more mixed experience.