<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Using Work Agreements as Operation-time System Requirements for Emergent Work Community Support Systems</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Stijn Hoppenbrouwers</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Uwe van Heesch</string-name>
          <email>Uwe.vanHeesch@han.nl</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Christian K¨oppe</string-name>
          <email>Christian.Koppe@han.nl</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>HAN University of Applied Sciences</institution>
          ,
          <addr-line>Arnhem</addr-line>
          ,
          <country country="NL">the Netherlands</country>
        </aff>
      </contrib-group>
      <fpage>19</fpage>
      <lpage>24</lpage>
      <abstract>
        <p>We propose an approach for capturing evolving requirements for work support systems that are organically created by co-workers in self-organized, networked organizations. It is in the nature of such organisations that comprehensive design-time capturing of the volatile taskrelated functional requirements is not possible. Therefore, we advocate a combination of two types of requirements: i. stable requirement fragments elicited at design time, based on elementary collaboration and communication patterns likely to occur in an operational context, and ii. highly dynamic requirements in the form of explicit, easy-to-understand yet well-structured work agreements between organisational actors within organisations at operation-time. These agreements capture many aspects and concepts well known from requirements engineering, as well as business process analysis and design, but design-time modeling/specification of work-specific structures is now moved to operation time. Description of such structures by co-workers is supported by mechanisms part of the stable communication patterns under i.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>even know each other. And yet, in principle they work together towards one
common goal: the well-being of the patient. SIT composition may vary from
day to day, and team members may not even be aware of this. Tasks, roles and
responsibilities are often subject to continuous change.</p>
      <p>Flawed cooperation in, and resulting sub-optimal functioning of, SITs in
healthcare is usually blamed on lack of exchange, or limited availability, of
factual medical and administrative information. However, another important factor
hampering cooperation is that information and communication of a more
operational, coordinative nature is missing: who is doing what with and for the patient,
when, and why. Part of these communicational shortcomings do not even
concern medical details. Cooperation in SITs is highly dependent on the current
situation and the tasks individual SIT members have to perform.</p>
      <p>Although SITs, perhaps even more than traditional forms of organisation
based on stable workprocesses, could benefit greatly from digital work support
systems (beyond basic message and file exchange), their dynamic
characteristics make it very hard to plan and develop such systems. In SITs, ’design time’
comprehensive articulation of work is not possible (no resources, no dedicated
analyst/developer, very frequent changes in the organisational structure).
Traditional pre-design requirements engineering activities are out of the question
here. So if design-time RE is out, what is the alternative?</p>
      <p>If design time elicitation of requirements is ruled out, only ’operation time’
articulation of work is possible in SITs. Interestingly, such ’communication about
work’ is part and parcel of all cooperative work, and comes natural to humans
as they cooperate. It is entwined with communication performed as part of the
execution of tasks. Central to such articulation of work are work agreements
made between co-workers. We propose that dynamic (i.e. operation time)
requirements directly pertaining to the emergent organisational structures in SIT
operations can in principle be derived from such work agreements.
Operationtime requirements can be used to enable self-adaption of work support systems
within the boundaries of pre-defined, stable functional building blocks. These
building blocks derive from existing, general organisational collaboration and
communication patterns, a subset of which directly support the articulation of
the volatile work agreements.</p>
      <p>The rest of this article is organised as follows: The problem is described in
more detail in Section 2. In Section 3 we outline our position, followed by the
description of the research goal and approach in Section 4.
2</p>
    </sec>
    <sec id="sec-2">
      <title>Problem Statement</title>
      <p>Although most work support systems o↵er support for communication and
collaboration, they often fall short of e↵ectively supporting SITs due to either their
restrictive and prescriptive nature, or their lack of required situation-specific
functionality. This becomes evident in the above example, but can also be
observed in other kinds of organizations.</p>
      <p>Work support systems are often designed using a top-down approach. They
are designed up-front and reflect the intended and anticipated collaboration
and communication structures in the organization. But SITs often emerge at
’operation-time’ and they have requirements that are not addressed by the
supporting systems. SITs therefore often use a variety of standard facilities like
oral communication, mail, unstructured file exchange, and meetings via informal
communication channels like social media. All of these are mainly unstructured
and are often not included in the systems supporting the work processes of the
organization, and the related tasks as performed by co-workers. This is the core
of the problem: due to their continuously changing nature and partial occurrence,
the situation-specific communication and collaboration needs of SITs cannot be
adequately addressed by work support systems designed and developed based
on traditional design-time requirements engineering.
3</p>
      <p>
        Position Statement: using work agreements for
capturing operation-time requirements
Following Taylor et al., who identify (the communication of) agreements between
team members as the basis of human organization [
        <xref ref-type="bibr" rid="ref1 ref2">1,2</xref>
        ], the work agreements
