Relating computer systems to sequence diagrams: the impact of underspecification and inherent nondeterminism

Runde, Ragnhild Kobro; Refsdal, Atle; Stølen, Ketil

doi:10.1007/s00165-011-0192-5

Cited by 6 publications

(6 citation statements)

References 35 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Seventeen papers focus on the representation of this type of uncertainty, in different ways. Seven of them make use of probabilistic state machines [22,38], probabilistic sequence diagrams [36,77,78,82], Markov chains [2], or stochastic temporal logic [15]. Two of them use Fuzzy State Machines [46] or Fuzzy DEVS [37] to represent the stochastic behavior of the system objects.…”

Section: Types Of Uncertainty Addressedmentioning

confidence: 99%

Uncertainty representation in software models: a survey

et al. 2021

View full text Add to dashboard Cite

This paper provides a comprehensive overview and analysis of research work on how uncertainty is currently represented in software models. The survey presents the definitions and current research status of different proposals for addressing uncertainty modeling, and introduces a classification framework that allows to compare and classify existing proposals, analyse their current status and identify new trends. In addition, we discuss possible future research directions, opportunities and challenges.A fundamental characteristic of software models is their ability to represent the relevant characteristics of the system under study, at the appropriate level of abstraction. Software models were initially conceived to design and develop general Information Technology (IT) systems, such as financial applications, enterprise databases or component-based systems, and have proven to be excellent artefacts for representing the basic structure and

show abstract

Section: Types Of Uncertainty Addressedmentioning

confidence: 99%

Uncertainty representation in software models: a survey

et al. 2021

View full text Add to dashboard Cite

show abstract

“…Probabilities are not covered, as they are not included in the UML 2.x standard. In [12], we have compared STAIRS and its refinement relations to related work on sequence diagrams, including the most relevant from [18], as well as other similar notations, refinement and nondeterminism. The discussion in this section is therefore restricted to aspects concerning time and probabilities.…”

Section: Sequence Diagrams and Similar Notationsmentioning

confidence: 99%

“…Of all the approaches discussed in [18] and [12], the one most closely related to STAIRS is the trace-based semantics proposed by Cengarle and Knapp in [19]. Based on that approach, [20] develops a semantics for UML 2.0 Interactions with support for (hard) real-time constraints.…”

Section: Sequence Diagrams and Similar Notationsmentioning

confidence: 99%

See 1 more Smart Citation

Stepwise refinement of sequence diagrams with soft real-time constraints

Refsdal

Runde

Stølen

2015

Journal of Computer and System Sciences

Self Cite

View full text Add to dashboard Cite

UML sequence diagrams and similar notations are much used to specify and analyze computer systems and their requirements. Probabilities are often essential, in particular for capturing soft real-time constraints. It is also important to be able to specify systems at different levels of abstraction. Refinement is a means to relate abstract specifications to more concrete specifications in such a way that constraints and analysis results are preserved through the transition. In order to allow soft real-time constraints to be included as an integral part of sequence diagram specifications, this paper presents an approach to extend UML 2.x sequence diagrams to capture probabilistic choice in general and soft real-time constraints in particular. The approach is supported by formal semantics and pragmatic refinement relations with mathematical properties that allow stepwise and modular development of specifications. An example focusing on communication is provided to demonstrate the language and refinement relations.

show abstract

“…STAIRS [HHRS05,RRS13] was designed to provide the UML community with this kind of understanding at a level of abstraction that is easily comprehensible for UML practitioners. STAIRS is inspired by formal methods and refinement theory.…”

Section: Introductionmentioning

confidence: 99%

Mandatory and Potential Choice: Comparing Event-B and STAIRS

Refsdal¹,

Runde²,

Stølen³

2016

From Action Systems to Distributed Systems

View full text Add to dashboard Cite

In order to decide whether a software system fulfills a specification, or whether a detailed specification preserves the properties of a more abstract specification, we need an understanding of what it means for one specification to fulfill another specification. This is particularly important when the specification contains one or more operators for expressing choice. Operators for choice have been studied for more than three decades within the field of formal methods in general, and within methods for action-refinement in particular. As a more recent method within this tradition, in this paper we have chosen to focus on Event-B. Another kind of method is STAIRS, focusing on UML interactions and designed to provide the UML community with an understanding of refinement and fulfillment. To provide the required expressiveness, STAIRS distinguishes between potential and mandatory choice, where only the latter is required to by preserved by refinement. In this paper, we investigate the relationship between the operators for choice in Event-B and STAIRS.

show abstract

Relating computer systems to sequence diagrams: the impact of underspecification and inherent nondeterminism

Cited by 6 publications

References 35 publications

Uncertainty representation in software models: a survey

Uncertainty representation in software models: a survey

Stepwise refinement of sequence diagrams with soft real-time constraints

Mandatory and Potential Choice: Comparing Event-B and STAIRS

Contact Info

Product

Resources

About