Towards a Maturity Assessment Scale for the Systems Engineering Assets Valorization to Facilitate Model‐Based Systems Engineering Adoption

Wu, Quentin; Gouyon, David; Boudau, Sophie; Levrat, Éric

doi:10.1002/inst.12274

Cited by 3 publications

(4 citation statements)

References 7 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Functions g and h in (MTS-EP 1) are the mathematical expression of constraints of the problem, issued from specification, system category, and company's system experience from past projects. The flow in Figure 2 matches the representations for adoption of MBSE Methodology sketched in [20], and adds a constraint that is not underlined in Wu's publications, which is the end of the process, when allowed budget or schedule for system conception ends. This is an application of the principles of [21] on UGV system category: the identification of a Pareto Front where the system scale budget and schedule constraints the concept choices.…”

Section: Theoretical Proposition: Optimization Processmentioning

confidence: 83%

Datasheet: where is requirements engineering gone? A case in Benchmarking Mobile Robotics

Brisacier-Porchon

Hammami

2022

INCOSE International Symp

View full text Add to dashboard Cite

The lifecycle of a system is extended from its early conception to its retirement of service. The lifespan of Unmanned Ground Vehicles (UGVs) can be expected to last over 50 years in the defence market. In this context, the rising complexity of UGV systems imposes engineering steps that would ensure both capabilities of the system and resilience to its future inclusion in a system‐of‐system context. During its operational usage, the UGV is supposed to be manoeuvred for specifically designed purposes following user manual datasheet of the components off‐the‐shelf (COTS) that were integrated. This paper exposes the public user datasheet relevance compared to the system engineering requirements that are the artefacts of system design architecture. The use of connecting COTS user manual to system requirements is discussed, all the more if the systems are to be re‐used in a system production line.

show abstract

Section: Theoretical Proposition: Optimization Processmentioning

confidence: 83%

Datasheet: where is requirements engineering gone? A case in Benchmarking Mobile Robotics

Brisacier-Porchon

Hammami

2022

INCOSE International Symp

View full text Add to dashboard Cite

show abstract

“…Functions g and h in (MTS-EP 1) are the mathematical expression of constraints of the problem, issued from specification, system category, and company's system experience from past projects. The flow in Figure 2 matches the representations for adoption of MBSE Methodology sketched in (Wu et al 2019), and adds a constraint that is not underlined in Wu's publications, which is the end of the process, when allowed budget or schedule for system conception ends. This is an application of the principles of (Wheaton and Madni 2018) on UGV system category: the identification of a Pareto Front where the system scale budget and schedule constraints the concept choices.…”

Section: Theoretical Proposition: Optimization Processmentioning

confidence: 83%

Inconsistent and Incomplete Datasheet: The case for systematic use of requirement engineering

Brisacier-Porchon

Hammami

2022

INCOSE International Symp

View full text Add to dashboard Cite

The lifecycle of a system is extended from its early conception to its retirement of service. The lifespan of Unmanned Ground Vehicles (UGVs) can be expected to last over 50 years in the defense market. In this context, the rising complexity of UGV systems imposes engineering steps that would ensure both capabilities of the system and resilience to its future inclusion in a system‐of‐system context. During its operational usage, the UGV is supposed to be maneuvered for specifically designed purposes following user manual datasheet of the components off‐the‐shelf (COTS) that were integrated. This paper exposes the public user datasheet relevance compared to the system engineering requirements that are the artifacts of system design architecture. The use of connecting COTS user manual to system requirements is discussed, all the more if the systems are to be re‐used in a system production line. This article is intended to explore system of system conception methods for future robotized battlefield.

show abstract

“…Functions g and h in (MTS-EP 1) are the mathematical expression of constraints of the problem, issued from specification, system category, and company's system experience from past projects. The flow in Figure 2 matches the representations for adoption of MBSE methodology sketched in Wu et al (2019) and adds a constraint that is not underlined in Wu's publications, which is the end of the process, when allowed budget or schedule for system conception ends. This is an application of the principles of Wheaton and Madni (2018) on UGV system category: the identification of a Pareto front where the system scale budget and schedule constrains the concept choices.…”

Section: Theoretical Proposition: Optimization Processmentioning

confidence: 83%

“…Figure 2 : System specification flow proposition inspired of (Wu et al 2019) In this article, x is instantiated by the UGV as it was designed and integrated. We want to put the UGV to a test and evaluate its Quality as a mule system, and evaluate the quality of its specification.…”

Section: Theoretical Proposition: Optimization Processmentioning

confidence: 99%

Inconsistent and Incomplete Datasheet: The Case for Systematic Use of Requirement Engineering

Brisacier-Porchon¹,

Hammami²

2023

INSIGHT

View full text Add to dashboard Cite

The lifecycle of a system is extended from its early conception to its retirement of service. The lifespan of unmanned ground vehicles (UGVs) can be expected to last over 50 years in the defense market. In this context, the rising complexity of UGV systems imposes engineering steps that would ensure both capabilities of the system and resilience to its future inclusion in a system‐of system context. During its operational usage, the UGV is supposed to be maneuvered for specifically designed purposes following user manual datasheet of the components off‐the‐shelf (COTS) that were integrated. This paper exposes the public user datasheet relevance compared to the system engineering requirements that are the artifacts of system design architecture. The use of connecting COTS user manual to system requirements is discussed, all the more if the systems are to be re‐used in a system production line. This article is intended to explore system of system conception methods for future robotized battlefield.

show abstract

Towards a Maturity Assessment Scale for the Systems Engineering Assets Valorization to Facilitate Model‐Based Systems Engineering Adoption

Cited by 3 publications

References 7 publications

Datasheet: where is requirements engineering gone? A case in Benchmarking Mobile Robotics

Datasheet: where is requirements engineering gone? A case in Benchmarking Mobile Robotics

Inconsistent and Incomplete Datasheet: The case for systematic use of requirement engineering

Inconsistent and Incomplete Datasheet: The Case for Systematic Use of Requirement Engineering

Contact Info

Product

Resources

About