<!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>BPMN Based Problem Domain Knowledge Specification Method</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Austina Varkalaite</string-name>
          <email>austina.varkalaite@knf.stud.vu.lt</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Vilnius University, Kaunas Faculty</institution>
          ,
          <addr-line>Muitines g. 8, Kaunas</addr-line>
          ,
          <country country="LT">Lithuania</country>
        </aff>
      </contrib-group>
      <fpage>112</fpage>
      <lpage>118</lpage>
      <abstract>
        <p>- Business Process Model and Notation (BPMN) is one of OMG (Object Management Group®) product, standardized ISO standard. Nowadays BPMN become de-facto notation and is used to create different types and architecture levels of activity diagrams. The main point of this article is to integrate the BPMN notation into the knowledge-based IS engineering process, thereby reducing the empiricity and enabling semi-automated generation of a more precise operational model. For this reason there is created Algorithm for the representation of the activity meta-model element BPMN and detailed one element "Activity" type selection algorithm. The prototype, by using Microsoft Access 2016 program, MagicDraw 18.1 tool and interactive expert system ES-Builder Web, tests correctly operation of both algorithms.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>Keywords— BPMN; Enterprise Model; Enterprise Meta-model;
IS engineering process.</p>
    </sec>
    <sec id="sec-2">
      <title>I. INTRODUCTION</title>
      <p>Constantly changing and expanding information systems of
organizations, is faced with the problem of displaying
information flows. To reach goals of business, it might be used
different types of interconnection and graphical imaging standard
diagrams and notations of business processes, functions, objects
and other elements. Each method has its own abilities to
interpret and submit information about organization domain
knowledge system.</p>
      <p>From the point of view of organizations and companies, it is
important to systematize stored information as easily and
accurately as possible. For each participant of the activity to be
equally well acquainted with the future benefits of the
information system.</p>
      <p>Different business activities require a variety of business
models describing business processes. The more research and
presentation of business process mapping techniques, the easier
it will be for businesses to select the most appropriate option for
them.</p>
      <p>The work deals with the notation and modeling languages,
which help to create business models in the field of knowledge.
The main point of this article is to integrate the BPMN notation
into the knowledge-based IS engineering process, thereby
reducing the empiricity and enabling semi-automated generation of a
more precise operational model. For this reason, the following
tasks are considered, such as, to study the modeling languages</p>
    </sec>
    <sec id="sec-3">
      <title>Copyright held by the author(s). 112</title>
      <p>Business Process Definition Meta-model (BPDM) [4]
provides the ability to represent and model business process without
reference to notation or methodology combined these different
methods into a coherent functional dependence. It is created by
using meta-model like perfect connection between terms and
concepts based basic processes’ vocabulary [6]. BPDM uses
OMG standard – MOF Meta-Object Facility [7,8,9] capturing
business process by common method and let XML syntax save
and transform business process models using tools and
infrastructure.</p>
      <p>
        Date-Time Vocabulary (DTV) [4] modeling the continuous,
discrete time, event relationships and time-space situations,
language aspects, time tables and graphs [
        <xref ref-type="bibr" rid="ref6">10</xref>
        ].
      </p>
      <p>
        Business Process Maturity Model (BPMM) [4] describes an
evolutionary path of development that focuses on the
organization's movement from immature, inconsistent processes to
mature, disciplined processes. BPMM based Process Maturity
Framework, which is basis widely used Capability Maturity
Model for Integration (CMMI) to help organizations organize
repeated software engineering processes [
        <xref ref-type="bibr" rid="ref7">11</xref>
        ].
      </p>
      <p>The most often there are used well-known modeling
languages – UML and SysML or notation – BPMN. All these are
OMG’s products. For more detailed information in the next
subsections.</p>
      <p>A. UML</p>
      <p>
        Unified Modeling Language® (UML) is ISO standard
created by OMG. UML has thirteen types of diagrams grouped in
three categories [
        <xref ref-type="bibr" rid="ref8">12</xref>
        ]:
 Structure Diagrams includes Class Diagram, Object
Diagram, Component Diagram, Composite Structure
Diagram, Package Diagram, and Deployment Diagram.
      </p>
      <p>Those diagrams represent static application structure.

