<!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>PICTURE - A new Approach for Domain-Specific Process Modelling</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Jörg Becker</string-name>
          <email>becker@ercis.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Daniel Pfeiffer</string-name>
          <email>pfeiffer@ercis.de</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Michael Räckers</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>European Research Center for Information Systems</institution>
          ,
          <addr-line>Leonardo-Campus 3, 48149 Münster</addr-line>
          ,
          <country country="DE">Germany</country>
        </aff>
      </contrib-group>
      <fpage>45</fpage>
      <lpage>48</lpage>
      <abstract>
        <p>In this paper a new process modelling method especially for public administrations is presented. With established generic process modelling methods reorganisation projects in this domain could only identify limited reorganization potential and just led to small local improvements [1]. Therefore, we have created the domain specific modelling approach PICTURE. The PICTURE-method applies the domain vocabulary to efficiently capture the process landscape of a public organisation.</p>
      </abstract>
      <kwd-group>
        <kwd>Domain Specific Modelling</kwd>
        <kwd>E-Government</kwd>
        <kwd>Process Building Blocks</kwd>
        <kwd>Public Administration</kwd>
        <kwd>Process Landscape</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>
        So far process modelling in public administrations has mainly been performed with
generic (general-purpose) languages [
        <xref ref-type="bibr" rid="ref1 ref2">1, 2</xref>
        ]. These modelling languages, such as
Activity Diagrams (AD) [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], Business Process Modelling Notation (BPMN) [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], or
Event Driven Process Chains (EPC) [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ], are flexible instruments to describe diverse
processes in many different domains. However, they do not consider in particular
public administration [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ] and reorganisation specific questions [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ] like: (1) what
processes, activities, or products depend on legal regulations or (2) how can a very
large number of processes be acquired efficiently?
      </p>
      <p>In this paper we present the process modelling method PICTURE. The
PICTUREmethod consists of a modelling language and a procedure model which guides the
application of the language. Both parts are implemented in a web-based tool.
PICTURE allows for an efficient modelling of the entire process landscape of an
organisation. As it is based on a simple, domain specific language, not only isolated
processes can be represented but a complete overview on the practices of an
organisation is accomplished. This overall view allows for reorganisation decisions
that are based on the consideration of structural analogies, potential synergy effects,
and economies of scale. PICTURE takes the specific legal and political constraints
within public administrations into account and indicates technical and organisational
measures to improve the efficiency of the process landscape.</p>
    </sec>
    <sec id="sec-2">
      <title>2 The PICTURE-Method</title>
      <p>The first step during an application of the PICTURE-method is to define the
objectives of the project. Based on these goals the PICTURE-method can be
customised for the specific properties of the situation. The second step of the
PICTURE-approach is to model the entire process landscape. PICTURE focuses on a
strong involvement of the officials of an administration in the modelling project. With
the PICTURE-approach the modelling is performed in a distributed manner and the
acquisition of process models is done in a coarse granular form to reduce time and
effort for modelling. The third step is to analyse and use the process models.</p>
      <p>
        Basic construct of the PICTURE modelling language is the so called process
building block. A process building block represents a certain set of activities within
an administrational process [
        <xref ref-type="bibr" rid="ref8">8</xref>
        ]. The PICTURE-method contains altogether 29
different process building blocks. Some examples of process building blocks are
“Incoming Document”, “Create Document” or “Formal Assessment”.
      </p>
      <p>
        Process building blocks have been specifically developed for public
administrations and apply the vocabulary of this domain. As they are domain specific
the meaning of a process building block is characterised by a corresponding domain
statement [
        <xref ref-type="bibr" rid="ref9">9</xref>
        ]. Contrary to constructs of traditional process modelling approaches like
activities in an AD or functions in an EPC, process building blocks in PICTURE
reside at a particular level of abstraction. For example a function in an EPC can be
instantiated as: “Waiting for document”, “Receiving application form via letter”, or
“Signing the labour contract”. These functions stand for differently abstract
phenomenon in the real world. However, an instance of a process building block, for
example “Incoming Document” has always a specific meaning, in this case that a
document arrives. The meaning is inherently pre-defined for this building block and is
not specified by the modeller.
      </p>
      <p>
        In PICTURE the process building blocks are the only way to describe the
administrational processes. This simple syntax makes the modelling easy for the
method’s users. Furthermore, processes are represented as a sequential flow of
building blocks. Also this syntactical restriction guides the method’s user and
simultaneously promotes the construction of structurally comparable models. Since
only process building blocks can be used, the type of each model element is not just
syntactically but also semantically fixed. Problems like naming conflicts [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ] in a
model comparison are avoided, because the name of a process building block is
specified by the language designer rather then the modeller.
      </p>
      <p>Additional facts about the processes can be collected with the help of attributes
assigned to the process building blocks. For example possible attributes for the
process building block “Enter Data into IT” are “Source”, “Source Medium“, or
“Processing Time”. Altogether, PICTURE contains nearly 50 different attributes.
Attributes provide the core information for a subsequent process analysis, in which,
according to predetermined goals, corresponding weaknesses and potentials are
detected.</p>
      <p>In PICTURE a process can consist of several sub-processes (cf.</p>
      <p>Fig. 1 a)). A sub-process is a process section being carried out by a responsible
official or a position within a single organisational unit. Sub-processes can be linked
together to visualise a whole process. The majority of the modelling activities take
place on the sub-process level. Within the scope of the sub-process the responsible
official can collect all relevant information and represent them in form of process
building blocks and attributes. However, some processes contain only one
subprocess (cf.</p>
      <p>Fig. 1 b)). An example is the process “Notification on fees for a motor vehicle”. The
