Systematic software development using VDM
Systematic software development using VDM
Parallel program design: a foundation
Parallel program design: a foundation
Safety and liveness from a methodological point of view
Information Processing Letters
Specifying Concurrent Program Modules
ACM Transactions on Programming Languages and Systems (TOPLAS)
Scenarios: A Model of Non-Determinate Computation
Proceedings of the International Colloquium on Formalization of Programming Concepts
Functional Specification of Time Sensitive Communicating Systems
Stepwise Refinement of Distributed Systems, Models, Formalisms, Correctness, REX Workshop
ACM Transactions on Software Engineering and Methodology (TOSEM)
Implementing Services by Partial State Machines
SOFSEM '09 Proceedings of the 35th Conference on Current Trends in Theory and Practice of Computer Science
| Hi-index | 0.00 |
The assumption/commitment (also called rely/guarantee) style hasbeen advocated for the specification of interactive components ofdistributed systems. It suggests the structuring of specifications intoassumptions about the behavior of the component‘s environment and intocommitments that are fulfilled by the component, provided the environmentfulfills these assumptions. One of its motivations is to achieve modularity(also called compositionality) for state transition specifications of systemcomponents. Another reason for writing specifications in this format lies inproof rules that refer to this format. We define the assumption/commitmentformats for functional system specifications. In particular, we work out acanonical decomposition of system specifications following theassumption/commitment format into safety and liveness aspects. Wedemonstrate the format of assumption/commitment specifications by a numberof examples. Finally, we discuss the methodological significance of theassumption/commitment format in the stepwise development ofspecifications.