This essay compares activity theory (AT) with distributed cognition theory (DCOG), asking what each can do for CSCW. It approaches this task by proposing that theories – when viewed as conceptual tools for making sense of a domain – have four important attributes: descriptive power; rhetorical power; inferential power; and application power. It observes that AT and DCOG are not so different: both emphasize cognition; both include the social and cultural context of cognition; both share a commitment to ethnographically collected data. Starting with a description of the distributed cognition approach, it uses an example of a DCOG analysis to ground a discussion of the strengths and weaknesses of AT and DCOG as an approach to issues in CSCW. Finally, the essay considers what theoretical work is being done by the attributes of the respective theories, and whether AT, DCOG, or any theory developed outside the context of group work, will work for CSCW.

Collaborative software engineering tools that have been developed and used to date exhibit a fundamental paradox: they are meant to support the collaborative activity of software development, but cause individuals and groups to work independently from one another. The underlying issue is that existing tools discretize time and tasks in concrete but isolated process steps. This approach is fundamentally flawed in assuming that human activity can be codified and that periodic resynchronization of tasks is an easy step. We propose a new approach to supporting collaborative work called continuous coordination. The underlying principle is that humans must not and cannot have their method of collaboration dictated, but should be supported flexibly with both the tools and the information to coordinate themselves and collaborate in their activities as they see fit. In this paper, we define the concept of continuous collaboration, introduce our work to date in building some example tools that support the continuous coordination paradigm, and set out a further research agenda to be pursued. 1.

We introduce and explicate a novel development paradigm for distributed software engineering development tools, Continuous Coordination. Continuous Coordination constitutes a paradigm for collaborative systems, which combines elements of traditionally formal, processoriented approaches with those of the more informal, awareness-based approaches, thus addressing some of the issues of global software development:- The lack of awareness and informal communication among developers are factors that contribute to problems arising during global software development. The Continuous Coordination paradigm improves awareness and enables a degree of self-coordination by integrating existing tools (based on formal, process-oriented approaches) with awareness for coordination (based on informal, peripheral and visual cues).- Developers often face challenges when they attempt to integrate artifacts produced by heterogeneous tools. Continuous Coordination is defined in terms of several general design principles which are implemented in new and existing tools. Consequently, practitioners can adopt the paradigm immediately and incrementally; moreover, Continuous Coordination allows them to more readily integrate the artifacts produced. Abstract (English) Along with the rapid globalization of companies, the globalization of software development

Abstract. Workflow Management Systems (WfMSs) are implemented to support the modelling, analysis and enactment of rigidly structured business processes. However, they typically have difficulty supporting unexpected or developmental change occurring in the work practices they model, and are unable to provide adequate support for exceptions, or deviations from the process model, even though such deviations are a common occurrence for almost all processes. These limitations mean a large subset of business practices do not easily translate to the inflexible modelling frameworks imposed by WfMSs, and so has inhibited their wider acceptance. Workflow modelling frameworks are usually based on software programming principles and proprietary formats, which may not be the most ideal base for the support of flexible work practices. A better approach may be to develop a WfMS based on accepted ideas of how people actually work. This paper derives a set of principles for work practice from a sound theoretical base called Activity Theory. These grounded principles are then applied to a set of criteria that a WfMS must meet if it is to provide adequate support for flexible work methods. Commercial workflow products, and some research trends, are discussed in relation to the criteria specified. 1

Abstract. This article presents a model for projects that have to adhere to Enterprise Architecture (EA) in order for their results to be aligned with the broader organization. The model features project artifacts (i.e. deliverables such as Software Architecture Documents), their mutual relationships, their relationship with EA, and the processes in which they are created and tested on conformance. We start with applying Activity Theory to show the crucial mediating role that artifacts have in projects and to identify and justify the new EA-related artifacts we introduce. We subsequently incorporate these findings and existing best practices in a standard systems development approach in order to create a practical model that projects can apply for EA conformance. This model features both new, dedicated EA artifacts, and well-known existing artifacts of which we describe the way they should conform to EA. Finally, two action research studies are used to empirically support the model.

Eingereicht am 2006-09-02, nach zwei Ûberarbeitungen angenommen am 2006-12-05 durch Prof. Dr. König. 1

This paper is a continuation of a series of work based upon a conceptual framework that we have called the “Price of Convenience ” Model. The PoC model was developed as a guide to understand adoption behaviour of mobile innovations. In particular, we are concerned with understanding (1) the manner in which users trade costs (i.e. loss of personal privacy) for the conveniences of a mobile innovation,(2) adoption dynamics work in response to external environment, and (3) the evolution of adoption decisions over time and across behavioural contexts. The paper develops the study of adoption behaviour further by identifying four distinct groups of “adopters ” – described through the concept of ‘community’. We identify four discrete formulations of the 'community ' concept as it pertains to the Price of Convenience debate. The paper concludes with the introduction of a behavioural economic research perspective suitable for quasi-experimental research on adopter responses to PoC dimensions of mobile applications. Specifically, the 'social learning ' sub-field of behavioural economics is offered as a complementary body of social science theory that may be employed by all institutional parties to the issue. 144 1.

The paper describes a multi-perspective approach to measuring dynamics of end-user encounters with innovative artefacts and services which fall into the class broadly described as pervasive Information Systems and which includes m-commerce systems and devices. This working framework is based on the "Model of User Acceptability and Product Uptake" which, in turn, is drawn from the "Price of Convenience (PoC)" model [1]. We model the framework as consisting of multiple system actors with a variety of influence, interests and functionalities.

Interfaces in adoption of an evolving innovation Interfaces in adoption of an evolving innovation: An