International audience

In the context of complex system development, heterogeneous modeling responds to the need to integrate several domains. This need requires the use of the most appropriate formalism and tooling for each domain to be efficient. Model federation promotes the semantic interoperability of heterogeneous models by providing the means to reify correspondences between different model elements, add custom behaviors and bridge the gap between technological spaces. As such, it can be used as an infrastructure to address many different system engineering problems. This is what we have been doing for over a decade, as part of a close collaboration between a small software engineering startup and academia. This paper reports on this experience.

With the ever growing digitization of activities, software systems are getting more and more complex. They must comply with new usages, varied needs, and are permanently exposed to new security vulnerabilities.

Cybersecurity is becoming vital as industries are gradually moving from automating physical processes to a higher level automation using cyber physical systems (CPS) and internet of things (IoT). In this context, security is becoming a continuous process that runs in parallel to other processes during the complete life cycle of a system. Traditional threat analysis methods use design models alongside threat models as an input for security analysis, hence missing the life-cycle-based dynamicity required by the security concern. In this paper, we argue for an attacker-aware systems modeling language that exposes the systems attack surfaces. For this purpose, we have designed Pimca, a domain specific modeling language geared towards capturing the attacker point of view of the system. This study introduces the formalism along with the Pimca workbench, a framework designed to ease the development and manipulation of the Pimca models. Finally, we present two relevant use cases, serving as a preliminary validation of our approach. © Copyright 2020 by SCITEPRESS - Science and Technology Publications, Lda. All rights reserved.

Researchers in software engineering have been striving to produce new methods to improve the quality of development methodologies to consequently produce quality products. Proposition of iterative and evolutionary approaches was triggered by the realization that requirements engineering is not confined to the initial phases of software development only. With this shift of perspective, requirements engineering has become more or less a continuous process in software development lifecycles. We believe that existing requirements engineering approaches and associated tooling leave a room for improvement in putting 'continuity' into practice. A continuous requirements engineering methodology needs to take into account different concerns of all the stakeholders involved in the process. Approaches like KAOS bring the multi-view nature of requirements modeling in focus by using different views for goal, responsibility, object and operation modeling. We argue that a multi-view approach, maintaining a dynamic link between the requirement models and multiple sources of requirements, can offer a better support for continuous requirements engineering methodology. In this paper, we expand on this argument and present the early findings with the associated in progress tooling support.