Logo des Repositoriums

Auflistung nach Autor:in "Ratiu, Daniel"

1 - 3 von 3
  • Konferenzbeitrag
    Model-based development tools for embedded systems in the industry – Results from an empirical investigation –
    (Software Engineering 2010 – Workshopband (inkl. Doktorandensymposium), 2010) Herrmannsdoerfer, Markus; Kofler, Thomas; Merenda, Stefano; Ratiu, Daniel; Thyssen, Judith
    Model-based development (MBD) is adopted in practice in different degrees. A prerequisite for building a new generation of tools for model-based development of embedded systems is to gain an overview over their current use and the needs of the industry. In this paper, we present the results of an empirical study-that we conducted in the context of the SPES2020 research project-about the use of modelbased development tools in industrial projects. We investigated the following general research questions by collecting empirical data from several industrial project partners: (1) What is the status quo of the tools currently used in industry? and (2) What are the requirements for the next generation of industrial tools? The result of our study shows that there is a considerable heterogeneity in both the development tools and in the manner in which model-based development is perceived in different industrial branches (e. g., automation, avionics, automotive). Furthermore, we identified that the most important need for industrialization of model-based development in the future is a higher integration of different tools and methods.
  • Konferenzbeitrag
    A system for seamless abstraction layers for model-based development of embedded software
    (Software Engineering 2010 – Workshopband (inkl. Doktorandensymposium), 2010) Thyssen, Judith; Ratiu, Daniel; Schwitzer, Wolfgang; Harhurin, Alexander; Feilkas, Martin; Thaden, Eike
    Model-based development aims at reducing the complexity of software development by the pervasive use of adequate models throughout the whole development process starting from early phases up to implementation. In this paper we present a conceptual framework to holistically classify developed models along different levels of abstraction. We do this by defining adequate abstractions for different development stages while ignoring the information that is not relevant at a particular development step or for a certain stakeholder. The abstraction is achieved in terms of the granularity level of the system under study (e. g. system, sub-system, sub-sub-system) and in terms of the information that the models contain (e. g. specification of functionality, description of architecture, deployment on specific hardware). We also present the relation between models that describe different perspectives of the system or are at different granularity levels. However, we do not address the process to be followed for building these models.
  • Konferenzbeitrag
    Taming the Software Development Complexity with Domain Specific Languages
    (Modellierung 2018, 2018) Ratiu, Daniel; Nehls, Holger; Michel, Jochen
    Modern computed tomography (CT) scanners are highly complex and flexible devices. This versatility is realized with a multitude of interconnected parameters and rules which are defined by domain experts in so-called scanner model specifications distributed over almost one hundred documents. The primarily used tools to write these documents (e.g. MS Word, MS Excel) are domain agnostic and they support only plain natural-language for the specification. Consequently, maintaining a valid scanner specification is a tedious, error-prone and therefore expensive process. To tackle the complexity of scanners parameters specifications, over the last two years we developed and deployed an eco-system of domain specific languages (DSLs) and associated tooling, covering a central portion of the scanner domain. The languages are developed using the Jetbrains’ MPS language workbench. In this paper, we present our experiences with developing our language eco-system. We briefly describe the language architecture, the design and development process that led us there, and discuss variation points of our approach and present in more detail a set of lessons learnt and best practices.