Social Business - The CIO's Guide to Oracle Products and Solutions - page 124

Continuous coordination,
Collaborative architecture
Seamless development environments

Seamless

Passive awareness of
development activities
and developers, manage
information overload

Advanced conflict
detection

Collocation benefits to
distributed development

Passive

Instant messaging,
monitoring
changes to artifacts

Fine grained
versioning, conflict
resolution

Organizational memory,
knowledge acquisition and
dissemination, social navigation

Proactive

Communication archival
along with artifacts

Parallel development,
roles and access rights

Prescribed and defined and
coordination support

Defined

Assess to a common
set of artifacts,
isolated workplaces
and version control

Asynchronous
communication

Task allocation and
assignment

Functional

Communication Artifact Management Task Management

FIGURE 4.4
Collaboration framework.

the requirements of the collaborative tool set. Whitehead (2007) catego-
rizes collaborative software engineering tools into four groups:

1. Model-based collaboration tools

2. Process support tools

3. Collaboration awareness tools

4. Collaboration infrastructure tools

On the other hand, Sarma's (2005) framework classifies tools based on
the required effort to collaborate effectively. The framework consists of
five layers and three strands, as shown in Figure 4.4. The layers are tools,
and strands are critical needs that permeate all aspects of collaboration.
As is often the case, many of the tool sets discussed in the literature are
experimental and are not offered for use by those in the field. In 2003,
Booch and Brown surveyed both experimental and commercial collab-
orative development environments (CDE). Their definition of a CDE is a
virtual space wherein all the stakeholders of a project, even if distributed