1,720,988 research outputs found
Lightweight consistency checking for advancing continuous model-based development in industry
No full textFor the development of modern software-intensive systems, a large number of development artifacts are created and maintained to design and implement their intended structure and behavior. In this thesis, we consider continuous model-based development settings in which models and other development artifacts are developed incrementally, in short development cycles. Inconsistencies between these development artifacts occur continuously throughout the system's development and maintenance, due to the incremental nature of the development of these artifacts. However, when not known and never resolved, such inconsistencies may ultimately cause failures in developed systems. Therefore, consistency checking across development artifacts is often desirable. Consistency checking approaches face challenges such as adoption in existing engineering settings, the potential informality and incompleteness of models and other development artifacts, as well as the need for shorter development cycles. We show a tight coupling between introducing short development cycles and the need for increased support for consistency checking across models and other development artifacts. From a surveyed set of industrial settings, we identify the need for lightweight consistency-checking approaches. Four aspects that make a consistency checking approach lightweight are formulated on the basis of the surveyed industrial settings. We then study specific challenges to developing consistency checks in four concrete industrial settings. We summarize our experiences in these settings in reference schemas showing the steps of creation and adoption of lightweight consistency checks from various starting points. In summary, this thesis presents contributions to lightweight consistency checking in industrial settings and ultimately aims to facilitate the adoption of continuous model-based development
Advancing Continuous Model-Based Development in Industry
No full textFor the development of complex software systems, two prominent paradigms have become popular in the industry: model-based development and agile software development. Model-based development holds the promise of improving the productivity of software development through abstraction, by focusing on the problem domain and capturing it in models. Agile methods are sometimes seen as conflicting with model-based development due to their favored short development cycles as opposed to the apparent longer development phases in model-based development. In this licentiate thesis, we explore how development can benefit from combining the two practices successfully into continuous model-based development. We present four papers studying this topic in the industrial development of complex embedded systems. The first two papers present investigations of the current state-of-practice and specific challenges of combining the agile practice of continuous integration and model-based development. In the third and fourth paper, we focus on one of those challenges: model synchronization, i.e. the management of consistency between disparate development artifacts describing the same system. We propose a lightweight approach that notifies developers of introductions of inconsistency between different models. Lastly, we consider a second dimension of the management of different development artifacts: variability. We provide support for alleviating manual tasks in maintaining consistency across variants of models in a product line created to describe system variants
Considerations about consistency management for industrial model-based development
No full textModel-based development of complex embedded systems commonly leverages multiple models to describe systems at different levels of abstraction and from different viewpoints. Inconsistencies between these models may cause delays or late changes throughout system design, development and maintenance. Therefore, an efficient model-based development practice requires support for managing consistency between different models. This is complicated in practice because these models are possibly created in several different modelling languages and modelling tools. Furthermore, in order to be suitable for industrial adoption, consistency checking support must fit within current development processes and environments. This extended abstract describes a model-based development scenario from which a need for consistency checking emerges, followed by a discussion of requirements for consistency checking from a development process point of view. We also include a brief summary of early work on a prototype tool addressing these requirements. Copyright © 2019 for this paper by its authors. Use permitted under Creative Commons License Attribution 4.0 International (CC BY 4.0).</p
Going Beyond Counting First Authors in Author Co-citation Analysis
Get PDFThe present study examines one of the fundamental aspects of author co-citation analysis (ACA) - the way co-citation
counts are defined. Co-citation counting provides the data on which all subsequent statistical analyses and mappings
are based, and we compare ACA results based on two different types of co-citation counting - the traditional type that
only counts the first one among a cited work's authors on the one hand and a non-traditional type that takes into
account the first 5 authors of a cited work on the other hand. Results indicate that the picture produced through this non-traditional author co-citation counting contains more coherent author groups and is therefore considerably clearer. However, this picture represents fewer specialties in the research field being studied than that produced through the traditional first-author co-citation counting when the same number of top-ranked authors is selected and analyzed. Reasons for these effects are discussed
How to Live with Inconsistencies in Industrial Model-Based Development Practice
No full textModern development of complex embedded systems utilizes models to describe multiple different views on the same system. Consistency between these models is essential to successful development but ensuring it is in current practice often a manual effort. In this research project, we aim to develop a methodology that helps developers to maintain consistency in industrial model-based development projects by identifying inconsistencies throughout the development and maintenance of the system. For such support to be applicable in industrial practice, it should fit in with current development, i.e., should be able to identify inconsistencies between models expressed in different modeling languages and created in different modeling tools. Furthermore, the required user interaction to defining consistency checks should be minimal. This paper sketches an approach meeting these requirements, initial results towards it and discusses future research plans towards a doctoral dissertation.</p
How Do Practitioners Reason About Security Requirements? : An Interview Study
No full textIn the development of modern software-intensive systems, security aspects are increasingly emphasized, with new laws and regulations putting more demands on manufacturers. Requirements elicitation must therefore carefully consider security aspects. The literature contains various frameworks that have been proposed to aid in the elicitation of these types of requirements. We are interested to understand how, in industrial practice, persons responsible for cybersecurity reason about so-called 'security requirements'. To find out, we perform eight semi-structured interviews with experts having leading roles in cybersecurity in large companies. We identify the concepts that they leverage when reasoning about security requirements, what other aspects they look at when identifying security requirements, how they differ between security requirements and other requirements, and what their definition of a security requirement is. In this paper, we report on this interview study and our analysis of it. We highlight the commonalities and crucial differences between experts' reasoning, and a surprising spread of conclusions regarding the identification of example requirements as being security requirements or not. Our analysis opens a new perspective on how to deal with security requirements, we hypothesize the benefits of using multiple approaches for elicitation and a single approach for requirements specification.</p
Flexible Modelling : a Systematic Literature Review
No full textCanonical software and systems modelling regards only models that conform to modelling languages and that are created in modelling tools. In practice, these models are often supplemented with free-form activities such as sketching and informal diagramming. Flexible modelling has been proposed to benefit from the combination of free-form activities, from relaxed to no conformance to modelling languages, and canonical modelling with more or less strict conformance of diagrammatic elements to modelling languages. Various tools and approaches have proposed mechanisms to support flexible modelling. In this paper, we report on a systematic literature review of these tools and approaches. We present an analysis of the existing body of knowledge in this area and discuss open research challenges that can help the modelling community identify promising next steps in this area.</p
- …
