Rainer Gimnich

Using Existing Software Assets in SOA Design

Service-Oriented Architecture (SOA) is a business-driven IT architecture that is based on services (repeatable business tasks). The move to SOA is performed evolutionarily in most companies and public organizations. Therefore, identifying and leveraging software assets from existing applications or packageshas become a key task in SOA design. This paper summarizes major practical requirements from SOA projects and provides an overview of methodimperatives that address the requirements. Tool functions that support these imperatives conclude this overview

Wartungsunterstützung in heterogenen Sprachumgebungen ein Überblick zum Projekt GUPRO

Wirtschaftliche Wartung und Weiterentwicklung von Anwendungssoftware setzt ein grundsatzliches Verstehen vorhandener Quelltexte voraus. Diese sind oft wenig strukturiert, schwach kommentiert und in unterschiedlichen Umgebungen entstanden. Im Projekt GUPRO — Eine Gene-rische Umgebung zum Programmverstehen 1 — wird ein benutzerkonfigurierbarer Generator zur Erzeugung sprachubergreifender Programmverstehenswerkzeuge entwickelt, die das Nachvollziehen und Verstehen auch heterogener Software behebiger Sprachen (Programmiersprachen, Anfragesprachen, Sprachen der “4. Generation”) unterstutzen. Hierzu dienen Anfrage- und Browsing-Werkzeuge, die uber eine gemeinsame, graphbasierte Datenstruktur integriert sind.

Implementing direct manipulation query languages using an adequate data model

Human factors work in the areas of database use addresses the design of the user interface of interactive database applications as well as the design of the on-line interface of the database system itself. Some conceptual prerequisites of using direct manipulation in an on-line database interface are discussed. It will be shown that choosing an adequate data model is vital in investigating the application of this style of interaction in complex database environments requiring a high level of abstraction. As an example, an advanced data model is introduced. In this model, the semantics of operating directly on a graphical database interface is specified, possible ambiguities are revealed, and a way of implementing the interface in an existing (e.g. normalized relational) data-base environment is shown.

Constructive Formal Specifications for Rapid Prototyping

The approach presented here suggests a way to translate software specifications into an operational form which can be used as a prototype, for revising the requirements, and for testing purposes by relating it to the actual implementation developed later.

A unifying view on interaction styles and their implementation in a user interface management system

This paper presents a research approach in an area common to software engineering and software ergonomics.

Human factors of database systems

The usability of software is becoming an increasingly important issue with vast economic implications. Indeed, the productivity and satisfaction of end-users can be a determining factor for the success of database systems.

Planning Year 2000 transformations using standard tools: an experience report

The Year 2000 transformation is by no means merely a problem of computer science, involving coding practice or programming-in-the-small. It turns out that the Year 2000 problem is mainly a project management problem. To plan and control a Year 2000 transformation one has to discover the facts on which all planning is based on. In this paper, we describe a straightforward approach to gather the facts relevant for a Year 2000 coarse-grained planning. It was done in a customer engagement at a large German insurance company. The engagement was done completely at the customers site using only standard tools, which are most likely installed in each larger organization.