2005
DOI: 10.1007/11603009_4
|View full text |Cite
|
Sign up to set email alerts
|

Specification and Refinement of Soft Real-Time Requirements Using Sequence Diagrams

Abstract: Abstract. Soft real-time requirements are often related to communication in distributed systems. Therefore it is interesting to understand how UML sequence diagrams can be used to specify such requirements. We propose a way of integrating soft real-time requirements in sequence diagram specifications by adding probabilities to timed sequence diagrams. Our approach builds on timed STAIRS, which is an approach to the compositional and incremental development of sequence diagrams supporting specification of manda… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
20
0

Year Published

2005
2005
2015
2015

Publication Types

Select...
4
2

Relationship

3
3

Authors

Journals

citations
Cited by 11 publications
(20 citation statements)
references
References 10 publications
0
20
0
Order By: Relevance
“…The simplicity of the specifications has allowed us to properly explain their semantic representations. For more examples related to communication see [HHRS05b], [RHS05c] and [RHS05a]. We firmly believe that STAIRS and probabilistic STAIRS offer a suitable expressiveness for practical specifications, and intend to show this in the future through studies of real-life specifications.…”
Section: Resultsmentioning
confidence: 95%
See 2 more Smart Citations
“…The simplicity of the specifications has allowed us to properly explain their semantic representations. For more examples related to communication see [HHRS05b], [RHS05c] and [RHS05a]. We firmly believe that STAIRS and probabilistic STAIRS offer a suitable expressiveness for practical specifications, and intend to show this in the future through studies of real-life specifications.…”
Section: Resultsmentioning
confidence: 95%
“…Probabilities are equally relevant in this setting, for instance to specify the probability that a message will never be received when sent over an unreliable communication channel. Another example is when specifying soft real-time constraints such as 'the user of the system will receive an answer within 10 seconds at least 90% of the time' (for more details, see [RHS05a]). As this example demonstrates, we are not only interested in assigning exact probabilities to all alternatives specified by an xalt, but also to specify a possible range for the probabilities, i.e.…”
Section: Motivationmentioning
confidence: 99%
See 1 more Smart Citation
“…As p = p ∪ n , it is easy to see that the p-obligation ((p , n ), {1}) (for sendSMS2*) is a narrowing refinement of the p-obligation ((p, ∅), {1}) (for sendSMS1*) according to definition (14).…”
Section: Refinement Relations For Single Interaction Obligations and mentioning
confidence: 99%
“…Intuitively, any finite loop corresponds to a finite number of seq operators, while the semantics of an infinite loop is made up of p-obligations whose traces, when projected on each lifeline, constitute the least upper bound with respect to prefixing of a sequence of traces obtained through any finite number of sequential compositions. The formal definition can be found in [14].…”
Section: Appendix A2 Semantics Of Composition Operatorsmentioning
confidence: 99%