</p>
      <p>Behavior Diagrams includes Use Case Diagram, Activity
Diagram and State Machine Diagram – show basic types
of behavior.</p>
      <p>To show different interactions aspects is needed to use
Interaction Diagrams, like Sequence Diagram,
Communication Diagram, Timing Diagram and Interaction
Overview Diagram.</p>
      <sec id="sec-3-1">
        <title>B. SysML</title>
        <p>
          Another OMG’s modeling language is Systems Modeling
Language™ (OMG SysML™). It is the general purpose
graphical modeling language is intended to specify, analyze, design
and test complex systems that may include hardware, software,
information, personnel, procedures and services [
          <xref ref-type="bibr" rid="ref9">13</xref>
          ]. SysML is
an extension of UML, so there are used basic Unified Modeling
Language diagrams: Use Case Diagram, Activity Diagram,
Sequence Diagram, State Machine Diagram. SysML includes
graphical constructions to describe text-based requirements and
link them to other elements of the model.
        </p>
      </sec>
      <sec id="sec-3-2">
        <title>C. BPMN</title>
        <p>
          Business Process Model and Notation (BPMN) is de-facto
graphical standard notation in modeling of processes. BPMN is
also OMG product and describes the progress of the business
processes to the final process flow. BPMN specially designed to
coordinate process sequences and reports that come from
different process participants. At the same time enables BPMN
diagrams to be transformed into components of the software
development process [
          <xref ref-type="bibr" rid="ref10 ref11 ref7">11,14,15</xref>
          ].
        </p>
        <p>
          In accordance with reference [
          <xref ref-type="bibr" rid="ref12">16</xref>
          ] complete BPMN
specifications includes thirty eight different language constructions
with attributes, grouped into four main categories of elements:
Flow Objects, Business Process Diagrams (BPDs), Connecting
Objects and Swimlanes. In the specification of BPMN published
in OMG website, reference [
          <xref ref-type="bibr" rid="ref13">17</xref>
          ], are five categories of elements:
1) Flow Objects. The main graphic elements for describing
the behavior of business processes:
a) Events,
b) Activities,
c) . Gateways.
a) Data Objects,
b) Data Inputs,
2) Data. All types of data:
        </p>
        <p>3) Connecting Objects. Used to interconnect flow objects
with different types of arrows:
c) Data Outputs
d) Data Stores.
a) Sequence Flows,
b) Message Flows,
c) Associations,
d) Data Associations.
a) Pools,
b) Lanes.</p>
      </sec>
      <sec id="sec-3-3">
        <title>a) Group,</title>
      </sec>
      <sec id="sec-3-4">
        <title>b) Text Annotation.</title>
        <p>4) Swimlanes are used to group the initial simulation
elements:</p>
      </sec>
      <sec id="sec-3-5">
        <title>5) Artifacts. Artifacts are used to provide additional process</title>
        <p>information:</p>
        <p>These elements are used to create different level BPMN
diagrams.</p>
        <p>Similarities and differences among UML, SysML and
BPMN in the next subsection.</p>
      </sec>
      <sec id="sec-3-6">
        <title>D. Comparison among UML, SysML and BPMN</title>
        <p>
          Kenneth D. Evensen and Dr. Kathryn Anne Weiss [
          <xref ref-type="bibr" rid="ref14">18</xref>
          ]
compare UML and SysML: both are chart-oriented notation
languages. UML and SysML diagrams specify types of graphical
components in model. UML can be used to define both
highlevel architectures and detailed representations. For a more
detailed description of the architecture, it is provided by SysML. It
addresses problems such as broken down various subsystems,
traceability requirements, and the location of arithmetic formula
components.
        </p>
        <p>
          UML and BPMN notations can adequately model most
structures. There are not adequate graphic layout layers
Interleaved Parallel Routing in UML activity diagram. Similar
graphic representation of forms for the same models. BPMN has
less basic objects. To avoid complexity in development process,
there need to invent variants to those objects. Business sequence
models are oriented to control flows between process activities.
Data flow is used between activities in BPMN. Activity diagram
and business process diagram are very close and are represented
by the same meta-model [
          <xref ref-type="bibr" rid="ref16">20</xref>
          ].
        </p>
        <p>
          According to reference [
          <xref ref-type="bibr" rid="ref15">19</xref>
          ], Table 1, there can be compared
