Model-Based System Architecting and Decision-Making

Menshenin, Yaroslav; Mordecai, Yaniv; Crawley, Edward F.; Cameron, Bruce

doi:10.1007/978-3-030-27486-3_17-1

Cited by 6 publications

(3 citation statements)

References 28 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Every system or product has an architecture which defines fundamental relationships between and within its elements during the high-level design phase. The system architecture is defined iteratively, in a series of decision-making activities [32] in which stakeholders, system architects, project managers and designers play a crucial and integrative role. Focusing on the upper-left side of the V-Model, the architecture includes feasibility study/concept exploration, concept of operations, system requirements, and high-level design.…”

Section: System Architecture Definitionmentioning

confidence: 99%

MBSE-PLM Integration: Initiatives and Future Outlook

Gerhard

Cordero

Vingerhoeds

et al. 2023

IFIP Advances in Information and Communication Technology

Self Cite

View full text Add to dashboard Cite

show abstract

Section: System Architecture Definitionmentioning

confidence: 99%

MBSE-PLM Integration: Initiatives and Future Outlook

Gerhard

Cordero

Vingerhoeds

et al. 2023

IFIP Advances in Information and Communication Technology

Self Cite

View full text Add to dashboard Cite

show abstract

“…CAMBRE is integrated into conceptual modeling, which allows for continued discussion, elaboration, and solution design to realize the requirements, as part of the same modeland the two are integrated, rather than detached. CAMBRE follows conceptual architecture theory described in [28], a derived concept representation framework [29], and a more rigorous model-based system architecting framework [30]. It consists of elaborating the conceptual architecture in five domains: a) stakeholder needs, b) solutionneutral domain, c) solution-specific domain, d) integrated concept domain, and e) operations domain.…”

Section: Context-aware Model-based Requirements Specification (Cambre)mentioning

confidence: 99%

“…According to [29,30] needs are defined in the Stakeholders domain and they are separate from requirements. Requirements are defined in the solution-neutral domain and solutions are defined in the solution-specific domain.…”

Section: Context-aware Model-based Requirements Specification (Cambre)mentioning

confidence: 99%

Towards Context-Awareness in Model-Based Requirements Engineering

Mordecai

Crawley

2021

2021 IEEE International Systems Conference (SysCon)

Self Cite

View full text Add to dashboard Cite

Evolutionary system development and capability deployment are becoming common even in aerospace and defense. As systems evolve, the need to reach significant understanding of the existing architecture is critical for good requirements specification, due to the growing dependency of the requirements on assets in the current architecture. At present, requirement specifications typically do not clearly separate the baseline, or context, from the necessary delta, or prospect. The context informs the prospect and grounds it in the given architecture. The prospect specifies what the requirement owner needs, requires, or expects the system to be or do that is not already in the baseline. We propose a Context-Aware Model-Based Requirements Engineering (CAMBRE) method in which the context of a requirement is modularly composed with its prospect, such that the requirement text is specified in a context-aware manner. We distill those parts of a requirement that are designated for development from those that constitute the background. This approach is acute for complex, evolving, interdependent, or adaptive systems, in which system properties mostly extend or enhance the existing architecture. We implement CAMBRE with Object-Process Methodology (OPM), and demonstrate our approach on the evolutionary extension of a missile defense system with drone interception capabilities to support border protection efforts.

show abstract