2019
DOI: 10.3390/systems7020019
|View full text |Cite
|
Sign up to set email alerts
|

Constructing True Model-Based Requirements in SysML

Abstract: Some authors suggest that transitioning requirements engineering from the traditional statements in natural language with shall clauses to model-based requirements within a Model-Based Systems Engineering (MBSE) environment could improve communication, requirements traceability, and system decomposition, among others. Requirement elements in the Systems Modeling Language (SysML) fail to fulfill this objective, as they are really a textual requirement in natural language as a model element. Current efforts to d… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
36
0
1

Year Published

2019
2019
2024
2024

Publication Types

Select...
9
1

Relationship

3
7

Authors

Journals

citations
Cited by 32 publications
(37 citation statements)
references
References 31 publications
0
36
0
1
Order By: Relevance
“…Although recent work on model-based requirements [81] and value models continues to emphasize the need for mathematical rigor in SE, there is still a lack for a formalism that can enable direct and rigorous representation of stakeholder preferences, facilitate evaluation of consistency in preferences, and enable distributed decision-making in a multi-agent organization. This article moves towards a holistic model-centric approach for preference representation and communication.…”
Section: Discussionmentioning
confidence: 99%
“…Although recent work on model-based requirements [81] and value models continues to emphasize the need for mathematical rigor in SE, there is still a lack for a formalism that can enable direct and rigorous representation of stakeholder preferences, facilitate evaluation of consistency in preferences, and enable distributed decision-making in a multi-agent organization. This article moves towards a holistic model-centric approach for preference representation and communication.…”
Section: Discussionmentioning
confidence: 99%
“…Additionally, the use of SysML can facilitate communication and make design easier between system users, maintenance personnel, and those who may debug, integrate, extend, modify and change the system [46]. SysML is mainly composed of nine types of diagrams: activity diagrams, sequence diagrams, state machine diagrams, use case diagrams, requirement diagrams, block definition diagrams, internal block diagrams, parameter diagrams and package diagrams [47]. The mapping relationship between FFIP and SysML elements is shown in Table 3.…”
Section: Improvement Of Sysml Based On Failure Logic 41 Conversion Methods From Ffip To Sysmlmentioning
confidence: 99%
“…In order to avoid this, innovative approaches are proposed (e.g. [37], [38]), where SysML elements are used to model requirement statements. However, other researchers (e.g.…”
Section: Literature Review On the Definition And Modeling Of Stakeholders Needs And Requirementsmentioning
confidence: 99%