10.1.1 A Commonsense‐Driven Architecture Framework. Part 1: A Car Manufacturer's (naïve) Take on MBSE

Góngora, Hugo G. Chalé; Dauron, Alain; Gaudré, Thierry

doi:10.1002/j.2334-5837.2012.tb01412.x

Cited by 6 publications

(8 citation statements)

References 8 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…• Broader adoption of SE modeling tools [13] -design engineers of all disciplines need a basic understanding of an MBSE approach in order to fully utilize the information generated by systems engineers.…”

Section: Key Findings From Case Studies Without Metricsmentioning

confidence: 99%

Systematic Literature Review: How is Model-Based Systems Engineering Justified?

Carroll¹,

Malins²

2016

View full text Add to dashboard Cite

The genesis for this systematic literature review was to search for industry case studies that could inform a decision of whether or not to support the change process, investment, training, and tools needed to implement an MBSE approach across the engineering enterprise. The question asked was, how the change from a document-based systems engineering approach (DBSE) to a modelbased systems engineering approach (MBSE) is justified? The methodology employed for this systematic literature review was to conduct a document search of electronically published case studies by authors from the defense, space, and complex systems product engineering industries. The 67 case studies without metrics mainly attributed success to completeness, consistency, and communication of requirements. The 21 case studies with metrics on cost and schedule primarily attributed success to the ability of an MBSE approach to improve defect prevention strategies. The primary conclusion is that there is a significant advantage to project performance by applying an MBSE approach. An MBSE approach made the engineering processes on a complex system development effort more efficient by improving requirements completeness, consistency, and communication. These were seen in engineering processes involved in requirements management, concept exploration, design reuse, test and qualification, Verification and Validation, and margins analyses. An MBSE approach was most effective at improving defect prevention strategies. The approach was found to enhance the capability to find defects early in the system development life cycle (SDLC), when they could be fixed with less impact and prevented rework in later phases, thus mitigating risks to cost, schedule, and mission. However, if a program only employed an MBSE approach for requirements management, advantages from finding defects early could not be leveraged in later phases, where the savings in cost and schedule from rework prevention is realized. Significant performance success was achieved when the systems engineer (SE) held a leadership role over engineering processes. A number of the case studies addressed a general lack of skilled MBSE engineers as a major hindrance to implementing an MBSE approach successfully.

show abstract

Section: Key Findings From Case Studies Without Metricsmentioning

confidence: 99%

Systematic Literature Review: How is Model-Based Systems Engineering Justified?

Carroll¹,

Malins²

2016

View full text Add to dashboard Cite

show abstract

“…A short summary presenting the classification of these techniques is presented in table 1, which do not take into account aspect oriented modeling for variability, as we considered this to be a software specific technique. Our aim is to embed variability concepts in SysML models, while providing [16], Gomma and Weber, Quality Aware OVM [19], COVAMOF [23], VSL [3] UML integration of OVM: Halmans and Pohl [12]; von der Maßen and Lichter [14] Constraint Based Sequoia (Tessier et al) [26], Feature Modelling Constraint Language (FMCL) [11] Salinesi et al [22], Streitferdt et al [24] Table 1 Classification of variability modelling techniques compatibility to the company "documentary language" and support for our MBSE framework [5].…”

Section: Related Workmentioning

confidence: 99%

“…However, we need to adapt it's functionalities in respect to the specific MBSE context at Renault. Variability concepts were defined as a UML profile, that extends current notions present in SysML and in the SysML-R profiles [5]. It is worth pointing out, that variants are implemented as stereotypes on use-cases, which was also proposed by Halmans et al [12], and by von der Maßen and Lichter [14].…”

Section: Research Approach and Requirements For The Description Of Varimentioning

confidence: 99%

Capturing Variability in Model Based Systems Engineering

Dumitrescu

Tessier²,

Salinesi³

et al. 2014

Complex Systems Design &Amp; Management

Self Cite

View full text Add to dashboard Cite

Automotive model-based systems engineering needs to be adapted to the industry specific needs, in particular by implementing appropriate means of representing and operating with variability. We rely on existing modeling techniques as an opportunity to provide a description of variability adapted to a systems engineering model. However, we also need to take into account requirements related to backwards compatibility with current practices, given the industry experience in mass customization. We propose to adopt the product line paradigm in model-based systems engineering by extending the orthogonal variability model, and adapting it to our specific needs. This brings us to an expression closer to a description of constraints, related to both orthogonal variability, and to SysML system models. We introduce our approach through a discussion on the different aspects that need to be covered for expressing variability in systems engineering. We explore these aspects by observing an automotive case study, and relate them to a list of contextual requirements for variability management.

show abstract

“…In consequence the derivation of the product line needs to be regarded, as proposed by Djebbi [6], as a decision making activity, where the engineer might take into account existing alternatives or develop new assets to reach a completely defined product. Our objective is to allow the user to perform usual SE activities during derivation according to the framework proposed by Chalé [3]. Consequently, we do not provide for now any guidance, but rather focus on rendering the process more flexible.…”

Section: Research Backgroundmentioning

confidence: 99%

Flexible Product Line Derivation Applied to a Model Based Systems Engineering Process

Dumitrescu

Tessier

Salinesi

et al. 2013

Complex Systems Design &Amp; Management

Self Cite

View full text Add to dashboard Cite

HAL is a multidisciplinary open access archive for the deposit and dissemination of scientific research documents, whether they are published or not. The documents may come from teaching and research institutions in France or abroad, or from public or private research centers. L'archive ouverte pluridisciplinaire HAL, est destinée au dépôt et à la diffusion de documents scientifiques de niveau recherche, publiés ou non, émanant des établissements d'enseignement et de recherche français ou étrangers, des laboratoires publics ou privés.

show abstract

10.1.1 A Commonsense‐Driven Architecture Framework. Part 1: A Car Manufacturer's (naïve) Take on MBSE

Cited by 6 publications

References 8 publications

Systematic Literature Review: How is Model-Based Systems Engineering Justified?

Systematic Literature Review: How is Model-Based Systems Engineering Justified?

Capturing Variability in Model Based Systems Engineering

Flexible Product Line Derivation Applied to a Model Based Systems Engineering Process

Contact Info

Product

Resources

About