2006
DOI: 10.1016/j.entcs.2005.10.035
|View full text |Cite
|
Sign up to set email alerts
|

Patterns for Timed Property Specifications

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
66
0

Year Published

2011
2011
2024
2024

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 54 publications
(67 citation statements)
references
References 10 publications
1
66
0
Order By: Relevance
“…This includes the patterns identified in [3] and [17], including existence, absence, precedence and response patterns. In our further research, we will investigate such patterns, including patterns for timerelated properties (see [18]). Another direction of our work will be to enable the business architects who are responsible for defining workflow specifications to specify such properties without a deeper knowledge in model checking or temporal logics.…”
Section: Resultsmentioning
confidence: 99%
“…This includes the patterns identified in [3] and [17], including existence, absence, precedence and response patterns. In our further research, we will investigate such patterns, including patterns for timerelated properties (see [18]). Another direction of our work will be to enable the business architects who are responsible for defining workflow specifications to specify such properties without a deeper knowledge in model checking or temporal logics.…”
Section: Resultsmentioning
confidence: 99%
“…Furthermore, for logic-based specification-formalism, the correct definition of QoS proper-ties is supported with specification patterns [39], [49], [48], [68] and structured English grammars [49], [68].Traditionally, the semantics of the PCTL/CSL is defined with a satisfaction relation j¼ over the states S and possible paths Path M ðsÞ that are possible in a state s 2 S of a discrete/continuous time probabilistic model M. For de-tails about the formal semantics the reader is referred to [8], [33], [53]. Normally, a PCTL/CSL formula is evaluated starting from the initial state of the probabilistic model M. However, for convenience, in tools like PRISM any state and also a set of states can be chosen with a filter.…”
Section: Formal Definition Of Qos Requirementsmentioning
confidence: 99%
“…Use cases and process models should be annotated with properties to be checked at run time. We envision these properties to be expressed in Restricted Natural Language (RNL), using some predefined templates based on property specification patterns (such as the systems defined in [13], [21], [6], [17] …”
Section: Design-time Layermentioning
confidence: 99%