UML activities and BPMN business processes. The main
elements of UML or BPMN correspond to the elements of the
activity meta-model, but depending on the level of detail of the
activity area or model, the activities in the meta-model are not
sufficient.
        </p>
        <p>There can be provided mappings and transformation
algorithm from BPMN Business process model to UML Activity
model at the later stage.
Condition 1. The starting point is defined by an Initial Node. No
method of specifying why the Activity was started is available.</p>
        <p>Condition 2. The basic behavior unit in an Activity is the
Actionelement. UML provides many different forms of Actions,
although the simulation makes use of a small subset of these.</p>
        <p>Condition 3. A Control Flow is used to connect the elements on an
Activity diagram. A distinguishing feature is that only a single control
flow may be followed from any node except for an explicit Fork Node.
To restrict flow on a control flow, add a guard.</p>
        <p>Condition 4. A Decision node is used to explicitly model a decision
being made. A Merge node, which uses the same syntax is used when
the potential flows are combined back into one.</p>
        <p>Condition 5. A Fork node is used to concurrently execute multiple
nodes, while a Join node, using the same syntax is used to wait for all
incoming flows to become available and leave with a single flow.
Condition 6. There is no allowance for concurrently executing only
some outputs from a node for UML Activities. If you needed this you
would need to add later control flows with the appropriate guards.
Condition 7. A Call Behavior Action is used when behavior needs to
be further decomposed by referring to an external activity.</p>
        <p>Condition 8. Activity elements are used when behavior needs to be
further decomposed without referring to an external activity.</p>
        <p>BPMN Business Process
Condition 1. The starting point is defined by a Start Event. This implies
a specific cause for the Activity to start, although it may be unspecified.
Condition 2. The basic behavior unit in an Activity is the Activity
element. A number of different Task Types are available. These typically
describe different methods of execution (for example Manual) as
opposed to what happens.</p>
        <p>Condition 3. A Sequence Flow is used to connect the elements on a
Business Process diagram. These differ from UML Activity diagrams
in that all valid sequence flows are taken by default. To restrict flow on
a sequence flow set the Condition Type to expression and the Condition
Expression.</p>
        <p>Condition 4. A Gateway node set to Exclusive is used when a single
path must be selected. It is also used to combine the potential flows
again. A direction may be specified as Converging or Diverging to
explicitly select between the two modes.</p>
        <p>Condition 5. A Gateway node set to Parallel is used to explicitly model
concurrent execution of multiple nodes. It is also used to wait for all
incoming flows to become available and leave with a single flow. A
direction may be specified as Converging or Diverging to explicitly
select between the two modes.</p>
        <p>Condition 6. A Gateway node set to Inclusive is used to explicitly
model the situation where all outgoing flows with a true condition are
executed concurrently.</p>
        <p>Condition 7. Activity elements are set as CallActivity Sub-Process
when behavior needs to be further decomposed by referring to an
external activity.</p>
        <p>Condition 8. Activity elements are set as an Embedded
Sub-Processwhen behavior needs to be further decomposed without referring to an
external activity.</p>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>III. PROPOSED DECISSION METHODOLOGY</title>
      <p>
        After analyzing the main features of the activity meta-model
elements' representation and possibilities in different modeling
languages and notation, moving in detailed analysis of Business
Process Modeling and Notation elements [
        <xref ref-type="bibr" rid="ref14">18</xref>
        ].
      </p>
      <p>BPMN has additional objects that are more detailed than the
abstraction level. Some elements are used just like explaining
the main ones.</p>
      <p>There compose schema from activity meta-model class
Cmodel elements, black color, with all BPMN elements, red color,
shown in Fig. 2. The main focus is on how the elements used in
the BPMN notation complement the activity meta-model.
Although a large number of objects overlap in meta-models, such
as a pool or lane match to the actor, the process matches the
function in the activity meta-model, but elements such as
sequence flow types or event types can more accurately convey
the informative nature and use of the element itself.</p>
      <p>Assumed, that some elements of meta-model and BPMN
