The existing service discovery infrastructure with UDDI as the de facto standard, is limited in that it does not support more complex searching based on matching business processes. Two business processes match if they agree on their simple services, their processing order as well as any mandatory or optional requirements for the service. This matching semantics can be formalized by modelling business processes as annotated finite state automata (aFSAs) and deciding emptiness of the intersection aFSA. Computing the intersection of aFSAs and deciding emptiness are computationally expensive, being more than quadratic on the number of states and transitions, thus does not scale for large service repositories. This paper presents an approach for indexing and matching business processes modeled as aFSAs, for the purpose of service discovery. Evaluation of this approach shows a performance gain of several orders of magnitude over sequential matching and a linear complexity with regard to the data set size. 1

Many software production processes advocate rigorous development testing alongside normal code writing, which implies that both test code and production code should co-evolve. To gain insight in the nature of this co-evolution, this paper proposes three views (realized by a tool called TeMo) that combine information from a software project's versioning system, the size of the various artifacts and the test coverage reports. We validate these views against two open source and one industrial software project and evaluate our results both with the help of log messages, code inspections and the original developers of the software system. With these views we could recognize different co-evolution scenarios (i.e., synchronous and phased) and make relevant observations for both developers as well as test engineers

Abstract. Nowadays there is a great effort underway to improve the World Wide Web. A better content organisation, allowing automatic processing, leading to the Semantic Web is one of the main goals. In the light of bringing this technology closer to the Software Engineering community we propose an architecture allowing an easier development for ontology-based applications. Thus, we first present a methodology for ontology creation and automatic code generation using the widely adopted CASE UML tools. And based on a study of the art of the different RDF storage and querying systems, we couple this methodology with the Sesame system for providing a framework able to deal with large knowledge bases. 1

It is crucial to understand users ’ perceptions of virtual environments, if they are to be adopted as a platform for other research. Existing research has focused primarily on the user’s reaction to the environment as a whole and to physical display qualities, but rarely on differences of user perceptions between real and virtual content. In this paper, we present work that indicates that simple virtual and real objects are perceived very similarly, but with a few critical differences. A method for directly comparing user perception of virtual and real environments is developed, based on perceived affordances of individual objects. The results of a study using this method indicate that critical differences exist in certain aspects of object perception across virtual and real spaces. Notably, users perceive more destructive actions with virtual objects than real and are more playful with the virtual objects. Additionally, the study indicates that perceptual differences exist across certain demographics, namely gender and gaming experience. These results indicate that performing perceptual based research with virtual environments is viable, but needs careful consideration. 1.

Abstract. Nowadays, MDA is gaining popularity as a feasible way to develop software in Web environments. As a consequence, several tools from both academic and industrial contexts, offer their own MDA processes for producing Web Applications. OO-Method is an object-oriented method that produces software systems by means of its MDA implementation, OlivaNOVA. This tool has been broadly tested in industry with real desktop applications. However, it lacks the expressivity needed to accurately describe Web Systems. OOWS is the web-oriented extension of OO-Method with was developed to solve this problem. This work, presents a MDA development environment that combines OO-Method and OOWS. This environment produces fully functional Web Applications that integrate the business logic generated by OlivaNOVA with a Web Interface produced from OOWS models. The followings tools are introduced to support OOWS development process: (1) an Eclipse-based modeller to edit OOWS models visually (2) a Web Interface Framework that is based on Software Factories philosophy in order to reduce the abstraction level between conceptual models and the code to be generated and (3) a set of Model-to-Text transformations that allows the automatic generation of a Web Interface from models. This work also describes a strategy to include the OlivaNOVA development process into the new MDA development environment. 1

Abstract not found

Abstract not found

This paper proposes a decentralized, distributed and secure communication infrastructure for indexing and retrieving multimedia contents with associated digital rights. The lack of structured metadata describing the enormous amount of multimedia contents distributed on the the web leads to simple search mechanisms that usually are limited to queries by title or by author. Our approach is based on structured peer-topeer networks and allows complex queries using standard MPEG-7 and MPEG-21 multimedia metadata. Moreover, security aspects limit the development of general purpose real applications using a peer-topeer routing infrastructure for sharing digital items with an associated license. Accordingly, we propose a framework made up of a secure Distributed Hash Table layer based on Kademlia, including an identity based scheme and a secure communication protocol, providing an effective defense against well known attacks. Povzetek: Predstavljen je sistem za učinkovito indeksiranje in doseganje digitalnih vsebin. 1

Writing this doctoral thesis and doing all the research that led up to it was a lot of work and took considerable time. There are also some other people, besides myself, who have invested time and energy into this PhD. My advisors, Stefanie Lindstaedt and Luciano Serafini, dedicated both time and patience to me and this work. They encouraged my ideas and pushed me to go on and work on them, for which I am truly grateful. Luciano specifically has read some parts of my thesis in many more versions than is human, and gave me useful feedback every time. I also shared interesting discussions with colleagues at the Knowledge Management Institute and the Know-Center, as well as with people at conferences, and I am glad for every input I got over the years from everyone. Specific honours and thanks in this regard go to my colleague and ‘PhDsister’ Barbara Kump, with whom I’ve shared quite a few ups and downs. Speaking of the Knowledge Management Institute and the Know-Center, the last but not the least thanks go to Klaus Tochtermann who heads both, and in doing so manages to provide a research environment which I experienced both as relaxed and motivating. Throughout all of this I had friends, my mother and sister and the man of my life. Especially

Abstract—An anti-pattern is a commonly occurring solution to a recurring problem that will typically negatively impact code quality. Code smells are considered to be symptoms of anti-patterns and occur at source code level. The lifespan of code smells in a software system can be determined by mining the software repository on which the system is stored. This provides insight into the behaviour of software developers with regard to resolving code smells and anti-patterns. In a case study, we investigate the lifespan of code smells and the refactoring behaviour of developers in seven open source systems. The results of this study indicate that engineers are aware of code smells, but are not very concerned with their impact, given the low refactoring activity. I.