Characterizing traits of coordination

How can one recognize coordination languages and technologies? As this report shows, the common approach that contrasts coordination with computation is intellectually unsound: depending on the selected understanding of the word "computation", it either captures too many or too few programming languages. Instead, we argue for objective criteria that can be used to evaluate how well programming technologies offer coordination services. Of the various criteria commonly used in this community, we are able to isolate three that are strongly characterizing: black-box componentization, which we had identified previously, but also interface extensibility and customizability of run-time optimization goals. These criteria are well matched by Intel's Concurrent Collections and AstraKahn, and also by OpenCL, POSIX and VMWare ESX.Comment: 11 pages, 3 table

An Architecture for Multi-User Software Development Environments

We present an architecture for multi-user software development environments, covering general, process-centered and rule-based MUSDEs. Our architecture is founded on componentization, with particular concern for the capability to replace the synchronization component - to allow experimentation with novel concurrency control mechanisms - with minimal effects on other components while still supporting integration. The architecture has been implemented in the MARVEL SD

Analysis of component-based approaches toward componentized 5G

5G is expected to be modular by design toward autonomic and agile networks. In this regards, the 5G functional architecture is designed as service-based seeking to support the concept of Network Slicing. This leads us to the question: what componentization approach to implement this modular architecture? Is there a componentization approach that is suitable for all the network functions? Which design approach will help to have autonomic and cognitive networks? In this paper we shed the light on the different component-based approaches. In addition, we reviewed the state of the art addressing the applicability of component-based approaches to build autonomic networks. Therefore, we present discussion, comparison and synthesis as input to 5G related activities

Incremental Process Support for Code Reengineering

Reengineering a large code base can be a monumental task, and the situation becomes even worse if the code is concomitantly being modified. For the past two years, we have been using the Marvel process centered environment (PCE) for all of our software development and are currently using it to develop the Oz PCE (Marvel's successor). Towards this effort, we are reengineering Oz's code base to isolate the process engine, transaction manager, and object management system as separate components that can be mixed and matched in arbitrary systems. In this paper, we show how a PCE can guide and assist teams of users in carrying out code reengineering while allowing them to continue their normal code development. The key features to this approach are its incremental nature and the ability of the PCE to automate most of the tasks necessary to maintain the consistency of the code base

Project quality management in virtual environments : a primer

The rise of geographically dispersed project teams enabled by technology has made project quality management a significant challenge for organizations. This paper uses findings from a project on geographically dispersed, cooperating SMEs in the building trade, to explore whether concepts and artefacts from the Rational Unified Process&reg; (RUP&reg;) software development approach could be adapted and used to better manage quality in virtual projects. Our future research aims to explore the use of RUP artefacts in a virtual environment and their impact onproject management and quality.<br /

A Knowledge-Based Agent Modeling and Design Environment

Agent-oriented software systems are becoming large and complex. This paper presents a methodology for agent-oriented software development, grounded in software engineering principles. It also presents a knowledge-based agent modeling and design environment that supports different phases of the agent-software lifecycle