A first attempt to combine SysML requirements diagrams and B

Laleau, Régine; Semmak, Farida; Matoussi, Abderrahman; Petit, Dorian; Hammad, Ahmed; Tatibouët, Bruno

doi:10.1007/s11334-009-0119-y

Cited by 57 publications

(30 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…There are already some works done for the mapping between SysML/Kaos and B in this regard. In [29], a method is defined for bridging the gap between the requirements analysis level (Extended SysML) and the formal specification level (B). This method derives the architecture of B specifications from SysML goal hierarchies.…”

Section: Discussionmentioning

confidence: 99%

“…SysML/Kaos is inpired from the work of [16] and [21]. The SysML/Kaos model allows both FRs [29] and NFRs [25] to be modeled. Figure 4 shows the extended meta-model of SysML/Kaos [25]; non-functional concepts are represented as yellow boxes (bottom), the gray boxes (top) represent the SysML concepts.…”

Section: Why Sysml/kaos?mentioning

confidence: 99%

“…In [29], the authors propose an extension to SysML with concepts from the goal model of the Kaos method (SysML/Kaos) with rules to derive a formal B [1] specification from this goal model. The B formal method is a complete method that supports a large segment of the software development life cycle: specification, refinement and implementation.…”

Section: Properties Verification Of Sasmentioning

confidence: 99%

See 2 more Smart Citations

Modeling and verification of Functional and Non-Functional Requirements of ambient Self-Adaptive Systems

Ahmad

Belloir

Bruel

2015

Journal of Systems and Software

View full text Add to dashboard Cite

Self-Adaptive Systems modify their behavior at run-time in response to changing environmental conditions. For these systems, Non-Functional Requirements play an important role, and one has to identify as early as possible the requirements that are adaptable. We propose an integrated approach for modeling and verifying the requirements of Self-Adaptive Systems using Model Driven Engineering techniques. For this, we use Relax, which is a Requirements Engineering language which introduces flexibility in Non-Functional Requirements. We then use the concepts of Goal-Oriented Requirements Engineering for eliciting and modeling the requirements of Self-Adaptive Systems. For properties verification, we use OMEGA2/IFx profile and toolset. We illustrate our proposed approach by applying it on an academic case study.

show abstract

Section: Discussionmentioning

confidence: 99%

Section: Why Sysml/kaos?mentioning

confidence: 99%

Section: Properties Verification Of Sasmentioning

confidence: 99%

See 1 more Smart Citation

Modeling and verification of Functional and Non-Functional Requirements of ambient Self-Adaptive Systems

Ahmad

Belloir

Bruel

2015

Journal of Systems and Software

View full text Add to dashboard Cite

show abstract

“…In the framework of the TACOS project, more concrete B specifications of the location component have been independently proposed in [2]: an enhanced realistic pure B model of the vehicle (with focus on the location problem) was derived from the requirements specified using the KAOS method [5].…”

Section: Motivating Case Studymentioning

confidence: 99%

“…In the context of the TACOS project, we modelled a multi-agent system of a convoy [1] while a complex B model of a location component was also independently designed [2]. Integrating the latter into the former appears to be problematic because the resulting assembly risks breaking the consistency of the whole vehicle component, as state sharing is involved.…”

Section: Introductionmentioning

confidence: 99%

Relaxing B Sharing Restrictions within CSP||B

Lanoix

Kouchnarenko

Colin³

et al. 2012

Software Composition

View full text Add to dashboard Cite

Abstract. This paper addresses the issue of state sharing in CSP B specifications: B machines controlled by various CSP parts are supposed not to refer to, share or modify the same state space. However, some kinds of B state sharing can be allowed without creating inconsistencies in CSP B specifications. To achieve this, we present an approach where inconsistencies in state sharing can be identified by translating the CSP controllers to B specifications and then using a more refined consistency checking process.

show abstract

Integrated product‐service analysis using SysML requirement diagrams

Durugbo

2012

Systems Engineering

View full text Add to dashboard Cite

During the design of integrated products and services, such as in a product-service system (PSS), an analysis of specific customer needs and the requirements to fulfil them is an important activity needed to determine value propositions based on the function, use, and result of products. Requirements modeling using the OMG Systems Modeling Language (OMG SysML TM ) offers a model-based systems engineering approach to documenting the functionality, performance, and interfacing of systems. However, to use modeling languages, there is a need to understand how the language meets the needs of the modeled system or domain. Following an initial review and evaluation of attributes of PSSs and existing approaches to modeling a PSS, this article analyzes the SysML requirements diagrams-as a technique for analyzing PSS requirements. SysML was compared against existing approaches to PSS modeling using the identified PSS attributes. Case scenarios of PSSs in the automotive industry were also applied to evaluate the use of SysML requirement diagrams. The article concludes by discussing implications of SysML for PSS researchers and managers.

show abstract

A first attempt to combine SysML requirements diagrams and B

Cited by 57 publications

References 20 publications

Modeling and verification of Functional and Non-Functional Requirements of ambient Self-Adaptive Systems

Modeling and verification of Functional and Non-Functional Requirements of ambient Self-Adaptive Systems

Relaxing B Sharing Restrictions within CSP||B

Integrated product‐service analysis using SysML requirement diagrams

Contact Info

Product

Resources

About