We present a Tool Suite which supports the (re-)construction of a behavioral model of a legacy component based on a learning approach by exploiting knowledge of known models of the existing component environment. This in turn enables to check whether the legacy component can be integrated correctly into its environment.

How do you organize an "industrial strength" one semester educational programming project for up to 200 second year students? This paper reports on four years of experience with such projects at the University of Paderborn and the University of Braunschweig. Key properties of our project design are: starting with an existing large application, regular hard deadlines with peer reviews and presentations to a large audience, working in groups, applying project and configuration management tools, a standard system architecture with interchangeable components and competing software agents, quality assurance and standard conformance testing through final overall system integration spanning all groups, and exposure to real-world project threats.

This paper proposes to use SDL block diagrams, UML class diagrams, and UML behavior diagrams like collaboration diagrams, activity diagrams, and statecharts as a visual programming language. We describe a modeling approach for flexible, autonomous production agents, which are used for the decentralization of production control systems. In order to generate a (Java) implementation of a production control system from its specification, we define a precise semantics for the diagrams and we define how different (kinds of) diagrams are combined to a complete executable specification.

it turns collaboration diagrams in a powerfull and easy-to-read visual programming construct. However, a single collaboration diagram is usually not expressive enough to model complex operations performing several modifications at different parts of the overall object structure. Such series of modifications need several collaboration diagrams to be modeled. In addition, there may be different situations where certain collaboration diagrams Figure 1 The Fujaba Environment Concepts \t \t \t <

Information systems have to evolve continually in order to keep up with emerging requirements. Various problems arise with each such evolution step, e.g. the modification of the application's conceptual data structure, the migration of existing data, the adaption of application code, and the modification of technical documentation. Most database systems provide only limited support for schema evolution while problems like data migration and application migration are tackled manually by the programmers. This evolution process is unsatisfactory for a number of novel complex evolutionary information systems (CEIS) in the area of business and engineering applications. The paper describes our experiences with a case study in developing a CEIS in the domain of analysis and design of mixed signal printed circuit boards. We show that a meta schema approach combined with a well defined set of schema transformations is a practical way to cope with evolution. Based on this case study, we distinguish application specific from reusable architectural components and propose a systematic approach of building CEIS.