elements match, like “Events”, “Actor” with “Pool”, “Actor of
Process” or “Actor of Function” with “Lane”, “Function” with
“Process”, “Material Flow” with “Message Flow”, “Information
Flow” with “Sequence Flow” or “Data Object”, “Processing
Access Input” with “Data Inputs”, “Processing Access Outputs”
with “Data Outputs”, “Information Activity” with “Task”,
“Activity Rules” and “Gateways”. Other elements from BPMN can
partly change in meta-model or be complementary.</p>
      <sec id="sec-4-1">
        <title>Algorithm for the representation of the activity metamodel element BPMN</title>
        <p>Elements, from the activity meta-model, in the development
of the activity model BPMN notation, can be displayed with a
certain sequence or according to certain rules. In order to reduce
the empiricity of the element and its related elements, a
macrolevel algorithm is created, in Fig. 1.
Fig. 2. (a), (b), (c) and (d) parts combine BPMN elements addition to
activity meta-model. See the next column.</p>
        <p>This algorithm can be applied to any element of the activity
meta-model, which is required to represent the BPMN notation.
The basic principle is that the desired element is represented by
an element from the BPMN and it is checked that it may still
have other related elements needed to generate the activity
model. This allows to create business models no matter what
kind of element.</p>
        <p>For the second step in the main algorithm, there is created
element activity selection algorithm shown in Fig. 3. There are
many types of activity in BPMN notation, so this algorithm
helps to choose one of them. In each step of the iteration, the
(c)
(d)
check is carried out and, if the condition is satisfied, the desired
type of activity is displayed. Otherwise, further steps are taken
until the desired element is found. The test sequence is consistent
and the type of activity is selected, the operation of this
algorithm is stopped, the work is completed.</p>
        <p>Experiment is made for both algorithms. For more details in
the next subsections.</p>
        <p>Fig. 3. (a) part is the beginning of element "Activity" type selection algorithm
and (b) part is the end of element "Activity" type selection algorithm.</p>
      </sec>
      <sec id="sec-4-2">
        <title>A. Algorithm for the representation of the activity metamodel element BPMN realization</title>
        <p>To test Algorithm for the representation of the activity
meta-model element BPMN proper operation, there is created
prototype. User interface is executed using Microsoft Access
2016 program. BPMN element is displayed in MagicDraw
18.1 tool.</p>
        <p>There is given a real example “Close Auction” Fig 4. At
first, it is chosen element, Fig. 5. Whole cycle of the main
algorithm is executes – select the element, represent the element
in BPMN, select others related elements, control if there are
enough related elements and if the link is assigned among
elements. The last step of the algorithm is carried out in</p>
      </sec>
      <sec id="sec-4-3">
        <title>MagicDraw 18.1 tool, Fig. 6.</title>
      </sec>
      <sec id="sec-4-4">
        <title>B. Element "Activity" type selection algorithm realization</title>
        <p>Element “Activity” is complex element and has many types,
in different hierarchy level. Algorithm shown in Fig, 3
realization is made in internet expert system platform ES-Builder Web.
The value returned by the expert system (satisfies the condition
that one element is selected) is the selection of the "Activity"
type element, the activity meta-model element BPMN notation
algorithm is executed at the beginning, that is, when the element
of the activity model element is selected and assigned to it the
element corresponding to the BPMN. Expert system is in the
www.mcgoo.com platform (note, it is in Lithuanian language).</p>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>IV. CONCLUSION</title>
      <p>OMG-based modeling languages UML and SysML are
graph-oriented, notation languages. UML can be used to define
high-level architectures, detailed imaging, modeling of
applications and user interactions in an early life cycle. For more
detailed architecture, SysML is used.</p>
      <p>When comparing the BPMN Activity Diagram with the
UML Activity Diagram, it is concluded that these notions
provide the same solutions and very similar graphical
representations of forms to many models. The BPMN has fewer essential
objects and the potential complexity of creating business process
diagrams; no significant difference is the terminology.</p>
      <p>The elements of the activity meta-model can be displayed
both in elements of the UML modeling language and in the main
elements of the BPMN notation. However, depending on the
level of detail of the field or model in question, the underlying
elements may not be sufficient.</p>
      <p>After examining all the elements in the BPMN notation, it
can be concluded that some of the values of these elements
correspond to the elements used in the activity meta-model. In
addition, the BPMN elements have types, expanded values, which
can more accurately convey the specifics of the business model
being developed.</p>
      <p>In order to reduce the empiricity of the development of a
