Evolution und Komposition von Softwaresystemen: Software-Produktlinien als Beitrag zu Flexibilität und Langlebigkeit

Software systems are today bigger, more complex and of higher importance for products and services than a decade before. At the same time changes are required many more frequently and of a larger size. Furthermore, they have to be implemented faster. Additionally, the software must achieve a higher life span, particularly because of the cost of its development. In the past, Object-Oriented Programming and Reuse techniques did not provide the expected success. The introduction of software product lines respectively system families makes possible it to reach a degree of prefabrication similar to the one of serial production. At the same time they facilitate the delivery of product variants with a short time to market. In this work methods of the methods of domain analysis are integrated with Reuse approaches and techniques of Generative Programming, and a methodology for product line development is presented. Feature models are used as means expressing variability and product configurations, so that the prefabrication be planned and the production of customer-specific products can be controlled. By enforcing the formalization in terms of syntax and semantics, feature models are made accessible to tools and automation. Object-oriented design models and architecture are separated into fine-granular components in such a way that new products can easily be developed as combinations of those components. The implementation of such products is automated by the composition of source code components. The composition of object models separated similarly enables a uninterrupted automation for the product development, which is controlled by a customer by means of a feature selection. To facilitate such a composition, the Hyperspace approach is applied to UML to Hyper/UML, which makes possible a feature-driven separation and composition of object models. In this way slim products can be developed, containing only the actually needed functionality. For the evolution of product lines and for the integration of existing solutions and components into the evolution, Reverse Engineering and Refactoring techniques are integrated. Requirements, models and implementation are connected by Traceability links to perform changes consistently. As a consequence, the loss of architectural quality - so-called Architectural Decay - can be avoided during the iterative development process. Measures for the improvement of the project and quality management are regarded briefly, as far as they are of importance for the effectiveness of the developed methods. The applicability and suitability of the results of the work were examined in several industrial projects.Softwaresysteme sind heute umfangreicher, komplexer und von entscheidenderer Bedeutung für Produkte und Dienstleistungen als eine Dekade zuvor. Gleichzeitig sind Änderungen viel häufiger und in größerem Umfang erforderlich. Sie müssen auch schneller realisierbar sein. Zudem muss die Software eine höhere Lebensdauer erreichen, vor allem wegen des Aufwandes zu ihrer Entwicklung. Objektorientierte Programmierung und Wiederverwendungstechniken haben dabei nicht den erwarteten Erfolg gebracht. Die Einführung von Software-Produktlinien beziehungsweise Systemfamilien ermöglichen es, einen der Serienfertigung ähnlichen Vorfertigungsgrad zu erreichen und erlauben es gleichzeitig, kurzfristig Produktvarianten zu erstellen. In dieser Arbeit werden Methoden der Domänenanalyse mit Wiederverwendungsansätzen und Generativen Programmiertechniken verknüpft und eine Methodik zur Produktlinien-Entwicklung vorgestellt. Featuremodelle werden als Ausdrucksmittel für Variabilität und Produktkonfigurationen eingesetzt, damit die Vorfertigung geplant und die Erstellung von kundenspezifischen Produkten gesteuert werden kann. Durch Präzisierung ihrer Syntax und Erweiterung ihrer Semantik werden Featuremodelle einer Nutzung in Werkzeugen zugänglich gemacht. Objektorientierte Entwurfsmodelle und Architektur werden so in feingranulare Komponenten zerlegt, dass Varianten als neue Produkte mit geringem Aufwand erstellbar sind. Die Erstellung der Implementierung solcher Produkte wird durch die Komposition von Quelltext-Komponenten automatisiert. Die Komposition von ebenfalls zerlegten Objektmodellen ermöglicht eine durchgehende Automatisierung der Produkterstellung, die durch einen Kunden mittels der Feature-Auswahl gesteuert wird. Dafür wird mit Hyper/UML eine Umsetzung des Hyperspace-Ansatzes auf die Modellierungssprache UML entwickelt, die eine Feature-gesteuerte Zerlegung und Komposition von Objektmodellen ermöglicht. Damit lassen sich schlanke Produkte entwickeln, die nur die tatsächlich benötigte Funktionalität enthalten. Zur Evolution von Produktlinien und zur Einbindung existierender Lösungen und Komponenten in die Evolution werden Reverse-Engineering- und Refactoring-Techniken integriert. Anforderungen, Modelle und Implementierung werden durch Traceability-Links verbunden, damit Änderungen konsistent durchgeführt werden können. Diese Mittel tragen dazu bei, dass während einer iterativen Entwicklung der Verlust an Architektur-Qualität, das sogenannte Architectural Decay, vermieden werden kann. Maßnahmen zur Verbesserung des Projekt- und Qualitätsmanagements werden kurz betrachtet, soweit sie wichtige Randbedingungen für die Wirksamkeit der Methoden schaffen müssen. Die Anwendbarkeit und Eignung der Ergebnisse der Arbeiten wurde in mehreren industriellen Projekten überprüft.Ilmenau, Techn. Univ., Habil.-Schr., 200

Towards an HPC certification program

