Abstract not found

However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works, must be obtained from the IEEE.

Abstract not found

Abstract not found

data types, modules, packages; F.3.1 [Logics and Meanings of Programs] Specifying and Verifying and Reasoning about Programs --- logics of programs, pre- and post-conditions, specification techniques; c fl David M. Egle, 1995. Copies may be made for any educational purpose whatever, provided this copyright notice appears on the copy. This work was supported in part by NSF Grant number CCR-9503168. Department of Computer Science 226 Atanasoff Hall Iowa Sate University Ames, Iowa 50011-1040, USA Evaluating Larch/C++ as a Specification Language: A Case Study Using the Microsoft Foundation Class Library David M. Egle Department of Computer Science, Atanasoff Hall Iowa State University, Ames, Iowa 50014 USA egle@cs.iastate.edu July 19, 1995 Abstract This paper attempts to evaluate Larch/C++, a formal specification language, as a means of more unambiguously documenting the interface specifications of C++ class libraries. In particular, the Microsoft Foundation Class Library is examined...

Abstract — Web services are emerging as a key infrastructure for providing inter-operation between applications and systems and for providing support for the deployment of e-commerce business processes. One important issue for ensuring the growth of Web services is having ways of describing the available Web services in a precise way. One possible step toward providing semantic information for Web services is through the use of formal contract specification—that is, using pre/post-conditions. We present a number of ways in which pre/post-conditions could be introduced into Web services descriptions, for specification as well as dynamic verification purpose. The use of pre/post-conditions, however, is not sufficient to describe the semantic of a group of related operations, for example, to describe the legal sequences in which these operations can/should be used. Although business process description languages like BPEL4WS or WSCI can express such descriptions, these are procedural descriptions, not necessarily appropriate for specification purpose. We present one possible way in which such descriptions could be provided for Web services, using path expressions that can show the order in which the various operations of a Web service can and should be invoked. Static and dynamic uses of these protocol specifications are then described. I.

Abstract not found