made between the patient and other team members (and other team members
among each other) constitute the organisation of a SIT. Such work agreements,
or in our case, care agreements, are the basic building blocks of cooperation and
organization. This has been acknowledged and embraced by information system
scientists and practitioners who came up with ways of modeling various aspects
of work agreements in context of stable and large-scale organisational patterns
(transactional business process models) [
        <xref ref-type="bibr" rid="ref3 ref4">3,4</xref>
        ]. They articulate them as business
processes, work-flows, protocols, business rules, and the information structures
used in and between them. A primary use of such business modelling is as
requirements in view of information system design, or work support system design.
However, as explained above, pre-described organisational work statements
cannot be expected to be available for SITs.
      </p>
      <p>Figure 1 shows a conceptual model of requirement fragments and work
agreements in support systems for SITs. A SIT organisation, although being dynamic
and emergent in nature, still operates in a stable context from a generalized
organisation perspective: patterns of organisation and communication do occur,
alongside ad-hoc or emergent interactions and agreements. An example of such
a context is the local healthcare system, as mentioned above. From this context,
but also from universal cooperative communication patterns, we can elicit
collaboration and communication requirement fragments that can be anticipated to
occur. We deliberately use the term ’requirement fragment’ as contrasted against
the basic practice in requirements engineering to comprehensively capture
functionality known to be required at operation-time. A requirement fragment is
rather a partial functionality likely to be required in combination with other
requirement fragments at operation-time. For instance, and central to our
approach, communication about work generically requires agreements to be made
elicited from</p>
      <p>Requirement Fragment
1 cover
1</p>
      <p>Collaboration/
Communication Pattern</p>
      <p>support
implementation of
1..*
Operational Context</p>
      <p>Work Agreement</p>
      <p>Work Support System
re-configures based on
operates in
0..*
1
SIT
1..*
combines
1..*</p>
      <p>
        create
(i.e. stating, structuring, negotiating, discussing, agreeing, committing), to be
monitored, and to be managed. Concepts required to cover such activities are
available (see for instance [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]), but we intend to apply them in a di↵erent way:
drawing them from operational but explicit work agreements.
      </p>
      <p>
        Organizational communication and collaboration has been extensively
