Model-Driven User Requirements Specification using SysML

Soares, Michel S.; Vrancken, Jos

doi:10.4304/jsw.3.6.57-68

Cited by 57 publications

(36 citation statements)

References 27 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…This facilitates the application of our approach to existing approaches for requirements modeling based on EMF. OMG SysML [74,80] is an example language that defines requirements modeling constructs. Requirements relations defined in SysML are either already present in our metamodel or can be defined as specializations.…”

Section: Discussion Of the Approachmentioning

confidence: 99%

See 1 more Smart Citation

Change impact analysis for requirements: A metamodeling approach

Göknil

Kurtev²,

Berg

et al. 2014

Information and Software Technology

View full text Add to dashboard Cite

a b s t r a c tContext: Following the evolution of the business needs, the requirements of software systems change continuously and new requirements emerge frequently. Requirements documents are often textual artifacts with structure not explicitly given. When a change in a requirements document is introduced, the requirements engineer may have to manually analyze all the requirements for a single change. This may result in neglecting the actual impact of a change. Consequently, the cost of implementing a change may become several times higher than expected. Objective: In this paper, we aim at improving change impact analysis in requirements by using formal semantics of requirements relations and requirements change types. Method: In our previous work we present a requirements metamodel with commonly used requirements relation types and their semantics formalized in first-order logic. In this paper the classification of requirements changes based on structure of a textual requirement is provided with formal semantics. The formalization of requirements relations and changes is used for propagating proposed changes and consistency checking of proposed changes in requirements models. The tool support for change impact analysis in requirements models is an extension of our Tool for Requirements Inferencing and Consistency Checking (TRIC). Results: The described approach for change impact analysis helps in the elimination of some false positive impacts in change propagation, and enables consistency checking of changes. Conclusion: We illustrate our approach in an example which shows that the formal semantics of requirements relations and change classification enables change alternatives to be proposed semi-automatically, the reduction of some false positive impacts and contradicting changes in requirements to be determined.

show abstract

Section: Discussion Of the Approachmentioning

confidence: 99%

“…SysML [74,80] uses the UML profiling mechanism to provide modeling constructs that represent text-based requirements and relate them to other modeling elements. The relation types for requirements in SysML are derive, copy, and contain.…”

Section: Requirements Metamodelingmentioning

confidence: 99%

Change impact analysis for requirements: A metamodeling approach

Göknil

Kurtev²,

Berg

et al. 2014

Information and Software Technology

View full text Add to dashboard Cite

show abstract

“…The details about the requirements metamodel, the semantics and the tool support are reported in [3]. In this work we use the requirements metamodel as a core metamodel that is specialized for multiple requirements modeling approaches such as Product-line [23] and SysML [25]. Mainly, the requirements relations in the metamodel are specialized to support relations in these approaches.…”

Section: Introductionmentioning

confidence: 99%

A metamodeling approach for reasoning on multiple requirements models

Göknil¹,

Kurtev²,

Millo³

2013

2013 17th IEEE International Enterprise Distributed Object Computing Conference

View full text Add to dashboard Cite

Abstract-The complex software development projects of today may require developers to use multiple requirements engineering approaches. Different teams may have to use different requirements modeling formalisms to express requirements related to their assigned parts of a given project. This situation poses difficulties in achieving interoperability and integration of requirements models for the purpose of reasoning on the overall system requirements. It is challenging to compose distributed models expressed in different notations and to reason on the composed models. In this paper we present a metamodeling approach which allows reasoning about requirements and their relations on the whole/composed models expressed in different requirements modeling approaches. In a previous work we expressed the structure of requirements documents as a requirements metamodel in which the most important elements are requirements relations and their types. The semantics of these elements is given in First Order Logic (FOL) and allows two activities: inferring new relations from the initial set of relations and checking consistency of relations. In this work we use the requirements metamodel as a core metamodel to be specialized for different requirements modeling approaches and notations such as Product-line and SysML. Mainly, the requirements relations in the metamodel are specialized to support relations in different requirements modeling approaches. The specialization allows using the same semantics and reasoning mechanism of the core metamodel for multiple requirements modeling approaches. To illustrate the approach we use an example from automotive domain expressed with two modeling approaches: product-line requirements models and SysML for system requirements.

show abstract

“…SysML [38,44] uses the UML profiling mechanism to provide modeling constructs that represent text-based requirements and relate them to other modeling elements. The relation types for requirements in SysML are derive, copy, and contain.…”

Section: Requirements Metamodelingmentioning

confidence: 99%

Semantics of trace relations in requirements models for consistency checking and inferencing

et al. 2009

View full text Add to dashboard Cite

Requirements traceability is the ability to relate requirements back to stakeholders and forward to corresponding design artifacts, code, and test cases. Although considerable research has been devoted to relating requirements in both forward and backward directions, less attention has been paid to relating requirements with other requirements. Relations between requirements influence a number of activities during software development such as consistency checking and change management. In most approaches and tools, there is a lack of precise definition of requirements relations. In this respect, deficient results may be produced. In this paper, we aim at formal definitions of the relation types in order to enable reasoning about requirements relations. We give a requirements metamodel with commonly used relation types. The semantics of the relations is provided with a formalization in first-order logic. We use the formalization for consistency checking of relations and for inferring new relations. A tool has been built to support both reasoning activities. We illustrate our approach in an example which shows that the formal semantics of relation types enables new relations to be inferred and contradicting relations in requirements documents to be determined.

show abstract

Model-Driven User Requirements Specification using SysML

Cited by 57 publications

References 27 publications

Change impact analysis for requirements: A metamodeling approach

Change impact analysis for requirements: A metamodeling approach

A metamodeling approach for reasoning on multiple requirements models

Semantics of trace relations in requirements models for consistency checking and inferencing

Contact Info

Product

Resources

About