A modal process logic

Larsen, Kim Guldstrand; Thomsen, Bent

doi:10.1109/lics.1988.5119

Cited by 293 publications

(306 citation statements)

References 2 publications

Supporting

Mentioning

303

Contrasting

Unclassified

Order By: Relevance

“…Following [6], we enrich modal specifications [18,16,3] with marked states in order to model states to be reached. For instance, if a designer specifies a service, this enables to represent session terminations.…”

Section: Marked Modal Specificationsmentioning

confidence: 99%

“…At this point, the reader may wonder why must-saturation, consistency and attractability are not fully part of the definition of marked modal specification (as it is the case for the consistency requirement in the original papers on unmarked modal specifications [18,16]). The reason for this is because, in what follows, we propose composition operators on marked modal specifications and it is easier to define these constructions without trying to preserve these different requirements.…”

Section: Definition 10 (Reduction Operation) Given a Marked Modal Spementioning

confidence: 99%

“…Now, what specification formalism capturing some behavioral aspects of components is convenient for interface-based design? Modal specifications [18,16,3] are widely acknowledged as a suitable proposal [14,22,23]. Basically, they consist in labeling interface transitions with modalities, either must if the transition has to be enabled in any refinement, or may if the transition is allowed.…”

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Ensuring Reachability by Design

Caillaud

Raclet

2012

Theoretical Aspects of Computing – ICTAC 2012

View full text Add to dashboard Cite

Modular design aims at decomposing systems as a set of distinct components that can be independently developed and then assembled all together. Interfaces are then attached to components; they abstract implementation details while exposing to the environment relevant information about cross-component interactions. Whereas state-of-the-art on interfaces essentially consider independent implementability of safety properties, we consider in this paper reachability properties, which are in general not compositional. The approach we advocate consists in controlling the design flow of components, that is, the evolution of their interfaces through combinations and refinements, in order to ensure a reachability property by construction. Modal specifications are widely acknowledged as a suitable specification formalism for interfacebased design. In order to obtain the required expressivity, we extend them with marked states to model states to be reached. We then develop an algebra with both logical and structural composition operators ensuring reachability properties by design.

show abstract

Section: Marked Modal Specificationsmentioning

confidence: 99%

Section: Definition 10 (Reduction Operation) Given a Marked Modal Spementioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Ensuring Reachability by Design

Caillaud

Raclet

2012

Theoretical Aspects of Computing – ICTAC 2012

View full text Add to dashboard Cite

show abstract

“…To overcome the limitation pointed out earlier of using LTSs as modelling framework for product families, Modal Transition Systems (MTSs) [26] and several variants have been proposed to capture variability in product family specifications [1,16,17,19,25,33]. In an MTS, transitions are either possible (may) or required (must ), corresponding to the notion of optional or mandatory features in product families.…”

Section: Modal Transition Systemsmentioning

confidence: 99%

“…Many years after their introduction in [26], Modal Transition Systems (MTSs) and several variants have been proposed as a formal model for defining product families [1,16,17,19,25,33]. An MTS is a Labelled Transition System (LTS) with a distinction among so-called may and must transitions, which can be seen as optional or mandatory for the products of the family.…”

Section: Introductionmentioning

confidence: 99%

A Logical Framework to Deal with Variability

Asirelli

Beek

Gnesi

2010

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Abstract. We present a logical framework that is able to deal with variability in product family descriptions. The temporal logic MHML is based on the classical Hennessy-Milner logic with Until and we interpret it over Modal Transition Systems (MTSs). MTSs extend the classical notion of Labelled Transition Systems by distinguishing possible (may) and required (must) transitions: these two types of transitions are useful to describe variability in behavioural descriptions of product families. This leads to a novel deontic interpretation of the classical modal and temporal operators, which allows the expression of both constraints over the products of a family and constraints over their behaviour in a single logical framework. Finally, we sketch model-checking algorithms to verify MHML formulae as well as a way to derive correct products from a product family description.

show abstract

Of software and change

Ghezzi

2017

J Softw Evol Proc

View full text Add to dashboard Cite

Change has been recognized as the distinguishing feature that makes software different from any other human-produced artifacts. Initial reflections on the urgent and unavoidable need to master change date back to the 1970s. However, despite the continuous progress that characterized software technology since, in practice, software change is still often handled as an afterthought, in an ad hoc and unprincipled manner. Agile development methods have been proposed and are now widely adopted to accommodate change during development. Recent extensions to also include operation-known as DevOps-are increasingly and successfully adopted by industry. Still, principled and rigorous foundations that can be taught, practiced, and replicated systematically are lacking.This paper argues that change has to become a first-class concept and that the development tools used by engineers and the runtime environment supporting software execution should be structured in a way that naturally accommodates change. It also provides a perspective along which several research approaches that were investigated by the community in the past decade might be integrated and extended to make this vision become true.Two main change categories are identified-evolution and adaptation-along with the forces that drive them. The paper discusses when and how the developed software can be designed in a way that it can self-adapt. It also discusses how the software itself can cooperate with humans in-the-loop to help them in their design and development efforts. Finally, it outlines a roadmap of future work needed to progress in the direction of supporting and automating software change that would lead to dependable adaptation and evolution.

show abstract

A modal process logic

Cited by 293 publications

References 2 publications

Ensuring Reachability by Design

Ensuring Reachability by Design

A Logical Framework to Deal with Variability

Of software and change

Contact Info

Product

Resources

About