Logo des Repositoriums

Modellierung 2016 (LNI P254)

Autor*innen mit den meisten Dokumenten  

Auflistung nach:

Neueste Veröffentlichungen

1 - 10 von 18
  • Konferenzbeitrag
    NESTML: a modeling language for spiking neurons
    (Modellierung 2016, 2016) Plotnikov, Dimitri; Blundell, Inga; Ippen, Tammo; Eppler, Jochen Martin; Morrison, Abigail; Rumpe, Bernhard
    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.
  • Konferenzbeitrag
    Tool support for model transformations: on solutions using internal languages
    (Modellierung 2016, 2016) Hinkel, Georg; Goldschmidt, Thomas
    Model-driven engineering (MDE) has proven to be a useful approach to cope with todays ever growing complexity in the development of software systems, yet it is not widely applied in industry. As suggested by multiple studies, tool support is a major factor for this lack of adoption. Existing tools for MDE, in particular model transformation approaches, are often developed by small teams and cannot keep up with advanced tool support for mainstream languages such as provided by IntelliJ or Visual Studio. In this paper, we propose an approach to leverage existing tool support for model transformation using internal model transformation languages and investigate design decisions and their consequences for inherited tool support. The findings are used for the design of an internal model transformation language on the .NET platform.
  • Konferenzbeitrag
    Towards a catalog of structural and behavioral verification tasks for UML/OCL models
    (Modellierung 2016, 2016) Hilken, Frank; Niemann, Philipp; Gogolla, Martin; Wille, Robert
    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.
  • Konferenzbeitrag
    On the de-facto standard of event-driven process chains: reviewing EPC implementations in process modelling tools
    (Modellierung 2016, 2016) Karhof, Arne; Jannaber, Sven; Riehle, Dennis M.; Thomas, Oliver; Delfmann, Patrick; Becker, Jörg
    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.
  • Konferenzbeitrag
    Infrastructure to use OCL for runtime structural compatibility checks of simulink models
    (Modellierung 2016, 2016) Bertram, Vincent; Manhart, Peter; Plotnikov, Dimitri; Rumpe, Bernhard; Schulze, Christoph; Wenckstern, Michael Von
    Functional development of embedded software systems in the automotive industry is mostly done using models consisting of highly adjustable and potentially reusable components. A basic pre-requisite for reuse is structural compatibility of available component versions and variants. Since each vendor in the automotive domain uses its own toolchain with corresponding models, an unified modeling notation is needed. For this reason based on a detailed feature analysis of wellestablished and commonly used modeling languages, a meta-model has been derived that allows checking structural compatibility, even between heterogeneous modeling languages.
  • Konferenzbeitrag
    Vom Clean Model zum Clean Code
    (Modellierung 2016, 2016) Vasileva, Anna; Schmedding, Doris
    In diesem Beitrag wird der Zusammenhang zwischen Code-Qualität und UML- Modellen in einem Software-Entwicklungsprozess in der Informatik-Ausbildung vorgestellt. Es wird untersucht, welche der im Code sichtbar werdenden Mängel bereits im Modell erkannt werden können. Werkzeuge zur statischen Code-Analyse und Refactoring-Techniken unterstützen die Studierenden beim Entdecken und Beseitigen der Qualitätsmängel im Programm-Code. Eine Analyse der studentischen Projekte hat gezeigt, dass sich manche Code-Mängel im Nachhinein nur schwer beseitigen lassen. Aus diesem Grund müssen Qualitätsaspekte bereits beim Modellieren in Betracht gezogen werden. Frühzeitig erkannte Mängel lassen sich mit geringeren Kosten beseitigen als spät erkannte Defekte.
  • Konferenzbeitrag
    On the de-facto standard of event-driven process chains: how EPC is defined in literature
    (Modellierung 2016, 2016) Riehle, Dennis M.; Jannaber, Sven; Karhof, Arne; Thomas, Oliver; Delfmann, Patrick; Becker, Jörg
    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.
  • Konferenzbeitrag
    Tunit - unit testing for template-based code generators
    (Modellierung 2016, 2016) Kolassa, Carsten; Look, Markus; Müller, Klaus; Roth, Alexander; Reiß, Dirk; Rumpe, Bernhard
    Template-based code generator development as part of model-driven development (MDD) demands for strong mechanisms and tools that support developers to improve robustness, i.e., the desired code is generated for the specified inputs. Although different testing methods have been proposed, a method for testing only parts of template-based code generators that can be employed in the early stage of development is lacking. Thus, in this paper we present an approach and an implementation based on JUnit to test template-based code generators. Rather than testing a complete code generator, it facilitates partial testing by supporting the execution of templates with a mocked environment. This eases testing of code generators in early stages of development as well as testing new or changed parts of a code generator. To test the source code generated by the templates under test, different methods are presented including string comparisons, API-based assertions, and abstract syntax tree based assertions.
  • Konferenzbeitrag
    Automatically binding variables of invariants to violating elements in an OCL-aligned xbase-language
    (Modellierung 2016, 2016) Fiss, Sebastian; Kramer, Max E.; Langhammer, Michael
    Constraints that have to hold for all models of a modeling language are often specified as invariants using the Object Constraint Language (OCL). If violations of such invariants shall be documented or resolved in a software system, the exact model elements that violate these conditions have to be computed. OCL validation engines provide, however, only a single context element at which a check for a violated invariant originated.Therefore, the computation of elements that caused an invariant violation is often specified in addition to the invariant declaration with redundant information. These redundancies can make it hard to develop and maintain systems that document or resolve invariant violations. In this paper, we present an automated approach and tool for declaring and binding parameters of invariants to violating elements based on boolean invariant expressions that are similar to OCL invariants. The tool computes a transformed invariant that returns violating elements for each iterator variable of the invariant expression that matches an explicitly declared invariant parameter. The approach can be used for OCL invariants and all models of languages conforming to the Meta- Object Facility (MOF) standard. We have evaluated our invariant language and transformation tool by transforming 88 invariants of the Unified Modeling Language (UML).
  • Konferenzbeitrag
    BPM considered harmful (Kurzbeitrag)
    (Modellierung 2016, 2016) Berner, Stefan
    Business Process Modeling (BPM) spielt eine grosse Rolle in den frühen Schritten der Softwareentwicklung. Eine zu grosse Rolle nach Meinung des Autors. Fast alle Vorgehensmethoden empfehlen für den Beginn einer Geschäftsmodellierung BPM. Fast alle Business-Analysten nutzen BPM als Einstieg und einfachsten Zugang zu Wissen und Verständnis um eine Geschäftswelt. Ohne gemeinsames Verständnis der Begriffe und ihrer Relevanz für eine Umgebung können weder künftige Nutzende noch Informatiker gute Geschäftsprozesse modellieren. BPM ist nicht der beste Weg dieses gemeinsame Verständnis zu erlangen. BPM hat weitere gravierende Nachteile, die es als Einstiegsvorgehen in ein IT-Projekt ungeeignet machen. Dieses Paper zeigt die Nachteile des BPM auf. Es zeigt weiter auf, wie vor der Prozessmodellierung ein besseres Verständnis der zu modellierenden Welt erlangt werden kann.