Several requirements specification styles for the specification of reactive systems have been proposed in the literature. Informal specifications are the most widely used in the software industry nowadays, mainly because they are “understandable” by domain experts and software engineers, and therefore can be included as part of a software contract. Unfortunately, because of the inherent ambigui...

Recently, the Web Services Interoperability Organization (WS-I) has announced to have completed its interoperability standards work. The latest deliverables include the so-called “Basic Security Profile” and the “Reliable Secure Profile”. This gives rise to the question whether or not Web Services adopters can rely on interoperability and functionality of Web Services stacks, in particular in t...

This paper argues that, in a collaboration context, instead of Web services requiring client applications to comply with individual permutations of security configurations, a standardized mechanism should be established to ensure global security-interoperability. Such a solution would facilitate providing Web services in Grid Services contexts as well. A framework is proposed which comprises, i...

E-contracts are textual documents describing various contractual assignments/tasksand dependencies among contractual elements such as parties, activities, clauses, exceptions and payments. The dependencies and constraints in e-contract can be differently stated in different parts of large documents. Inconsistencies in the e-contract document, particularly the contract activities and clauses spe...

Abstract A toll road is one of the National Strategic Projects with complete problems and needs highspeed performance during construction. So, contract construction that usually applied to these projects design build contract. Furthermore, best practice for Design Build combined Lump Sum as an estimation cost aspect, so type used Price. This study aims review implementation Lup Price Contract b...

Modular static verification of concurrent object-oriented programs remains a challenge. This paper discusses the impact of concurrency on the use and meaning of behavioural specifications, and in particular on method contracts and class invariants. Atomicity of methods is often advocated as a solution to the problem of verification of multithreaded programs. However, in a design-by-contract fra...

Contract-based property checkers hold the potential for precise, scalable, and incremental reasoning. However, it is difficult to apply such checkers to large program modules because they require programmers to provide detailed contracts, including an interface specification, module invariants, and internal specifications. We argue that given a suitably rich assertion language, modest effort su...

The provision of multimedia services is becoming ubiquitous. Services such as audio/video streaming, digital libraries and on-line businesses are widely deployed. Different middleware frameworks have been developed to enable such a dynamic and customized delivery of multimedia services. Two major types of QoS-aware systems have evolved:(1) Reservation-based Systems such as Qualman [3] and (2) A...

Contracts are a pragmatic tool for managing software systems, but programs using contracts suffer runtime overhead. If this overhead becomes a performance bottleneck, programmers must manually edit or remove their contracts. This is no good. Rather, the contracts should identify their own inefficiencies and remove unnecessary dynamic checks. Implementing contracts with Rosette is a promising wa...