Stepwise refinement of sequence diagrams with soft real-time constraints

Abstract

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.

Design Decisions in the Development of a Graphical Language for Risk-Driven Security Testing

“…To summarize, a formal semantics would be beneficial and we hope to provide this in the future, for example, based on STAIRS [7] or probabilistic STAIRS [24] for sequence diagrams. Formalizing the natural-language expressions would probably alienate the CORAL approach from its intended users, namely security testers.…”

Uncertainty representation in software models: a survey

“…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.…”

Development of digitalised maintenance – a concept

“…This is done in such a way that these tasks collectively preserve the system's original objective. If a refined task remains abstract, then the refinement process continues until a level at which the subtasks are implementable (Abbott, 1987; Wooldridge, 1997; Refsdal et al , 2015). This approach has several advantages, including: (1) it provides a foundation for a separation of concerns (i.e.…”