International Journal of Software Engineering and Knowledge Engineering

Concurrent programs are more difficult to test than sequential programs because of non-deterministic behavior. An execution of a concurrent program non-deterministically exercises a sequence of synchronization events called a synchronization sequence (or SYN-sequence). Non-deterministic testing of a concurrent program P is to execute P with a given input many times in order to exercise distinct SYN-sequences. In this paper, we present a new testing approach called reachability testing. If every execution of P with input X terminates, reachability testing of P with input X derives and executes all possible SYN-sequences of P with input X. We show how to perform reachability testing of concurrent programs using read and write operations. Also, we present results of empirical studies comparing reachability and non-deterministic testing. Our results indicate that reachability testing has advantages over non-deterministic testing.

Recently, object-oriented specifications of distributed systems has gained more attention. The object-oriented approach is known for its flexibility for system construction. However, one of the major challenges is to provide facilities for the dynamic modifications of such specifications during the development and maintenance process. Yet, current work has not addressed the dynamic modifications of specifications of distributed systems. In this paper, we are concerned with formal description techniques that allow for the development and dynamic modification of executable specifications. A two-level model for the evolution of large object-oriented specifications is introduced. The first deals with the dynamic modifications of types (classes), while the second deals with modifications of modules. We have defined a set of structural and behavioral constraints to ensure specification consistency after modification at both levels. To allow dynamic modification of types and modules, we have developed a reflective object-oriented specification language which uses meta-objects to support the modification operations. In this language, types and modules are objects.

Recently, many on-line help systems have been developed that provide usage explanation for applications. However, it is difficult to find out necessary information in help contents and to understand how to obtain complete information. A navigation mechanism which can provide a user with essential information and guide the user so that he can carry out intended actions is indispensable. In this paper, we propose an adaptive navigation system which does not display navigation information on decisions that a user has already made by reflecting the current state of an application. In this research, in order to describe the structure of an application, Petri nets which are suitable for modeling event-driven systems are used. The application system is constructed based on these Petri nets. By communicating between the application system and its navigation system through these Petri nets, user navigation system reflecting the execution state of the application is realized.

The BOOTSTRAP approach to software process assessment and improvement offers a methodology which can be suitably used with different types of the software process and products, and with different software producing organization structures and sizes. The approach is supported by cumulative data about the software industry as a whole as well as its individual sectors. At the same time BOOTSTRAP is based on the ISO 9000 series quality standards and appropriately general software project management standards (ESA-PSS-05), as well as is related to such defacto maturity standards as SEI's CMM. More granularity in expressing capability (in terms of scale and multidimensionality) makes BOOTSTRAP particularly suitable for process improvement. While having established position in Europe and participating in such wider standardization efforts as ISO/SPICE, it is important for BOOTSTRAP to look for comparisons of assumptions and results elsewhere. This paper presents the BOOTSTRAP methodology and and in conclusions brings forward some topics that may constitute a cultural interface orspecific boundary conditions between different software process assessment and improvement approaches.

Current interest in improving the effectiveness and predictability of software development has led to a recent focus on software process modeling and improvement. Process-centered software development environments (PCSDEs), have been examined as a useful adjunct to software process modeling. A number of PCSDEs have been designed and built; an examination of the range of potential users of such environments reveals a wide range of needs with respect to information about an enacted software process and how this information is presented. This paper describes one aspect of a PCSDE supporting multiple simultaneous views: the design of a representation of enacted software processes which is suitable for the generation of multiple simultaneous views.

Cogito 1 is the first iteration of a Z-based integrated methodology and support system for formal software development. This paper gives an overview of the Cogito methodology and associated tools. Particular emphasis is placed on the way in which Cogito integrates the various phases of the formal development process and provides comprehensive tools support for all phases of development addressed by the methodology.