Component and Interface Refinement in Closed-System Specifications

Authors:
Reino Kurki-Suonio
Affiliations:
-
Venue:
FM '99 Proceedings of the Wold Congress on Formal Methods in the Development of Computing Systems-Volume I - Volume I
Year:
1999

Citing 6
Cited 0

Introduction to the ISO specification language LOTOS

Computer Networks and ISDN Systems - Special Issue: Protocol Specification and Testing
Object-oriented specification of reactive systems

ICSE '90 Proceedings of the 12th international conference on Software engineering
The temporal logic of actions

ACM Transactions on Programming Languages and Systems (TOPLAS)
Conjoining specifications

ACM Transactions on Programming Languages and Systems (TOPLAS)
Compositional specification and verification of high-speed transfer protocols

PSTV '94 Proceedings of the fourteenth of a series of annual meetings on Protocol specification, testing and verification XIV
Formalizing design patterns

Proceedings of the 20th international conference on Software engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

A closed-system specification models a system in the context of its assumed environment. A component is then a view on the total system, where unnecessary details of other components and the external environment have been abstracted away. Starting from a crude initial model, details of components can be introduced in separate component refinements, and the resulting views can be synthesized by composition into a detailed model of the total system. In contrast to open systems, also component interfaces can be refined in this process. The original model may therefore have abstract interfaces, whose implementability with the available mechanisms is one of the concerns in component refinements. However, since component refinements may then interfere, conditions are needed for their composability. Such conditions are derived in this paper, and the application of component refinements to interface refinement is investigated.