business model, a basic algorithm has been developed that
shows how the sequence can be represented by the activity</p>
      <p>Fig. 6. Element Bidder display for excaple “Close Auction”.
model element in the BPMN notation. A detailed selection of
possible variations of one element "Activities" has also been
developed. "Activity" type selection is made from all variants of
the BPMN notation.</p>
      <p>The experiment used to create the Microsoft Access 2016
user interface program, the MagicDraw 18.1 tool to implement
BPMN charts, and an interactive expert development platform
for setting the "Activity" type of the ES-Builder Web element.</p>
      <p>The experiment was conducted with the example of the
chosen subject area. It was verified that the invented tool - the
prototype, according to the activity meta-model element RPMN
notation algorithm, in a semi-automated way, can generate the
activity model BPMN notation.</p>
      <p>Interactive:</p>
      <p>January
12
d.</p>
      <p>Interactive:
Documents Associated With Business Process Definition MetaModel
(BPDM), Version 1.0. 2008 November 4 d. Interactive:
http://www.omg.org/spec/BPDM/1.0/.</p>
      <p>MDA architekturos esminis elementas. 2013. Interactive:
http://kursiniai.blogspot.lt/2013/09/mda-architekturos-esminiselementas.html.</p>
      <p>Veitaite, I., Lopata, A. (2015) Additional Knowledge Based MOF
