Model-based Requirement Verification : A Case Study

Feng, Liang; Schamai, Wladimir; Rogovchenko, Olena; Sadeghi, Sara; Nyberg, Mattias; Fritzson, Peter

doi:10.3384/ecp12076385

Cited by 15 publications

(14 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Feng Liang [14] proposed a vVDR (Virtual Verification of Designs against Requirements) approach for verifying a system with its requirement. In his research, the system is modeled in Modelica, and requirement verification scenarios are specified in ModelicaML, an UML profile and a language extension for Modelica.…”

Section: Requirements Verificationmentioning

confidence: 99%

Validation and Verification of SYSML Activity Diagrams Using HOARE Logic

Yin¹,

Liu²,

Chen³

2018

IJSEA

View full text Add to dashboard Cite

show abstract

Section: Requirements Verificationmentioning

confidence: 99%

Validation and Verification of SYSML Activity Diagrams Using HOARE Logic

Yin¹,

Liu²,

Chen³

2018

IJSEA

View full text Add to dashboard Cite

show abstract

“…This and relations (24) and (25) imply that B Env E (E) ∩G = ∅. Finally, relation A A ∩G ⊆ B of condition (i) and the fact that A A ⊆ A A and G ⊆ G, as expressed in relations (24) and (25), respectively, imply that A A ∩ G ⊆ B. Relations (24), (25), B Env E (E) ∩ G = ∅ and A A ∩ G ⊆ B imply that conditions (i') and (ii') hold.…”

Section: Theorem 2 Given a Contract (A G X ) And Set Of Variablesmentioning

confidence: 99%

“…An example where this RE principle is manifested in an industrial case study can be found in [24] where ModelicaML [25] is used to specify and verify requirements on a subsystem of a fuel management system where the requirements express the end-to-end functionality of the fuel management system in general. Another example can be found in [26] where SysML [27] is used to specify requirements on an engine knock controller and where the requirements allocated to the controller explicitly refer to parts, such as the piston, which is not a port of the controller but rather a port in its environment.…”

Section: (I N(m I) ∧ Ou T (O C) ∧ N At (M C) R E Q(m C)) For Somentioning

confidence: 99%

Conditions of contracts for separating responsibilities in heterogeneous systems

Westman

Nyberg

2017

Form Methods Syst Des

Self Cite

View full text Add to dashboard Cite

A general, compositional, and component-based contract theory is proposed for modeling and specifying heterogeneous systems, characterized by consisting of parts from different domains, e.g. software, electrical and mechanical. Given a contract consisting of assumptions and a guarantee, clearly separated conditions on a component and its environment are presented where the conditions ensure that the guarantee is fulfilled-a responsibility assigned to the component, given that the environment fulfills the assumptions. The conditions are applicable whenever it cannot be ensured that the sets of ports of components are partitioned into inputs and outputs, and hence fully support scenarios where components, characterized by both causal and acausal models, are to be integrated by solely relying on the information of a contract. An example of such a scenario of industrial relevance is explicitly considered, namely a scenario in a supply chain where the development of a component is outsourced. To facilitate the application of the theory in practice, necessary properties of contracts are also derived to serve as sanity checks of the conditions. Furthermore, based on a graph that represents a structuring of a hierarchy of contracts, sufficient conditions to achieve compositionality are presented.

show abstract

“…An example of when a specification such as the one shown in Fig. 1b is used in an industrial case-study, can be found in [24] where ModelicaML [25] is used to specify and verify requirements on a subsystem of a fuel management system where the requirements express the end-to-end functionality of the fuel management system in general. Another example can be found in [26] where SysML [27] is used to specify requirements on an engine knock controller and where the requirements allocated to the controller explicitly refer to parts, such as e.g.…”

Section: Introductionmentioning

confidence: 99%

Environment-Centric Contracts for Design of Cyber-Physical Systems

Westman

Nyberg

2014

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. A contract splits the responsibilities between a component and its environment into a guarantee that expresses an intended property under the responsibility of the component, given that the environment fulfills the assumptions. Although current contract theories are limited to express contracts over interfaces of components, specifications that are not limited to interfaces are used in practice and are needed in order to properly express safety requirements. A framework is therefore presented, generalizing current contract theory to environment-centric contracts -contracts that are not limited to the interface of components. The framework includes revised definitions of properties of contracts, as well as theorems that specifies exact conditions for when the properties hold. Furthermore, constraints are introduced, limiting the ports over which an environment-centric contract is expressed where the constraints constitute necessary conditions for the guarantee of the contract to hold in an architecture.

show abstract

Model-based Requirement Verification : A Case Study

Cited by 15 publications

References 4 publications

Validation and Verification of SYSML Activity Diagrams Using HOARE Logic

Validation and Verification of SYSML Activity Diagrams Using HOARE Logic

Conditions of contracts for separating responsibilities in heterogeneous systems

Environment-Centric Contracts for Design of Cyber-Physical Systems

Contact Info

Product

Resources

About