Patterns in property specifications for finite-state verification

Dwyer,; Avrunin,; Corbett, Elizabeth L.

doi:10.1109/icse.1999.841031

Cited by 292 publications

(699 citation statements)

References 0 publications

Supporting

Mentioning

687

Contrasting

Unclassified

Order By: Relevance

“…The scope can be: Global, Before an event or state, After an event or state, Between two events or states, After one event or state and Until another event or state. For more details about property specification patterns, see [22,23] or [6]. The latter reference is specific for property patterns over events, and provides a way to combine property patterns to guarantee that the generated properties preserve the closure under stuttering property.…”

Section: Examplementioning

confidence: 99%

“…However, checking whether a formula is closed under stuttering is a PSPACE-complete problem. Therefore, we adopt here an approach to obtain closed under stuttering formulas constructively by using property specification patterns [6,22,23]. This has the additional advantage of aiding the user in the formulation of the desired properties, because expressing correct non trivial properties using temporal logic is usually a complex task.…”

Section: Examplementioning

confidence: 99%

“…Basically, in the literature we can identify two complementary approaches used to specify temporal properties about models, one based on events and another based on states [23]. Considering OBGGs, we can view the application of rules as being events and graphs, obtained from the application of rules, as states.…”

Section: Property Specificationmentioning

confidence: 99%

See 2 more Smart Citations

Verifying Object-based Graph Grammars

et al. 2006

View full text Add to dashboard Cite

The development of concurrent and reactive systems is gaining importance since they are well-suited to modern computing platforms, such as the Internet. However, the development of correct concurrent and reactive systems is a non-trivial task. Object-based graph grammar (OBGG) is a visual formal language suitable for the specification of this class of systems. In previous work, a translation from OBGG to PROMELA (the input language of the SPIN model checker) was defined, enabling the verification of OBGG models using SPIN. In this paper we extend this approach in two different This work is partially sponsored by projects IQ-MObile (CNPqBrazil/CNR-Italy) and PLATUS (CNPq). ways: (1) the approach for property specification is improved, enabling to prove properties not only about possible OBGG derivations, but also about the internal state of involved objects; (2) an approach is defined to interpret PROMELA traces as OBGG derivations, generating graphical counter-examples for properties that are not true for a given OBGG model. Another contribution of this paper is (3) the definition of a method for model checking partial systems (isolated objects or a set of objects) using an assume-guarantee approach. A gas station system modeled with OBGGs is used to illustrate the contributions.

show abstract

Section: Examplementioning

confidence: 99%

Section: Examplementioning

confidence: 99%

See 1 more Smart Citation

Verifying Object-based Graph Grammars

et al. 2006

View full text Add to dashboard Cite

show abstract

“…To investigate the potential for domain-independent application of our temporal OCL approach, we have mapped the general property patterns identified by Dwyer et al [14] to corresponding temporal OCL expressions [20]. It turned out that only some minor extensions are necessary to cover all property patterns.…”

Section: Examplementioning

confidence: 99%

Formal semantics of static and temporal state-oriented OCL constraints

Flake

Mueller

2003

Softw Syst Model

View full text Add to dashboard Cite

The textual Object Constraint Language (OCL) is primarily intended to specify restrictions over UML class diagrams, in particular class invariants, operation pre-, and postconditions. Based on several improvements in the definition of the language concepts in last years, a proposal for a new version of OCL has recently been published [43]. That document provides an extensive OCL semantic description that constitutes a tight integration into UML. However, OCL still lacks a semantic integration of UML Statecharts, although it can already be used to refer to states in OCL expressions.This article presents an approach that closes this gap and introduces a formal semantics for such integration through a mathematical model. It also presents the definition of a temporal OCL extension by means of a UML Profile based on the metamodel of the latest OCL proposal. Our OCL extension enables modelers to specify behavioral state-oriented real-time constraints. It provides an intuitive understanding and readability at application level since common OCL syntax and concepts are preserved. A well-defined formal semantics is given through the mapping of temporal OCL expressions to temporal logics formulae.

show abstract

“…However, the use of temporal logics is still limited to users with a good mathematical background because temporal logic formulae are difficult to understand and even more difficult to create. To bridge this gap between practitioners and model checking tools, many authors have proposed property specification patterns [1,14,18,25,26] to guide users in expressing system requirements directly in temporal logic.…”

Section: Introductionmentioning

confidence: 99%

Use Case Maps as a property specification language

2007

View full text Add to dashboard Cite

Although a significant body of research in the area of formal verification and model checking tools of software and hardware systems exists, the acceptance of these tools by industry and end-users is rather limited. Beside the technical problem of state space explosion, one of the main reasons for this limited acceptance is the unfamiliarity of users with the required specification notation. Requirements have to be typically expressed as temporal logic formalisms and notations. Property specification patterns were successfully introduced to bridge this gap between users and model checking tools. They also enable non-experts to write formal specifications that can be used for automatic model checking.In this paper, we propose an abstract high level pattern-based approach to the description of property specifications based on Use Case Maps (UCM). We present a set of commonly used properties with their specifications that are described in terms of occurrence, ordering and temporal scopes of actions. Furthermore, our approach also supports the description of properties with respect to their architectural scope. We provide a mapping of our UCM property specification patterns in terms of CTL, TCTL and Architectural TCTL (ArTCTL), an extension to TCTL, introduced in this research that provides Communicated by Dr. Alessandra Cavarra. temporal logics with architectural scopes. We illustrate the use of our pattern system for requirement specifications of an IP Header compression feature.

show abstract

Patterns in property specifications for finite-state verification

Cited by 292 publications

References 0 publications

Verifying Object-based Graph Grammars

Verifying Object-based Graph Grammars

Formal semantics of static and temporal state-oriented OCL constraints

Use Case Maps as a property specification language

Contact Info

Product

Resources

About