Results 1 -
9 of
9
Continuous Coordination: A New Paradigm to Support Globally Distributed Software Development Projects
"... 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 ..."
Abstract
-
Cited by 14 (3 self)
- Add to MetaCart
(Show Context)
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
F.: “The Trade-Offs of Blending Synchronous and Asynchronous Communication Services to Support Contextual Collaboration
- In: Journal of Universal Computer Science
"... Abstract: Contextual collaboration seamlessly integrates existing groupware technologies into a uniform user experience that combines synchronous and asynchronous interactions. This user experience is usually supported by a collaboration infrastructure that needs to efficiently cope with the fast s ..."
Abstract
-
Cited by 6 (1 self)
- Add to MetaCart
Abstract: Contextual collaboration seamlessly integrates existing groupware technologies into a uniform user experience that combines synchronous and asynchronous interactions. This user experience is usually supported by a collaboration infrastructure that needs to efficiently cope with the fast switching and integration of different modes of interaction. In this paper, we study a model for contextual collaboration that supports multiple modalities of collaboration. Our model is based on generic shared objects that provide building blocks for supporting contextual collaboration applications. We describe a native implementation of this model and evaluate its behavior under different media traffic conditions. We compare the native implementation with an alternative implementation that integrates existing notification and meeting servers to deliver the same model behavior. We discuss trade-offs and limitations of those two implementations.
Managing Feature Interaction by Documenting and Enforcing Dependencies in Software Product Lines
"... Abstract. Software product line engineering provides a systematic approach for the reuse of software assets in the production of similar software systems. For such it employs different variability modeling and realization approaches in the development of common assets that are extended and configure ..."
Abstract
-
Cited by 3 (0 self)
- Add to MetaCart
(Show Context)
Abstract. Software product line engineering provides a systematic approach for the reuse of software assets in the production of similar software systems. For such it employs different variability modeling and realization approaches in the development of common assets that are extended and configured with different features. The result is usually generalized and complex implementations that may hide important dependencies and design decisions. Therefore, whenever software engineers need to extend the software product line assets, there may be dependencies in the code that, if not made explicit and adequately managed, can lead to feature interference. Feature interference happens when a combined set of features that extend a shared piece of code fail to behave as expected. Our experience in the development of YANCEES, a highly extensible and configurable publish/subscribe infrastructure product line, shows that the main sources of feature interference in this domain are the inadequate documentation and management of software dependencies. In this paper, we discuss those issues in detail, presenting the strategies adopted to manage them. Our approach employs a contextual plug-in framework that, through the explicit annotation and management of dependencies in the software product line assets, better supports software engineers in their extension and configuration.
Understanding the Trade-offs of Blending Collaboration Services in Support of Contextual Collaboration
- In Proc. 12th International Workshop on Groupware, CRIWG 2006
"... Abstract. Contextual collaboration seamlessly integrates existing groupware technologies into a uniform user experience that combines synchronous and asynchronous interactions. This user experience is usually supported by a contextual collaboration infrastructure that needs to efficiently cope with ..."
Abstract
-
Cited by 1 (0 self)
- Add to MetaCart
(Show Context)
Abstract. Contextual collaboration seamlessly integrates existing groupware technologies into a uniform user experience that combines synchronous and asynchronous interactions. This user experience is usually supported by a contextual collaboration infrastructure that needs to efficiently cope with the fast switching and integration of different modes of interaction. This paper experiments with a new model for contextual collaboration based on the notion of generic shared objects. We describe a native implementation of this model and evaluate its behavior under different media traffic conditions. We compare the native implementation with an alternative implementation that integrates existing notification and meeting servers to deliver the same model behavior. We discuss trade-offs and limitations of those two implementations. 1
Research Statement
"... My research so far has focused on the synergetic relationship between Groupware, Middleware and Software Engineering. As computing becomes increasingly ubiquitous, new collaborative tools and applications are created. These applications require novel software infrastructures, or Middleware, that are ..."
Abstract
- Add to MetaCart
(Show Context)
My research so far has focused on the synergetic relationship between Groupware, Middleware and Software Engineering. As computing becomes increasingly ubiquitous, new collaborative tools and applications are created. These applications require novel software infrastructures, or Middleware, that are able to support and evolve with the constant shift of networking and application domain requirements. Novel Software Engineering fundaments and techniques are also required in support of these applications and infrastructures. A common thread in my research has been the development of collaborative tools and their supporting infrastructures, and the multi-dimensional evaluation of the trade-offs involved in their design, development and use. In particular, I focus on both end-users and developers, researching for novel software engineering principles and guidelines that can better support their activities. My Ph.D. work at UC, Irvine, was motivated by the increasing popularity of event-driven applications and their need for application-specific features. In particular, I worked with applications in different areas including: usability monitoring [1], security [2], workspace awareness [3] and contextual collaboration [4]. These applications usually rely on custom-made publish/subscribe infrastructures, developed to meet their specific needs. This observation resulted in my work on YANCEES, a versatile publish/subscribe infrastructure [5], based on plug-ins and extensible languages, that can be extended and customized to meet the requirements of existing
Continuity of User Tasks Execution in Pervasive Environments
, 2013
"... First, I would like to express my deepest sense of gratitude to my supervisor Dr. Djamel Belaïd for his patient guidance, encouragement and excellent advice throughout this study. His constructive suggestions were a source of inspiration and motivation all along my way. I would like also to express ..."
Abstract
- Add to MetaCart
First, I would like to express my deepest sense of gratitude to my supervisor Dr. Djamel Belaïd for his patient guidance, encouragement and excellent advice throughout this study. His constructive suggestions were a source of inspiration and motivation all along my way. I would like also to express my sincere gratitude to my thesis advisor Pr. Guy Bernard for his direction and signi cant feedback.
Managing Feature Interaction by D Documenting ti and dE Enforcing f i Dependencies in Software Product Lines
, 2007
"... redmiles ..."
engineering development tools, Continuous Coordination. Continuous Coordination
"... We introduce and explicate a novel development paradigm for distributed software ..."
Abstract
- Add to MetaCart
(Show Context)
We introduce and explicate a novel development paradigm for distributed software
An Event System Architecture for Scaling Scale-Resistant Services
, 2005
"... Large organizations are deploying ever-increasing numbers of networked compute devices, from utilities installing smart controllers on electricity distribution cables, to the military giving PDAs to soldiers, to corporations putting PCs on the desks of employees. These computers are often far more c ..."
Abstract
- Add to MetaCart
(Show Context)
Large organizations are deploying ever-increasing numbers of networked compute devices, from utilities installing smart controllers on electricity distribution cables, to the military giving PDAs to soldiers, to corporations putting PCs on the desks of employees. These computers are often far more capable than is needed to accomplish their primary task, whether it be guarding a circuit breaker, displaying a map, or running a word processor. These devices would be far more useful if they had some awareness of the world around them: a controller that resists tripping a switch, knowing that it would set off a cascade failure, a PDA that warns its owner of imminent danger, a PC that exchanges reports of suspicious network activity to its peers to identify stealthy computer crackers. In order to provide these higher-level services, the devices need a model of their environment. The controller needs a model of the distribution grid, the PDA needs a model of the battlespace, and the PC needs a model of the network and of normal network and user behavior. Unfortunately, not only might models such as these require substantial computational resources, but generating and updating them is even more demanding. Modelbuilding