Formal Specification Level

Soeken, Mathias; Drechsler, Rolf

doi:10.1007/978-3-319-08699-6

Cited by 11 publications

(2 citation statements)

References 51 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Rather than just specifying what the system-to-be does, we have to specify "what" system we want to obtain [17], meaning an abstract model of the system induced by the specifications. Such a model implements an integrated behavior by conditioning the use cases and tracks their effect on the evolution of the system state.…”

Section: Contextmentioning

confidence: 99%

Modeling and verification method for an early evaluation of systems of systems interactions

Baduel

Ober

Bruel

2020

Proceedings of the 35th Annual ACM Symposium on Applied Computing

View full text Add to dashboard Cite

This paper presents the results achieved while pursuing the verification and validation of a train system behavior at the first steps of development in an industrial context. At this stage, and at least from the industrial point of view, the train can be considered as a System of Systems (SoS). A method is proposed, supported by preliminary results through the definition and verification of constrained states and preconditions to use cases, as well as a structure for the behavior.

show abstract

Section: Contextmentioning

confidence: 99%

Modeling and verification method for an early evaluation of systems of systems interactions

Baduel

Ober

Bruel

2020

Proceedings of the 35th Annual ACM Symposium on Applied Computing

View full text Add to dashboard Cite

show abstract

“…Requirements expressed in natural language are ambiguous and the ones expressed in lower levels like electronic system level (ESL) cannot deal with design complexity. Intermediate levels like the Formal Specification Level (FSL) [1] have been proposed to fill this gap with models that are both close enough to requirements engineer concerns, and formal enough to allow further phases of automatic or semiautomatic generation and verification. This paper contributes to this effort at FSL.…”

Section: Introductionmentioning

confidence: 99%

Natural interpretation of UML/MARTE diagrams for system requirements specification

Khan

Mallet

Rashid

2016

2016 11th IEEE Symposium on Industrial Embedded Systems (SIES)

View full text Add to dashboard Cite

To verify embedded systems early in the design stages, we need formal ways to requirements specification which can be as close as possible to natural language interpretation, away from the lower ESL/RTL levels. This paper proposes to contribute to the FSL (Formal Specification Level) by specifying natural language requirements graphically in the form of temporal patterns. Standard modeling artifacts like UML and MARTE are used to provide formal semantics of these graphical models allowing to eliminate ambiguity in specifications and automatic design verification at different abstraction levels using these patterns.

show abstract

A Cognitive Journey for Requirements Engineering

Feldman

Broodney

2016

INCOSE International Symp

View full text Add to dashboard Cite

The classical systems engineering practice is mostly process centric, but with the recent advances in Information Technologies, we have started to engage in model‐based and other software‐supported activities that make us more efficient and our products better. The subject of this paper is a pursuit of further improvements in the software tools supporting the systems engineers, this time an attempt to transform the regular textual requirements into computer‐readable artifacts that will enable software tools to better analyze a requirement set and to automate cross‐lifecycle exchange of information leading to increased automation and higher quality. The paper starts by describing an experiment targeted at requirements formalization, continues with the insights gained from the experiment, and finishes with the insights that the authors have reached on a reasonable and incremental roadmap to a fully synergetic interaction between Requirements Engineers and their supporting tools.

show abstract

Formal Specification Level

Cited by 11 publications

References 51 publications

Modeling and verification method for an early evaluation of systems of systems interactions

Modeling and verification method for an early evaluation of systems of systems interactions

Natural interpretation of UML/MARTE diagrams for system requirements specification

A Cognitive Journey for Requirements Engineering

Contact Info

Product

Resources

About