Information sharing between two well-deened development environments demands data transformation between the tools or the underlying repositories of the environments. We give a solution to the problem of making tools in diierent environments cooperate without modifying the tools or their environments. In building an interface between a kbs environment and a selected case tool we have used a tra...

The aim of Web services is the provision of software services to a range of different users in different locations. Service localisation in this context can facilitate the internationalisation and localisation of services by allowing their adaption to different locales. The authors investigate three dimensions: (i) lingual localisation by providing service-level language translation techniques ...

We present a formal methodology and tool for uncovering errors in the interaction of software modules. Our methodology consists of a suite of languages for defining software interfaces, and algorithms for checking interface compatibility. We focus on interfaces that explain the method-call dependencies between software modules. Such an interface makes assumptions about the environment in the fo...

Hardware/software partition is a critical phase in hardware/software co-design. This paper proposes a hybrid partitioning framework, in which we design a set of protocol converters to construct the interface component between the hardware and software components, and reuse the formerly well-built partitioning rules by introducing protocol converters and rewriting them for this hybrid framework....

User interface (UI) is point of interaction between user and computer software. The success and failure of a software application depends on User Interface Design (UID). Possibility of using a software, easily using and learning are issues influenced by UID. The UI is significant in designing of educational software (e-Learning). Principles and concepts of learning should be considered in addit...

or low-fidelity prototypes are generally limited in function but only need limited prototyping effort. They usually do not require programming skills and coding. They are constructed to facilitate discussion of UI concepts and design alternatives, rather than to model the user interaction with a system. Low fidelity prototypes (see Figure 63, left) therefore mainly demonstrate the look, but rar...

We present an automata-based execution model describing the interaction and internal behaviors of software components extending our previous work with internal behaviors. In order to make the services provided by the component unblockable without knowing the implementation details, we propose an interface model that specifies all the unblockable interaction behaviors with any environment. To th...