The Experts below are selected from a list of 27873 Experts worldwide ranked by ideXlab platform
Jeanfrancois Mule - One of the best experts on this subject based on the ideXlab platform.
-
extensions to rtsp based on the cablelabs edge resource management Interface Specification ermi
2008Co-Authors: Charles Bergren, Jeanfrancois MuleAbstract:This document provides a description of the RTSP extensions used in the second version of the CableLabs Edge Resource Manager Interface Specification. It is provided to seek comments from the IETF with the intent of following the IETF procedures for protocol extensions and variations. It is a work-in-progress document and future revisions will contain IANA registrations.
-
extensions to rtsp based on the cablelabs edge resource management Interface Specification ermi
2008Co-Authors: Charles Bergren, Jeanfrancois MuleAbstract:This document provides a description of the RTSP extensions used in the second version of the CableLabs Edge Resource Manager Interface Specification. It is provided to seek comments from the IETF with the intent of following the IETF procedures for protocol extensions and variations. It is a work-in-progress document and future revisions will contain IANA registrations.
Gary T Leavens - One of the best experts on this subject based on the ideXlab platform.
-
Behavioral Interface Specification languages
ACM Computing Surveys, 2012Co-Authors: John Hatcliff, Gary T Leavens, K. Rustan M. Leino, Peter Müller, Matthew ParkinsonAbstract:Behavioral Interface Specification languages provide formal code-level annotations, such as preconditions, postconditions, invariants, and assertions that allow programmers to express the intended behavior of program modules. Such Specifications are useful for precisely documenting program behavior, for guiding implementation, and for facilitating agreement between teams of programmers in modular development of software. When used in conjunction with automated analysis and program verification tools, such Specifications can support detection of common code vulnerabilities, capture of light-weight application-specific semantic properties, generation of test cases and test oracles, and full formal program verification. This article surveys behavioral Interface Specification languages with a focus toward automatic program verification and with a view towards aiding the Verified Software Initiative—a fifteen-year, cooperative, international project directed at the scientific challenges of large-scale software verification.
-
preliminary design of jml a behavioral Interface Specification language for java
ACM Sigsoft Software Engineering Notes, 2006Co-Authors: Gary T Leavens, Albert L Baker, Clyde RubyAbstract:JML is a behavioral Interface Specification language tailored to Java(TM). Besides pre- and postconditions, it also allows assertions to be intermixed with Java code; these aid verification and debugging. JML is designed to be used by working software engineers; to do this it follows Eiffel in using Java expressions in assertions. JML combines this idea from Eiffel with the model-based approach to Specifications, typified by VDM and Larch, which results in greater expressiveness. Other expressiveness advantages over Eiffel include quantifiers, Specification-only variables, and frame conditions.This paper discusses the goals of JML, the overall approach, and describes the basic features of the language through examples. It is intended for readers who have some familiarity with both Java and behavioral Specification using pre- and postconditions.
-
enhancing the pre and postcondition technique for more expressive Specifications
Formal Methods, 1999Co-Authors: Gary T Leavens, Albert L BakerAbstract:We describe enhancements to the pre- and postcondition technique that help Specifications convey information more effectively. Some enhancements allow one to specify redundant information that can be used in "debugging" Specifications. For instance, adding examples to a Specification gives redundant information that may aid some readers, and can also be used to help ensure that the Specification says what is intended. Other enhancements allow improvements in frame axioms for object-oriented (OO) procedures, better treatments of exceptions and inheritance, and improved support for incompletely-specified types. Many of these enhancements were invented by other authors, but are not widely known. They have all been integrated into Larch/C++, a Larch-style behavioral Interface Specification language for C++. However, such enhancements could also be used to make other Specification languages more effective tools for communication.
Matthew Parkinson - One of the best experts on this subject based on the ideXlab platform.
-
Behavioral Interface Specification languages
ACM Computing Surveys, 2012Co-Authors: John Hatcliff, Gary T Leavens, K. Rustan M. Leino, Peter Müller, Matthew ParkinsonAbstract:Behavioral Interface Specification languages provide formal code-level annotations, such as preconditions, postconditions, invariants, and assertions that allow programmers to express the intended behavior of program modules. Such Specifications are useful for precisely documenting program behavior, for guiding implementation, and for facilitating agreement between teams of programmers in modular development of software. When used in conjunction with automated analysis and program verification tools, such Specifications can support detection of common code vulnerabilities, capture of light-weight application-specific semantic properties, generation of test cases and test oracles, and full formal program verification. This article surveys behavioral Interface Specification languages with a focus toward automatic program verification and with a view towards aiding the Verified Software Initiative—a fifteen-year, cooperative, international project directed at the scientific challenges of large-scale software verification.
Sergey Rybin - One of the best experts on this subject based on the ideXlab platform.
-
asis for gnat from the prototype to the full implementation
International Conference on Reliable Software Technologies, 1996Co-Authors: Sergey Rybin, Alfred Strohmeier, Alexey Kuchumov, Vasiliy FofanovAbstract:This article is about the implementation of the Ada Semantic Interface Specification (ASIS) for the GNAT Ada 95 compilation system (ASIS-for-GNAT). It discusses implementation problems and their solutions. It explains the interaction of ASIS-for-GNAT with GNAT and its internal data structures. Finally, it describes the current state of ASIS-for-GNAT.
-
asis for gnat goals problems and implementation strategy
ACM Sigada Ada Letters, 1996Co-Authors: Sergey Rybin, Alfred Strohmeier, Eugene ZueffAbstract:This article describes the approach taken to implement the Ada Semantic Interface Specification (ASIS) for the GNAT Ada compiler. The paper discusses the main implementation problems and their solutions. It also describes the current state of the implementation. This is a slightly revised version of the paper published in the proceedings of the Ada-Europe'95 conference.
-
asis for gnat goals problems and implementation strategy
International Conference on Reliable Software Technologies, 1995Co-Authors: Sergey Rybin, Alfred Strohmeier, Eugene ZueffAbstract:This article describes the approach taken to implement the Ada Semantic Interface Specification (ASIS) for the GNAT Ada compiler. The paper discusses the main implementation problems and and their solution. It also describes the current state of the implementation.
Bartosz Belter - One of the best experts on this subject based on the ideXlab platform.
-
design and implementation of an openflow hardware abstraction layer
ACM Special Interest Group on Data Communication, 2014Co-Authors: Damian Parniewicz, Lukasz Ogrodowczyk, Mehdi Rashidi Fard, Umar Toseef, Adel Zaalouk, Jon Matias, Victor Fuentes, Matteo Gerola, Roberto Doriguzzi Corin, Bartosz BelterAbstract:OpenFlow is a leading standard for Software-Defined Networking (SDN) and has already played a significant role in reshaping network infrastructures. However, a wide range of existing provider domains is still not equipped with a framework that supports wider deployment of an OpenFlow-based control plane beyond Ethernet-dominated networks. We address this gap by introducing a Hardware Abstraction Layer (HAL) which can transform legacy network elements into OpenFlow capable devices. This paper details the functional architecture of HAL, discusses the key design aspects and explains how HAL can support a number of network device classes. In addition, this paper presents the implementation details of HAL for hardware platforms such as DOCSIS (Data over Cable Service Interface Specification) and DWDM (Dense Wavelength Division Multiplexing) which have so far received little attention by the OpenFlow research community despite their wide real-world deployment.