modelling with the PICTURE-language is strictly sequential. PICTURE offers no
language constructs to represent forks in the course of process building blocks. It is
also not possible to model iterations. To describe technically important ramifications
in the process flow, PICTURE offers two different ways: On the one hand attributes
can be used to specify different cases with percentage values. For example an
incoming document can arrive in 50% of the cases through the communication
medium mail, in 30% per email, and in 20% per fax. On the other hand it is possible
to specify process variants (cf. Fig. 1 c)). A process variant defines an alternative
sequence within a sub-process. The frequency of a process variant can be weighted by
percentage values.</p>
    </sec>
    <sec id="sec-3">
      <title>3 Evaluation of the PICTURE-method</title>
      <p>
        In two case studies in the City of Münster and the University of Münster, the
PICTURE-method has proved to be viable and efficient. We collected altogether 340
process models in the two case studies. In comparison in the Regio@KomM project
processes of a municipal administration have been acquired with the modelling
language EPC [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. In this project the collection of 22 administrational processes took
six person hours on average. The paper based modelling of a single process with the
PICTURE-method required only half of that time. With the tool based modelling the
time could be further reduced to a fourth. The participants at University of Münster
and City of Münster who had pervious experiences with EPC modelling evaluated the
PICTURE-approach as faster to learn and its models as easier to understand in
comparison to EPC.
      </p>
      <p>Currently, the PICTURE-method is applied in the cities of Bielefeld and Hamm. It
is an objective of the project to compare the different processes of the cities and
consolidate them if significant variations are recognised.</p>
      <p>Acknowledgements. The work published in this paper is partly funded by the
European Commission through the STREP PICTURE. It does not represent the view
of European Commission or the PICTURE consortium, and the authors are solely
responsible for the paper's content.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Algermissen</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Delfmann</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Niehaves</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          :
          <article-title>Experiences in Process-oriented Reorganisation through Reference Modelling in Public Administrations - The Case Study Regio@KomM</article-title>
          .
          <source>In: Proc. 13th European Conference on Information Systems (ECIS</source>
          <year>2005</year>
          )
          <article-title>(</article-title>
          <year>2005</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Janssen</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Modeling for Accountability: The Case of the Virtual Business Counter</article-title>
          .
          <source>In: Proc. 11th Americas Conference on Information Systems (AMCIS</source>
          <year>2005</year>
          )
          <article-title>(</article-title>
          <year>2005</year>
          )
          <fpage>2021</fpage>
          -
          <lpage>2029</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>Object</given-names>
            <surname>Management</surname>
          </string-name>
          <article-title>Group</article-title>
          .
          <source>UML 2</source>
          .0
          <string-name>
            <given-names>Superstructure</given-names>
            <surname>Specification</surname>
          </string-name>
          .[Online]. Available: http://www.omg.org/cgi-bin/doc?formal/05-07-04
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>Object</given-names>
            <surname>Management</surname>
          </string-name>
          <article-title>Group</article-title>
          .
          <source>BPMN Final Adopted Specification</source>
          <volume>1</volume>
          .
          <fpage>0</fpage>
          .[Online]. Available: http://www.bpmn.org/Documents/OMG%20Final%
          <fpage>20Adopted</fpage>
          %
          <fpage>20BPMN</fpage>
          %
          <fpage>201</fpage>
          -
          <lpage>0</lpage>
          %20Spec%
          <fpage>2006</fpage>
          -02-01.pdf
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Scheer</surname>
            ,
            <given-names>A</given-names>
          </string-name>
          .-W.: ARIS - Business
          <source>Process Modeling. 3 edn</source>
          . Springer Publishing, Heidelberg et al. (
          <year>2000</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <surname>Bretschneider</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          :
          <article-title>Management Information Systems in Public and Private Organizations: An Empirical Test</article-title>
          .
          <source>Public Administration Review</source>
          <volume>50</volume>
          (
          <year>1990</year>
          )
          <fpage>536</fpage>
          -
          <lpage>545</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <surname>Maier</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Remus</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          :
          <article-title>Towards a Framework for Knowledge Management Strategies: Process Orientation as Strategic Starting Point</article-title>
          .
          <source>In: Proc. 34th Hawaii International Conference on System Sciences (HICSS2001)</source>
          (
          <year>2001</year>
          )
          <fpage>1</fpage>
          -
          <lpage>10</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <surname>Rupprecht</surname>
            ,
            <given-names>C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Funffinger</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Knublauch</surname>
            ,
            <given-names>H.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Rose</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Capture and Dissemination of Experience about the Construction of Engineering Processes</article-title>
          .
          <source>In: Proc. 12th International Conference on Advanced Information Systems Engineering (CAiSE2000)</source>
          (
          <year>2000</year>
          )
          <fpage>294</fpage>
          -
          <lpage>308</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Guizzardi</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pires</surname>
            ,
            <given-names>L. F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sinderen</surname>
            ,
            <given-names>M. J. v.</given-names>
          </string-name>
          :
          <article-title>On the role of Domain Ontologies in the design of Domain-Specific Visual Modeling Languages</article-title>
          .
          <source>In: Proc. 2nd Workshop on Domain-Specific Visual Languages</source>
          (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Pfeiffer</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gehlert</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          :
          <article-title>A framework for comparing conceptual models</article-title>
          .
          <source>In: Proc. Workshop on Enterprise Modelling and Information Systems Architectures (EMISA</source>
          <year>2005</year>
          )
          <article-title>(</article-title>
          <year>2005</year>
          )
          <fpage>108</fpage>
          -
          <lpage>122</lpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>