studied in the past. As a result, several patterns of organisational communication,
collaboration, and workflow were published, see for instance [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ], [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ], [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ],
[
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. Such patterns can be leveraged to elicit and describe requirement
fragments of organisational communication. The advantage of using existing
patterns is twofold: On the one hand, they can serve as candidates when eliciting
requirement fragments in a specific operational context; on the other hand, the
implementation of such patterns in work support systems can be based upon
proven implementation of the patterns in existing systems.
      </p>
      <p>While the elicitation of requirement fragments based on patterns in an
operation context happens at design-time, the concrete operation-time
communication and collaboration requirements of SITs are not comprehensively known
at design-time. Therefore, we propose to continuously capture operation-time
requirements of SITs in the form of work agreements. Work agreements as
artefacts represent agreements made between co-workers in a SIT at operation time.
They combine and instantiate requirement fragments. The work support system
analyzes the work agreements at run-time to dynamically re-configure itself to
support the collaboration and communication requirements of the SIT. This
embraces the volatile nature of SITs, while enabling operation specific support to
the co-workers.</p>
      <p>To recapitulate, the requirements engineering process is split into a stable
design-time process used to elicit requirement fragments as anticipated
functional building blocks, and a continuous requirements capturing process based
on work agreements at operation time. The former process is applied by
requirements engineers, while the latter process is executed by the actors of the
system.
4</p>
    </sec>
    <sec id="sec-3">
      <title>Outline of Research Project</title>
      <p>The goal of this research project is to improve work support systems for SITs
by means of dynamic work agreements captured at operation time. We plan to
identify and describe collaboration patterns that support self-organizing
interdisciplinary teams with their work agreements and to provide these patterns
as functional building blocks for system design in order to enable continuous
requirements engineering.</p>
      <p>In first instance we focus on SITs in healthcare contexts, in particular
outside tightly organized institutions. There is a strong demand for improving the
collaboration between co-workers in order to improve healthcare quality and
efficiency. We utilise our existing cooperations with local healthcare organisations
in the Netherlands. In the following, we sketch the phases of the research project:
Step 1 : Identify and categorize types of work agreement used in local
healthcare organizations. For this purpose, we will conduct interviews with
stakeholders from our partner healthcare institutions and observe individual
workers in their daily work.</p>
      <p>Step 2 : In addition, collect examples of work agreements and
communication about them using an explerimental application (currently being
alphatested) that supports the situation-independent articulation, negotiation,
setting and monitoring of work agreements and related cooperative
communication. This will not be done in a healthcare environment (yet) but
in our own team and in various other teams in educational and research
organizations interested in our research.</p>
      <p>Step 3 : Perform a systematic mapping study for collaboration and
communication patterns.</p>
      <p>Step 4 : Map the collaboration patterns identified in Step 3 to the work
agreements types and observed communication found in Steps 1 and 2. We expect
that several work agreements and communcations can be de-composed into
one or more fragments that instantiate one of the collaboration patterns.
Step 5 : Develop a reference architecture for work support systems that
provides means for dynamic re-configurations of workflow support modules
based on work agreements. We will leverage proven solutions promoted for
the implementation of the corresponding collaboration patterns.</p>
      <p>The results of our research project can be used for designing innovative
SIToriented work support systems for use in healthcare organizations, and beyond.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>James R Taylor</surname>
          </string-name>
          , Carole Groleau, Lorna Heaton, and
          <string-name>
            <surname>Elizabeth Van</surname>
          </string-name>
          Every-Taylor.
          <article-title>The Computerization of Work: A Communication Perspective</article-title>
          . Sage Publications, Inc, Thousand Oaks, CA,
          <year>2000</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>James R Taylor and Elizabeth J Van Every</surname>
          </string-name>
          .
          <article-title>The Emergent Organization: Communication as its Site and Surface</article-title>
          . Lawrence Erlbaum Associates, Mahwah, NJ,
          <year>1999</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <given-names>Hans</given-names>
            <surname>Weigand</surname>
          </string-name>
          .
          <article-title>Two decades of the language-action perspective: Introduction</article-title>
          .
          <source>Communications of the ACM</source>
          ,
          <volume>49</volume>
          (
          <issue>5</issue>
          ):
          <fpage>44</fpage>
          , May
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Jan</surname>
            <given-names>L. G.</given-names>
          </string-name>
          <string-name>
            <surname>Dietz. Enterprise</surname>
          </string-name>
          Ontology -
          <source>Theory and Methodology</source>
          . Springer Berlin Heidelberg, Berlin, Heidelberg,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <given-names>Nick</given-names>
            <surname>Russell</surname>
          </string-name>
          ,
          <string-name>
            <surname>Wil M P van der Aalst</surname>
          </string-name>
          ,
          <article-title>Natalya Mulyar, and</article-title>
          <string-name>
            <given-names>Others. Workflow</given-names>
            <surname>Control-Flow Patterns</surname>
          </string-name>
          :
          <article-title>A Revised View</article-title>
          .
          <source>BPM Center Report BPM-06-22</source>
          ,
          <year>2006</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>W M P Van Der Aalst</surname>
          </string-name>
          ,
          <string-name>
            <surname>A H M Ter Hofstede</surname>
            ,
            <given-names>B</given-names>
          </string-name>
          <string-name>
            <surname>Kiepuszewski</surname>
            , and
            <given-names>A P</given-names>
          </string-name>
          <string-name>
            <surname>Barros. Workflow Patterns</surname>
          </string-name>
          .
          <source>Distributed and Parallel Databases</source>
          ,
          <volume>14</volume>
          (
          <issue>1</issue>
          ):
          <fpage>5</fpage>
          -
          <lpage>51</lpage>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <given-names>Dongsoo</given-names>
            <surname>Kim</surname>
          </string-name>
          , Minsoo Kim, and
          <string-name>
            <given-names>Hoontae</given-names>
            <surname>Kim</surname>
          </string-name>
          .
          <article-title>Dynamic Business Process Management Based on Process Change Patterns</article-title>
          .
          <source>In Proceedings of the 2007 International Conference on Convergence Information Technology</source>
          , pages
          <fpage>1154</fpage>
          -
          <lpage>1161</lpage>
          . IEEE Computer Society,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          8.
          <string-name>
            <given-names>Till</given-names>
            <surname>Schu</surname>
          </string-name>
          <article-title>¨mmer. GAMA: A Pattern Language for Computer Supported Dynamic Collaboration</article-title>
          .
          <source>In Proceedings of the 8th European Conference on Pattern Languages of Programs (EuroPLoP</source>
          <year>2003</year>
          ), pages
          <fpage>53</fpage>
          -
          <lpage>114</lpage>
          ,
          <year>2003</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          9.
          <string-name>
            <given-names>Yiannis</given-names>
            <surname>Verginadis</surname>
          </string-name>
          , Dimitris Apostolou, Nikos Papageorgiou, and
          <string-name>
            <given-names>Gregoris</given-names>
            <surname>Mentzas</surname>
          </string-name>
          .
          <article-title>An Architecture for Collaboration Patterns in Agile Event-Driven Environments</article-title>
          .
          <source>In Proceedings of the 2009 18th IEEE International Workshops on Enabling Technologies: Infrastructures for Collaborative Enterprises</source>
          , pages
          <fpage>227</fpage>
          -
          <lpage>230</lpage>
          . IEEE Computer Society,
          <year>2009</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          10.
          <string-name>
            <surname>Brian T Pentland</surname>
          </string-name>
          and
          <article-title>Martha S Feldman. Narrative Networks: Patterns of Technology and Organization</article-title>
          . Organization Science,
          <volume>18</volume>
          (
          <issue>5</issue>
          ):
          <fpage>781</fpage>
          -
          <lpage>795</lpage>
          ,
          <year>2007</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>