documents, messages, etc. in order to achieve the
joint goals. In addition to this, project management
tools or projectware, which form a subset of collab-
orative software, cope with task interdependencies in
order to coordinate the various activities making up
the project.
Different architectural models have been used for
implementing collaborative software. The two main
models are the classical client-server architecture,
where each user runs a specific client application to
access the collaborative space, and the web-based ar-
chitecture, where the role of the client is played by a
general-purpose web browser. This latter model has
evolved to the cloud paradigm, whereby all the nec-
essary resources, including applications and data, re-
side in a network of virtual servers (National Institute
of Standards and Technology, 2011), and is rapidly
becoming more and more widespread.
One of the most popular collaborative tools today
is Google Apps (Google Inc., nd), based on cloud
technology, and encompassing applications like joint
editing of documents, presentations and spreadsheets,
polls and surveys, forums, virtual meetings, hangouts,
etc. Google Drive is the specific application within
Google Apps to manage the storage and sharing of
such resources. Another collaborative tool is Zoho
(Zoho Corp., 2013), an office suite that comprises
a number of components, grouped into business ap-
plications, productivity applications, and collabora-
tion applications. The latter include Zoho Chat, Zoho
Docs, Zoho Projects, etc. The Yammer service (Yam-
mer Inc., 2014) is another example of a tool that can
be used in a corporative environment for communi-
cation between its members. It is usually cited as an
“enterprise social network”, but it can be used in sce-
narios other than businesses. More recently, Asana
(Asana, nd) has been developed as a teamwork tool
for managing conversations and tasks in a more flex-
ible way than simple e-mail exchange. As of today,
there are dozens of different collaborative tools avail-
able, and their characteristics have been compared in
many studies, e. g. Reixa et al. (2012), Dr
˘
aghici et al.
(2013), etc.
Like many others, Google Apps, Zoho and Asana
are online services following the “software as a ser-
vice” (SaaS) model. In these systems, all data (doc-
uments, calendars, conversations, etc.) and the appli-
cation itself do not reside in the user’s computer or
device but in the server or servers supplied by the
service provider, i. e. in “the cloud”. The case of
Yammer, although the server-side application is more
characteristic of a social network, can also be in-
cluded in this category.
The four examples of collaborative tools men-
tioned above are available for free, under certain con-
ditions for personal projects or small groups, or for a
monthly or yearly fee for larger professional teams.
More commercial solutions also exist, but at present
we focus on tools with basic functionality that can be
used at no charge in an academic institution. An ex-
ample of a commercial tool is Trunity (Trunity Hold-
ings Inc., 2013).
4.2 Mobile Access
The ability to access the collaborative tools from a
mobile device, i. e. a smartphone or tablet, is a pos-
itive factor for out-of-classroom courses given their
externality.
Usually web-based applications can be accessed
with most available web browsers, including those
which are incorporated into mobile devices, i. e.
smartphones and tablets. However the peculiarities
of these devices (smaller display, touch-based input
system) can complicate the user experience if the ap-
plication is not specifically designed for them. Most
applications intended to be used in mobile devices are
therefore designed as mobile applications or “mobile
apps” (or simply “apps”).
This is the case for many of the collaborative tools
described in the previous subsection. In particular,
Google Drive as well as Asana and Zoho provide a
mobile app version that can be downloaded to the
user’s device before accessing the corresponding tool.
This of course requires the user to be provided
with such a mobile device, either a smartphone or a
tablet. However today it is more and more common
for students to have their own personal mobile de-
vice that they can use for training purposes at school.
Actually, some academic institutions are introducing
a BYOD policy (Bring Your Own Device) in their
learning systems, a process that is not free from con-
troversy, but it is out of the scope of this paper to de-
bate this issue.
5 INTEGRATION WITH
LEARNING MANAGEMENT
SYSTEMS
External tools have been successfully integrated into
learning management systems (LMS) using different
methods, e. g. through the IMS Basic Learning Tools
Interoperability (BLTI) standard (IMS Global Learn-
ing Consortium, 2010). If a LMS and an external tool
both implement the BLTI interface, the tool can be in-
tegrated so that it is seen by users as though it was a
UseofMobileCollaborativeToolsfortheAssessmentofOut-of-ClassroomCoursesinHigherEducation-Cloud
TechnologiesAppliedtotheMonitoringofthePracticum
241