We propose an approach for incremental modeling of composite Web services. The technique takes into consideration both the functional and nonfunctional requirements of the composition. While the functional requirements are described using symbolic transition systems—transition systems augmented with state variables, function invocations, and guards; non-functional requirements are quantified us...

The aim of program development process is to construct a correct program with respect to its requirements specification. Our paper deals with the first step of this process in the framework of the theory of correct programming. We construct requirements specification institution in terms of algebraic specifications, design specification institution in terms of functional programming and type th...

We have experienced the B Method on a case study which was defined by the French working group on formalisms for interactive systems, i.e. a Post-It® Notes like collaborative application. This experience showed that the B approach allows to cover the description, the formal specification, and the design of each component of basic architecture models, i.e., the five components of the Arch model....

Planning is a traditional research area in AI. The last decade has witnessed a large body of work in the development of languages and algorithms for planning, up to the point where complex, realistic problems can be modeled and solved in seconds. At the same time, thanks to the generality of the problem formulation, several applicative problems can be recasted into planning. This is also true i...

One of the current challenges of Service Oriented Engineering is to provide instruments for dealing with dynamic and unpredictable user requirements and environment. Traditional approaches based on workflow for orchestrating services provide little support for configuring at run-time the flow of activities. This paper presents a general approach for composing and orchestrating services in a sel...

In the SDLC the software requirement is the foremost step. A clear requirement specification results a reliable software development. But any change in requirement will disturb the whole development process and increase the software cost. But when the requirement is clearly defined we can save such cost, effort and time of re-development. In this proposed work we are presenting the agile based ...

This work proposes a set of important issues to analyze the feasibility of developing automatic design tools in automation and robotics tasks. The development of a methodology for the automatic design of modular systems makes possible to develop several types of systems by using the same tools for design. The automatic design process is based on the user requirements for system specification. I...

Scenarios are often constructed for illustrating example runs through reactive system. Scenarios that describe possible interactions between a system and its environment are widely used in requirement engineering, as a means for users to communicate their functional requirements. Various software development methods use scenarios to define user requirements, but often lack tool support. Existin...

eveloping software systems involves a series of activities where there are many opportunities to make errors. Such errors may occur at an early stage of the development process where user requirements are incorrectly or incompletely specified, and also in subsequent stages when design and programming faults are introduced. Thus, software development should always be accompanied by quality assur...

Agent-based models (ABMs) are ubiquitous in research and industry. Currently, simulating ABMs involves at least some imperative (step-by-step) computer instructions. An alternative approach is declarative programming, in which a set of requirements is described at a high level of abstraction. Here we describe a fully declarative approach to the automated construction of simulations for ABMs. In...