System testing is concerned with testing an entire system based on its specifications. In the context of object-oriented, UML development, this means that system test requirements are derived from UML analysis artifacts such as use cases, their corresponding sequence and collaboration diagrams, class diagrams, and possibly Object Constraint Language (OCL) expressions across all these artifacts. Our goal here is to support the derivation of functional system test requirements, which will be transformed into test cases, test oracles, and test drivers once we have detailed design information. In this paper, we describe a methodology in a practical way and illustrate it with an example. In this context, we address testability and automation issues, as the ultimate goal is to fully support system testing activities with high-capability tools.

We propose a methodology for hypermedia design which is based on a UML profile for the hypermedia domain. Starting with a use case analysis and a conceptual model of the application we first provide guidelines for modeling the navigation space. From the navigation space model we can derive, in a next step, a navigational structure model which shows how to navigate through the navigation space using access elements like indexes, guided tours, queries and menus. Finally, a presentation model is constructed that can be directly implemented by HTML frames. The different models of the design process are represented by using a hypermedia extension of UML.

We propose a precise UML-based authoring method for Web applications. This authoring method is part of the UML-based Web Engineering (UWE) approach. Starting with a requirement analysis done by use cases technique, it focuses on the design phase. The conceptual model of the application is used as guideline for modeling the navigation space. From the navigation space model we derive, in a next step, a navigation structure model which shows how to navigate through the navigation space using access elements like indexes, guided tours, queries and menus. Finally, a presentation model is constructed based on the navigation structure model. It provides an appropriate UML notation to support sketching and storyboarding. In addition, we suggest to use UML interaction diagrams to represent the presentation flow. During the whole development process we identify steps that can be performed in an automatic way thus providing the basis for a generation mechanism for Web application design. The different models of the design process are represented by using a UML conform extension of UML for Web applications (UML profile). The authoring process is illustrated with an example: a Web--based conference review system. The strength of the presented Web engineering approach is given by the fact that we use exclusively the UML notation and techniques. Moreover, our specification of constraints with OCL (part of UML) allows augmenting the exactitude of the models. In the same way our methodology has a high degree of precision in the description of guidelines of the authoring process of Web application, which can even partially be automated. Keywords: Web Engineering, Unified Modeling Language, Web applications, Authoring Process, Design Method, Systematic Development, UML Extension 1

Use cases have proven helpful for eliciting, communicating and documenting requirements. But whereas functional requirements are well supported, use cases provide less support for working with extra-functional requirements, such as security requirements. With the advent of e-commerce applications, security and other extra-functional requirements are growing in importance. In an earlier paper, the authors have introduced the concept of misuse cases -- inverted use cases to denote functions that should not be possible to perform in a system. In this paper, security related misuse cases are elaborated in further detail through a discussion of templates for their textual description.

This paper presents a comparative study of the most relevant methodologies for hypermedia and Web development published in the last few years. Most of these methods focus on the design of hypermedia applications; only a few cover more aspects of the life cycle, such as requirements capture, implementation and/or testing. One common characteristic is the separation of the domain analysis from the specification of the navigation space structure as well as from the design of the user interface. A brief description of each of these methodologies is given as well as a set of comparisons. We compare the main concepts, the phases o steps of the model, CASE Tool support as well as the modelling technique, notation and graphical representation. A list of the most relevant characteristics of the Unified Process is given as well comparing it to hypermedia development methodologies.

Abstract. Refactoring of UML class diagrams is an emerging research topic and heavily inspired by refactoring of program code written in object-oriented implementation languages. Current class diagram refactoring techniques concentrate on the diagrammatic part but neglect OCL constraints that might become syntactically incorrect by changing the underlying class diagram. This paper formalizes the most important refactoring rules for class diagrams and classifies them with respect to their impact on annotated OCL constraints. For refactoring rules, whose application on class diagrams could make attached OCL constraints incorrect, we formally describe how the OCL constraints have to be refactored to preserve their syntactical correctness. Our refactoring rules are defined in the graph-grammar based formalism proposed by the QVT Merge Group for the specification of model transformations. 1

In this state of the art report, we review advances in distributed component technologies, such as the Enterprise Java Beans specification and the CORBA Component Model. We assess the state of industrial practice in the use of distributed components. We show several architectural styles for whose implementation distributed components have been used successfully. We review the use of iterative and incremental development processes and the notion of model driven architecture. We then assess the state of the art in research into novel software engineering methods and tools for the modelling, reasoning and deployment of distributed components. The open problems identified during this review result in the formulation of a research agenda that will contribute to the systematic engineering of distributed systems based on component technologies.

Abstract—Use cases are believed to be a good basis for system testing. Yet, to automate the test generation process, there is a large gap to bridge between high-level use cases and concrete test cases. We propose a new approach for automating the generation of system test scenarios in the context of object-oriented embedded software, taking into account traceability problems between highlevel views and concrete test case execution. Starting from a formalization of the requirements based on use cases extended with contracts, we automatically build a transition system from which we synthesize test cases. Our objective is to cover the system in terms of statement coverage with those generated tests: An empirical evaluation of our approach is given based on this objective and several case studies. We briefly discuss the experimental deployment of our approach in the field at Thalès Airborne Systems. Index Terms—Use case, test generation, scenarios, contracts, UML. 1

Abstract. Several agent-oriented methodologies have been proposed over the last few years. Unlike the object-oriented domain and unfortunately for designers, most of the time, each methodology has its own purposes and few standardization works have been done yet, limiting the impact of agent design on the industrial world. By studying three existing methodologies- ADELFE, Gaia and PASSI- and the concepts related to them, this paper tries to find a means to unify their metamodels. Comparing a certain number of features at the agent or system level (such as the agent structure, its society or organization, its interactions capacities or how agents may be implemented) has enabled us to draw up a first version of a unified meta-model proposed as a first step toward interoperability between agent-oriented methodologies. 1

Test case generation for concurrent reactive systems on the grounds of symbolic execution basically amounts to searching their state space. As in the case of model checkers, di#erent search strategies (depth-first, breadth-first, best-first, tabu) together with di#erent strategies for storing visited states have a significant impact on the performance of the generation algorithm. We present experimental data for the performance of di#erent search strategies and discuss the results, taking into account counter examples as generated by model checkers.