Architecture Layer for UML Models Generation Process. Business
Information Systems Workshops, vol. 228, p. 56-63.</p>
      <p>Interactive:</p>
      <p>Interactive:</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          <string-name>
            <surname>Lopata</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Veitaite</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Zemaityte</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          (
          <year>2016</year>
          )
          <article-title>Enterprise Model based UML Interaction Overview Model Generation Process</article-title>
          .
          <source>International Conference on Business Information Systems</source>
          , p.
          <fpage>69</fpage>
          -
          <lpage>78</lpage>
          . ISBN 978-3-
          <fpage>319</fpage>
          -52463-4.
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <surname>Ambraziunas</surname>
            ,
            <given-names>Martas.</given-names>
          </string-name>
          (
          <year>2014</year>
          )
          <article-title>Veiklos Zinių Baze Isplestos Modeliais Grindziamos Architekturos Taikymo Informacijos Sistemų Inzinerijoje Metodas</article-title>
          .
          <article-title>Unpublished doctorate dissertation</article-title>
          .
          <source>Kaunas</source>
          .
          <volume>31</volume>
          p.
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          <string-name>
            <surname>About</surname>
            <given-names>OMG</given-names>
          </string-name>
          ®.
          <source>2015 December 18 d.</source>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          <source>OMG® Specifications</source>
          .
          <year>2017</year>
          http://www.omg.org/spec/index.htm.
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          <string-name>
            <surname>Veitaite</surname>
            ,
            <given-names>I.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lopata</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          (
          <year>2014</year>
          )
          <article-title>Enterprise Model, MOF and ISO Standards Based Information System's Development Process</article-title>
          .
          <source>International Conference on Business Information Systems</source>
          , p.
          <fpage>73</fpage>
          -
          <lpage>79</lpage>
          . ISBN 978-3-
          <fpage>319</fpage>
          -11459-0.
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [10]
          <string-name>
            <surname>Mark</surname>
            <given-names>H.</given-names>
          </string-name>
          <string-name>
            <surname>Linehana</surname>
          </string-name>
          , Ed Barkmeyerb , and
          <string-name>
            <surname>Stan Hendryx</surname>
          </string-name>
          (
          <year>2012</year>
          )
          <article-title>The DateTime Vocabulary</article-title>
          .
          <article-title>OASIS Advancing open standards for the information society</article-title>
          .
          <source>FOIS</source>
          . p.
          <fpage>265</fpage>
          -
          <lpage>378</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [11]
          <string-name>
            <given-names>OMG</given-names>
            <surname>Business Process Management Portal</surname>
          </string-name>
          .
          <source>2013 December</source>
          <volume>16</volume>
          d. Interactive: http://www.omg.org/bpm/.
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [12]
          <string-name>
            <surname>INTRODUCTION TO OMG'S UNIFIED MODELING LANGUAGE</surname>
          </string-name>
          <article-title>® (UML®). 2005 July</article-title>
          . Interactive: http://www.uml.org/what-is-uml.htm.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [13]
          <string-name>
            <surname>WHAT IS SYSML</surname>
          </string-name>
          <article-title>®? 2012 June http</article-title>
          ://www.omgsysml.org/what-is-sysml.htm.
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [14]
          <string-name>
            <given-names>Object</given-names>
            <surname>Management Group Business Process Model</surname>
          </string-name>
          and Notation. 2016 Interactive: http://www.bpmn.org/.
        </mixed-citation>
      </ref>
      <ref id="ref11">
        <mixed-citation>
          [15]
          <string-name>
            <given-names>BPMN</given-names>
            <surname>Introduction</surname>
          </string-name>
          and History. 2016 http://www.trisotech.com/articles/bpmn-introduction-history.
        </mixed-citation>
      </ref>
      <ref id="ref12">
        <mixed-citation>
          [16]
          <string-name>
            <surname>RECKER</surname>
          </string-name>
          , Jan; INDULSKA, Marta; ROSEMANN, Michael; GREEN,
          <string-name>
            <surname>Peter.</surname>
          </string-name>
          (
          <year>2006</year>
          )
          <article-title>How Good Is BPMN Really? Insights From Theory And Practice</article-title>
          .
          <source>Proceedings 14th European Conference on Information Systems</source>
          , [interaktyvus] Goeteborg, Sweden. Interactive: http://eprints.qut.edu.au/4636/1/4636.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref13">
        <mixed-citation>
          [17]
          <string-name>
            <surname>Information</surname>
          </string-name>
          technology - Object
          <source>Management Group Business Process Model and Notation</source>
          .
          <source>2013 November</source>
          <volume>3</volume>
          d. ISO/IEC 19510:
          <string-name>
            <surname>2013(E). Interactive</surname>
          </string-name>
          : http://www.omg.org/spec/BPMN/ISO/19510/PDF.
        </mixed-citation>
      </ref>
      <ref id="ref14">
        <mixed-citation>
          [18]
          <string-name>
            <surname>Kenneth</surname>
            <given-names>D.</given-names>
          </string-name>
          <string-name>
            <surname>Evensen</surname>
          </string-name>
          and
          <string-name>
            <surname>Dr. Kathryn Anne Weiss</surname>
          </string-name>
          (
          <year>2010</year>
          )
          <article-title>A Comparison and Evaluation of Real-Time Software Systems Modeling Languages</article-title>
          .
          <source>AIAA Infotech@Aerospace</source>
          <year>2010</year>
          20 -
          <fpage>22</fpage>
          April 2010, Atlanta, Georgia.
        </mixed-citation>
      </ref>
      <ref id="ref15">
        <mixed-citation>
          [19]
          <string-name>
            <given-names>Sparx</given-names>
            <surname>Systems</surname>
          </string-name>
          Pty Ltd.
          <article-title>(</article-title>
          <year>1998</year>
          -2011), Comparing UML Activities to BPMN Processes.
        </mixed-citation>
      </ref>
      <ref id="ref16">
        <mixed-citation>
          [20]
          <string-name>
            <surname>Stephen</surname>
            <given-names>A.</given-names>
          </string-name>
          <string-name>
            <surname>White</surname>
          </string-name>
          (
          <year>2004</year>
          )
          <article-title>Process Modeling Notations and Workflow Patterns</article-title>
          .
          <source>IBM Corporation</source>
          . p.
          <fpage>23</fpage>
          -
          <lpage>24</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref17">
        <mixed-citation>
          [21]
          <string-name>
            <surname>Kuster</surname>
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Lutzenberger</surname>
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hessler</surname>
            <given-names>A</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hirsch</surname>
            <given-names>B.</given-names>
          </string-name>
          (
          <year>2012</year>
          )
          <article-title>Integrating process modelling into multi-agent system engineering, Fig. 5. BPMN diagram for use case Close Auction</article-title>
          . Interactive: https://www.researchgate.net/publication/220535349_
          <article-title>Integrating_proces s_modelling_into_multi-agent_system_engineering.</article-title>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>