<!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>Parametrisation of CSA-nets</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Mohammed Alahmadi</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>School of Computing, Newcastle University Science Square</institution>
          ,
          <addr-line>Newcastle upon Tyne, NE4 5TG</addr-line>
          ,
          <country country="UK">United Kingdom</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>The modelling approach proposed in this paper has its origin in the structured occurrence nets [1] that are a Petri net-based model for the representation of the execution behavior of complex evolving systems. They are an extension of occurrence nets which represent the causality and concurrency information relating to a single system execution. In general, a structured occurrence net consists of several occurrence nets linked through different types of formal relationships. A particular formal model we are using in this paper are the communication structured occurrence nets (CSA-nets), which are generalisations of communication structured occurrence nets (a subclass of structured occurrence nets [1]), where individual acyclic nets are linked by buffer places capable of modelling both asynchronous and synchronous communication between different subsystems.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>d
f
r2 : {p2} {b} r3 : {p3}</p>
      <p>t2
r1 : {p1} {a}
pp11::12 t1
structure of a system model does not need to be re-built each time it is run. Such an approach
will allow the reuse of the model multiple times and increase comprehension and make larger
systems under investigation easier to handle. Figure 1 illustrates the transition from the original
CSA-nets to their parameterised versions.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>M.</given-names>
            <surname>Koutny</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Randell</surname>
          </string-name>
          ,
          <article-title>Structured occurrence nets: A formalism for aiding system failure prevention and analysis techniques</article-title>
          ,
          <source>Fundamenta Informaticae</source>
          <volume>97</volume>
          (
          <year>2009</year>
          )
          <fpage>41</fpage>
          -
          <lpage>91</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <given-names>M.</given-names>
            <surname>Alahmadi</surname>
          </string-name>
          ,
          <article-title>Master channel places for communication structured acyclic nets</article-title>
          , in: M.
          <string-name>
            <surname>Köhler-Bussmeier</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          <string-name>
            <surname>Kindler</surname>
          </string-name>
          , H. Rölke (Eds.),
          <source>Proceedings of the International Workshop on Petri Nets and Software Engineering</source>
          <year>2021</year>
          , volume
          <volume>2907</volume>
          <source>of CEUR Workshop Proceedings, CEUR-WS.org</source>
          ,
          <year>2021</year>
          , pp.
          <fpage>233</fpage>
          -
          <lpage>240</lpage>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>