The appropriation of a software ecosystem : a practice take on the usage, maintenance and modification of the eclipse IDE

This thesis was written in order to gain a deeper understanding of the appropriation of software in groups and organizations. In doing so, it focuses on software created under the modern software engineering trend software ecosystems. Software ecosystems have a major influence on software development, as they rely on massive usage of distributed software development, open source models and modularization. It is unclear if existing models to explain appropriation still hold good. Furthermore, it has to be explored whether current appropriation support is still appropriate and beneficial or if we need new ideas to help users cope with these developments. In order to achieve these objectives, this work is mainly based on an empirical field study, which investigates workgroups at seven German organizations that use the Eclipse IDE, an extremely modularized and adaptable software system, developed by a globally active ecosystem of large corporations, small businesses and even hobbyists. Using the qualitative analysis approach of the grounded theory method and appropriation as a lens for this research endeavor, observations and interviews as well as artifacts were analyzed, uncovering practices that are part of Eclipse usage and appropriation. They are identified and discussed from the backdrop of software ecosystems – viewed from a users perspective. Examples are the sheer amount of appropriation activities at the shop floor, the dilemma of software maintenance, that comes with continuously developed but sometimes unstable technology, practices as learning or tailoring, influences on practices stemming from the software ecosystem, the organization and the group. Grounded in these results, suggestions for the design of appropriation support are given and prototypically implemented, which reflect the embeddedness of individuals and groups in the software ecosystem. They provide a fresh perspective, based on peer-to-peer technology and awareness mechanisms.Diese Arbeit wurde erstellt, um ein tieferes Verständnis über die Aneignung von Software in Gruppen und Organisationen zu erlangen. Dabei fokussiert sie auf eine Software die unter den Bedingungen eines modernen Trends im Software Engineering entstanden ist: Der Software Ökosystem Bewegung. Software Ökosysteme beeinflussen die Entwicklung von moderner Software maßgeblich, da sie verstärkt auf örtlich verteilte Entwicklung, Open Source Modelle und Modularisierung setzen. Bisher ist ungeklärt, ob existierende Ansätze zum Verständnis von Aneignung unter diesen Gegebenheiten ihre Gültigkeit behalten. Weitergehend ist zu untersuchen ob existierende Maßnahmen der Aneignungsunterstützung auch in diesem Kontext angemessen und vorteilhaft wirken, oder ob neue Ansätze entwickelt werden müssen um Nutzer heute sinnvoll zu unterstützen. Um diese Ziele zu erreichen, basiert diese Arbeit hauptsächlich auf einer qualitativ-empirischen Feldstudie in Arbeitsgruppen sieben Deutscher Organisationen, die alle die Eclipse IDE einsetzen – ein extrem modularisiertes und anpassbares Software System das durch ein global agierendes Software Ökosystem aus großen Konzernen, KMU und sogar Hobbyisten hergestellt wird. Mit Hilfe des qualitativen Analyseansatzes in Form der Grounded Theory Method und Aneignung als Linse für dieses Forschungsvorhaben wurden die Daten aus Beobachtungen, Interviews und bei Arbeitsplatzbesuchen gesammelter Artefakte analysiert. Dabei wurden Praktiken die Teil der Eclipse Nutzung und Aneignung sind, erfasst näher definiert und vor dem Hintergrund von Software Ökosystemen und aus Perspektive der Nutzer diskutiert. Die Ergebnisse umfassen unter anderem eine Reihe verschiedener Aneignungsaktivitäten, das Dilemma der Wartung komplexer Software Systeme welche durch die kontinuierliche Entwicklung und teilweise instabile Komponenten entsteht, Praktiken wie Lernen oder Anpassen, sowie Einflüsse auf die Arbeitspraktiken die aus dem Software Ökosystem, der Gruppe oder der Organisation stammen. Begründet auf den Ergebnissen dieser Forschung, werden Vorschläge für das Design von Aneignungsunterstützung gegeben und prototypisch realisiert. Diese spiegeln wider wie Individuen und Gruppen in das Software Ökosystem eingebettet sind und präsentieren durch den Einsatz von Peer-to-Peer Technik und Awareness Mechanismen eine neue Perspektive auf Aneignungsunterstützung

Fostering Continuous User Participation by Embedding a Communication Support Tool in User Interfaces

This paper critically reviews previous IS literature on user participation and argues that the literature is mainly empirically or normatively oriented and lacks design research on developing system prototypes in order to foster continuous user participation. It then contributes to the current research by introducing a system prototype, a communication tool that enables users to participate while using their application systems in their work contexts. The prototype provides different communication channels for supporting user-designer communications and knowledge sharing among users with respect to application usage. When integrated in the interface of an application system, the tool can help to adapt and redesign the application. The initial evaluation of the communication tool within the context of an application system indicates its usefulness and usability

Keeping the Development Environment Up to Date - A Study of the Situated Practices of Appropriating the Eclipse IDE

Software engineers and developers are surrounded by highly complex software systems. What does it take to cope with these? We introduce a field study that explores the maintenance of the Eclipse Integrated Development Environment by software developers as part of their daily work. The study focuses on appropriation of the Eclipse IDE. We present an empirical view on appropriation as a means to maintain the collective ability to work. We visited seven different organizations and observed and interviewed their members. Each organization was chosen to provide an overall picture of Eclipse use throughout the industry. The results decompose the appropriation of Eclipse by software developers in organizations into four categories: learning, tailoring and discovering, as well as the cross-cutting category: collaboration. The categories are grounded in situations that provoked a need to change as well as in policies adopted for coping with this need. By discussing these categories against the background of Eclipse and its ecosystem, we want to illustrate in what ways appropriation of component- or plugin-based software is nowadays a common and highly complex challenge for Eclipse users, and how the related appropriation practices can be supported by IT systems