<?xml version="1.0" encoding="UTF-8"?><rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel rdf:about="http://dl.gi.de/handle/20.500.12116/39453">
<title>Modellierung 2016 (LNI P254)</title>
<link>http://dl.gi.de/handle/20.500.12116/39453</link>
<description/>
<items>
<rdf:Seq>
<rdf:li rdf:resource="http://dl.gi.de/handle/20.500.12116/832"/>
<rdf:li rdf:resource="http://dl.gi.de/handle/20.500.12116/830"/>
<rdf:li rdf:resource="http://dl.gi.de/handle/20.500.12116/834"/>
<rdf:li rdf:resource="http://dl.gi.de/handle/20.500.12116/831"/>
</rdf:Seq>
</items>
<dc:date>2026-07-21T13:29:58Z</dc:date>
</channel>
<item rdf:about="http://dl.gi.de/handle/20.500.12116/832">
<title>NESTML: a modeling language for spiking neurons</title>
<link>http://dl.gi.de/handle/20.500.12116/832</link>
<description>NESTML: a modeling language for spiking neurons
Plotnikov, Dimitri; Blundell, Inga; Ippen, Tammo; Eppler, Jochen Martin; Morrison, Abigail; Rumpe, Bernhard
Oberweis, Andreas; Reussner, Ralf
Biological nervous systems exhibit astonishing complexity. Neuroscientists aim to capture this complexity by modeling and simulation of biological processes. Often very complex models are necessary to depict the processes, which makes it difficult to create these models. Powerful tools are thus necessary, which enable neuroscientists to express models in a comprehensive and concise way and generate efficient code for digital simulations. Several modeling languages for computational neuroscience have been proposed [Gl10, Ra11]. However, as these languages seek simulator independence they typically only support a subset of the features desired by the modeler. In this article, we present the modular and extensible domain specific language NESTML, which provides neuroscience domain concepts as first-class language constructs and supports domain experts in creating neuron models for the neural simulation tool NEST. NESTML and a set of example models are publically available on GitHub.
</description>
<dc:date>2016-01-01T00:00:00Z</dc:date>
</item>
<item rdf:about="http://dl.gi.de/handle/20.500.12116/830">
<title>On the de-facto standard of event-driven process chains: how EPC is defined in literature</title>
<link>http://dl.gi.de/handle/20.500.12116/830</link>
<description>On the de-facto standard of event-driven process chains: how EPC is defined in literature
Riehle, Dennis M.; Jannaber, Sven; Karhof, Arne; Thomas, Oliver; Delfmann, Patrick; Becker, Jörg
Oberweis, Andreas; Reussner, Ralf
The Business Process Modelling Notation (BPMN) and the Event-driven Process Chain (EPC) are both frequently used modelling languages to create business process models. While there is a well-defined standard for BPMN, such a standard is missing for EPC. As a standard would be beneficial to improve interoperability among different vendors, this paper aims at providing the means for future EPC standardization. Therefore, we have conducted a structured literature review of the most common EPC variants in IS research. We provide a structured overview of the evolution of different EPC variants, describe means and capabilities and elaborate different criteria for decision-making in regard to including EPC variants in a standardization process.
</description>
<dc:date>2016-01-01T00:00:00Z</dc:date>
</item>
<item rdf:about="http://dl.gi.de/handle/20.500.12116/834">
<title>Towards a catalog of structural and behavioral verification tasks for UML/OCL models</title>
<link>http://dl.gi.de/handle/20.500.12116/834</link>
<description>Towards a catalog of structural and behavioral verification tasks for UML/OCL models
Hilken, Frank; Niemann, Philipp; Gogolla, Martin; Wille, Robert
Oberweis, Andreas; Reussner, Ralf
Verification tasks for UML and OCL models can be classified into structural and behavioral tasks. For both task categories a variety of partly automatic solving approaches exist. But up to now, different interpretations of central notions as, for example, `consistency' or `reachability' can be found in current approaches and tools. This paper is designed to clarify central verification notions and to establish a collection of typical verification tasks that are common to multiple approaches and tools. In addition, the verification tasks are categorized with the aim of creating a central catalog of tasks, providing a common understanding of the terms used in model verifications.
</description>
<dc:date>2016-01-01T00:00:00Z</dc:date>
</item>
<item rdf:about="http://dl.gi.de/handle/20.500.12116/831">
<title>On the de-facto standard of event-driven process chains: reviewing EPC implementations in process modelling tools</title>
<link>http://dl.gi.de/handle/20.500.12116/831</link>
<description>On the de-facto standard of event-driven process chains: reviewing EPC implementations in process modelling tools
Karhof, Arne; Jannaber, Sven; Riehle, Dennis M.; Thomas, Oliver; Delfmann, Patrick; Becker, Jörg
Oberweis, Andreas; Reussner, Ralf
Nowadays, most process modelling tools implement popular modelling languages such as the Business Process Model and Notation (BPMN) or the Event-driven Process Chain (EPC). However, in contrast to BPMN, no effort has yet been undertaken to standardize the EPC language, thus rendering EPCs as being merely a de-facto standard for business process modelling. Subsequently, this paper addresses this issue by laying ground for a successful EPC standardization. To achieve this task, several process modelling tools have been evaluated regarding their implementation of the EPC language with the objective to derive consensus about important language constructs. The evaluation reveals that there is a high degree of variety in the way tools implement EPCs. Especially syntax, semantic and pragmatic of the EPC language are not perceived homogenously and, in fact, commonly neglected. Hence, our research provides valuable implications for further EPC standardization by highlighting the state-of-the-art of the EPC from a software point of view.
</description>
<dc:date>2016-01-01T00:00:00Z</dc:date>
</item>
</rdf:RDF>
