Deriving Available Behavior All Out from Incompatible Component Compositions
نویسندگان
چکیده
منابع مشابه
Deriving Available Behavior All Out from Incompatible Component Compositions
In component-based software development, an important problem is behavioral incompatibility in component compositions. That two components are behaviorally incompatible means that they cannot work together due to the mismatching order of exchanged messages between them. One of the approaches to solving this problem is to construct an environment for the incompatibility components and make it po...
متن کاملConstructing Web Services out of Generic Component Compositions
Todays information systems are built using various component models such as Enterprise Java Beans, JavaBeans, Microsoft COM+, and CORBA distributed objects. In this paper we argue that it is crucial for designers of information systems to interactively build and test systems constructed from (a) components (enabling interoperability across component models) and (b) Web services at the same time...
متن کاملDeriving component designs from global requirements
This paper is concerned with the early development phases of distributed applications, service compositions and workflow systems. It deals with the transformation of a global requirements model, which makes abstraction from the physical distribution of the different system functions, into a system design that identifies a certain number of distributed components. The temporal constraints of the...
متن کاملComponent Publications and Compositions
The method of refinement of component and object systems, known as rCOS, provides a notation with a formally defined relational semantics. In rCOS, the notions of interfaces, contracts, components, and component publications are formally defined. With the definitions of various compositions and refinement relations between contracts and components, the key software artifacts in all phases of a ...
متن کاملDeriving Behavior Specifications from Textual Use Cases
The design of a software system or component starts with specifying its requirements; traditionally, use cases written in natural language are used for this task. While this makes use cases easily readable, it neither permits reasoning on requirement specifications (written as use cases), nor employing the use cases in deriving an initial design in an automated way. While employing linguistic t...
متن کاملذخیره در منابع من
با ذخیره ی این منبع در منابع من، دسترسی به آن را برای استفاده های بعدی آسان تر کنید
ژورنال
عنوان ژورنال: Electronic Notes in Theoretical Computer Science
سال: 2006
ISSN: 1571-0661
DOI: 10.1016/j.entcs.2006.05.033