Not (strictly) relying on SysML for MBSE: Language, tooling and development perspectives: The Arcadia/Capella rationale

Bonnet, Stéphane; Voirin, Jean‐Luc; Exertier, Daniel; Normand, Véronique

doi:10.1109/syscon.2016.7490559

“…-Number of components in time by subsystem 5 . we counted the number of components composing a subsystem at each release date of that subsystem.…”

Section: Research Methods and Objectivesmentioning

confidence: 99%

“…Thales DMS' design process involves different and specific teams that work together throughout the life cycle of a product. The system engineering team builds systems' design models using dedicated methods like Arcadia [22] and modeling tools like Capella [5]. System engineers model interactions between hardware entities, software entities, users, etc.…”

Section: Engineering Impact: Design Traceability and Co-workingmentioning

confidence: 99%

Reuse in component-based prototyping: an industrial experience report from 15 years of reuse

LaBorde¹,

Costiou

²

,

Pors³

et al. 2022

Innovations Syst Softw Eng

1

0

View full text Add to dashboard Cite

At Thales Defense Mission Systems, software products first go through an industrial prototyping phase. We elaborate evolutionary prototypes which implement complete business behavior and fulfill functional requirements. We elaborate and evolve our solutions directly with end-users who act as stake-holders in the products' design. Prototypes also serve as models for the final products development. Because software products in the defense industry are developed over many years, this prototyping phase is crucial. Therefore, reusing software is a high-stakes issue in our activities. Component-oriented development helps us to foster reuse throughout the life cycle of our products. The work presented in this paper stems from 15 years of experience in developing prototypes for the defense industry. We directly reuse component implementations to build new prototypes from existing ones. We reuse component interfaces transparently in multiple prototypes, whatever the underlying implementation solutions. This kind of reuse spans prototypes and final products which are deployed on different execution platforms. We reuse non-component legacy software that we integrate in our component architectures. In this case, we seamlessly augment standard classes

show abstract

“…Thales DMS' design process involves different and specific teams that work together throughout the life cycle of a product. The system engineering team builds systems' design models using dedicated methods like Arcadia [20] and modeling tools like Capella [5]. System engineers model interactions between hardware entities, software entities, users, etc.…”

Section: Engineering Impact: Design Traceability and Co-workingmentioning

confidence: 99%

15 Years of Reuse Experience in Evolutionary Prototyping for the Defense Industry

LaBorde¹,

Costiou

²

,

Pors³

et al. 2020

Lecture Notes in Computer Science

View full text Add to dashboard Cite

At Thales Defense Mission Systems, software products first go through an industrial prototyping phase. We elaborate evolutionary prototypes which implement complete business behavior and fulfill functional requirements. We elaborate and evolve our solutions directly with end-users who act as stake-holders in the products' design. Prototypes also serve as models for the final products development. Because software products in the defense industry are developed over many years, this prototyping phase is crucial. Therefore, reusing software is a high-stakes issue in our activities. Component-oriented development helps us to foster reuse throughout the life cycle of our products. The work presented in this paper stems from 15 years of experience in developing prototypes for the defense industry. We directly reuse component implementations to build new prototypes from existing ones. We reuse component interfaces transparently in multiple prototypes, whatever the underlying implementation solutions. This kind of reuse spans prototypes and final products which are deployed on different execution platforms. We reuse non-component legacy software that we integrate in our component architectures. In this case, we seamlessly augment standard classes with component behavior, while preserving legacy code. In this paper, we present our component programming framework with a focus on component reuse in the context of evolutionary prototyping. We report three scenarios of reuse that we encounter regularly in our prototyping activity.

show abstract

“…As explained in [7,8], SysML on its own is not the best suited to apply a development method or build meaningful models in systems engineering. We have to ensure that we manipulate system concepts that are represented by corresponding model elements, along with proper semantic and relationships.…”

Section: State Of the Artmentioning

confidence: 99%

“…However, it is possible to adapt SysML to our needs through the use of profile, constraints and additional semantic. The Arcadia method [7] is an example of an adaptation of SysML to system development using system concepts. Arcadia is not considered as a DSML by its creators because of the broad scope of its application and its links to modeling standards.…”

Section: State Of the Artmentioning

confidence: 99%

SysML Models Verification and Validation in an Industrial Context: Challenges and Experimentation

Baduel

¹

,

Chami

²

,

Bruel

³

et al. 2018

Lecture Notes in Computer Science

View full text Add to dashboard Cite

This paper presents a solution for SysML model verification and validation, with a return of experience from its implementation in an industrial context. We present this solution as a way to overcome issues regarding the use of SysML in an industrial context. We contribute by providing a method and a list of the existing challenges and experimentation results. We advocate the need to have semantics for SysML models without having to define a full domain-specific modeling language. We highlight the work, requirements and benefits that arise from the application of existing technical solutions, and hint at new perspectives and future development in system verification and validation.

show abstract

Not (strictly) relying on SysML for MBSE: Language, tooling and development perspectives: The Arcadia/Capella rationale

Cited by 15 publications

References 3 publications

Reuse in component-based prototyping: an industrial experience report from 15 years of reuse

Reuse in component-based prototyping: an industrial experience report from 15 years of reuse

15 Years of Reuse Experience in Evolutionary Prototyping for the Defense Industry

SysML Models Verification and Validation in an Industrial Context: Challenges and Experimentation

Contact Info

Product

Resources

About