The HPC community has always considered the training of new and existing HPC practitioners to be of high importance to its growth. This diversification of HPC practitioners challenges the traditional training approaches, which are not able to satisfy the specific needs of users, often coming from non-traditionally HPC disciplines, and only interested in learning a particular set of competences. Challenges for HPC centres are to identify and overcome the gaps in users’ knowledge, while users struggle to identify relevant skills. We have developed a first version of an HPC certification program that would clearly categorize, define, and examine competences. Making clear what skills are required of or recommended for a competent HPC user would benefit both the HPC service providers and practitioners. Moreover, it would allow centres to bundle together skills that are most beneficial for specific user roles and scientific domains. From the perspective of content providers, existing training material can be mapped to competences allowing users to quickly identify and learn the skills they require. Finally, the certificates recognized by the whole HPC community simplify inter-comparison of independently offered courses and provide additional incentive for participation

Exploring Web Search Engines to Find Architectural Knowledge

Software engineers need relevant and up-to-date architectural knowledge (AK), in order to make well-founded design decisions. However, finding such AK is quite challenging. One pragmatic approach is to search for AK on the web using traditional search engines (e.g. Google); this is common practice among software engineers. Still, we know very little about what AK is retrieved, from where, and how useful it is. In this paper, we conduct an empirical study with 53 software engineers, who used Google to make design decisions using the Attribute-Driven-Design method. Based on how the subjects assessed the nature and relevance of the retrieved results, we determined how effective web search engines are to find relevant architectural information. Moreover, we identified the different sources of AK on the web and their associated AK concepts

Percutaneous dilatational tracheotomy in high-risk ICU patients

BACKGROUND Percutaneous dilatational tracheotomy (PDT) has become an established procedure in intensive care units (ICU). However, the safety of this method has been under debate given the growing number of critically ill patients with high bleeding risk receiving anticoagulation, dual antiplatelet therapy (DAPT) or even a combination of both, i.e. triple therapy. Therefore, the purpose of this study, including such a high proportion of patients on antithrombotic therapy, was to investigate whether PDT in high-risk ICU patients is associated with elevated procedural complications and to analyse the risk factors for bleeding occurring during and after PDT. METHODS PDT interventions conducted in ICUs at 12 European sites between January 2016 and October 2019 were retrospectively analysed for procedural complications. For subgroup analyses, patient stratification into clinically relevant risk groups based on anticoagulation and antiplatelet treatment regimens was performed and the predictors of bleeding occurrence were analysed. RESULTS In total, 671 patients receiving PDT were included and stratified into four clinically relevant antithrombotic treatment groups: (1) intravenous unfractionated heparin (iUFH, prophylactic dosage) (n = 101); (2) iUFH (therapeutic dosage) (n = 131); (3) antiplatelet therapy (aspirin and/or P2Y12 receptor inhibitor) with iUFH (prophylactic or therapeutic dosage) except for triple therapy (n = 290) and (4) triple therapy (DAPT with iUFH in therapeutic dosage) (n = 149). Within the whole cohort, 74 (11%) bleedings were reported to be procedure-related. Bleeding occurrence during and after PDT was independently associated with low platelet count (OR 0.73, 95% CI 0.56, 0.92, p = 0.009), chronic kidney disease (OR 1.75, 95{\%} CI 1.01, 3.03, p = 0.047) and previous stroke (OR 2.13, 95{\%} CI 1.1, 3.97, p = 0.02). CONCLUSION In this international, multicenter study bronchoscopy-guided PDT was a safe and low-complication airway management option, even in a cohort of high risk for bleeding on cardiovascular ICUs. Low platelet count, chronic kidney disease and previous stroke were identified as independent risk factors of bleeding during and after PDT but not triple therapy

Model‐Driven Engineering for Digital Twins: Opportunities and Challenges

Digital twins are increasingly used across a wide range of industries. Modeling is a key to digital twin development—both when considering the models which a digital twin maintains of its real‐world complement (“models in digital twin”) and when considering models of the digital twin as a complex (software) system itself. Thus, systematic development and maintenance of these models is a key factor in effective and efficient digital twin development, maintenance, and use. We argue that model‐driven engineering (MDE), a field with almost three decades of research, will be essential for improving the efficiency and reliability of future digital twin development. To do so, we present an overview of the digital twin life cycle, identifying the different types of models that should be used and re‐used at different life cycle stages (including systems engineering models of the actual system, domain‐specific simulation models, models of data processing pipelines, etc.). We highlight some approaches in MDE that can help create and manage these models and present a roadmap for research towards MDE of digital twins

Problem-Solution Mapping for Evolution Support of Software Architectural Design

Software architectures constitute a crucial factor for the development and evolution of software systems because they have to sustain their quality properties like flexibility, scalability, or security. A software architecture has to reflect the transition from the problem space with quality goals and requirements on one side to the solution space with technical solutions on the other side. A mapping between goals and solutions shall enable long-term evolution of the systems by expressing design knowledge and fundamental decisions explicitly. The gap between the fields of requirements engineering, software architectural design and software quality has not yet been closed. This paper discusses the Goal Solution Scheme, which maps quality goals and goal refinements to architectural principles and solutions. Its application in forward and re-engineering activities is shown, as well as its establishment. The concept has been evaluated in various projects including industrial case studies

Einladung vom 10. Fachgruppentreffen der Fachgruppe OOSE Objektorientierte Software-Entwicklung

Einladung zum 10. Fachgruppentreffen, das im Unterschied zu den bisherigen Treffen als gemeinsamer Workshop der Arbeitskreise durchgeführt wird. Das Umfeld der Fachkonferenz Modellierung 2004 bietet im Anschluss an das Treffen weitere interessante Möglichkeiten der Diskussion, des Erfahrungsaustauschs und des Wissenserwerbs