Dirk Jäger

Using UML for software process modeling

We examine the benefits of using an object-oriented modeling language for software process modeling. We show how the Unified Modeling Language (UML) can be used to model software processes based on dynamic task nets, which evolve continuously during enactment. We have selected UML for various reasons: it is wide-spread, provides a comprehensive set of diagrams for both structural and behavioral modeling, and supports the early phases of process modeling (analysis and design).

AHEAD: A Graph-Based System for Modeling and Managing Development Processes

Management of development processes in different engineering disciplines is a challenging task. The AHEAD system addresses these challenges by providing an integrated environment for modeling and managing development processes. Products, activities, and resources are managed in an integrated way; furthermore, AHEAD supports evolving development processes by seamless interleaving of planning and execution. AHEAD is based on programmed graph transformations; tools are generated from a graph-based specification. Finally, a wide-spread object-oriented modeling language (UML) is employed for acquiring process knowledge from domain experts.

UPGRADE: A Framework for Building Graph-Based Interactive Tools

Abstract Construction of interactive tools for visual languages is a challenging task. The UPGRADE framework leverages tool builders by integrating application logic and GUI components. It is based on attributed graphs as its internal data model. At the user interface (external representation), graphs can be rendered in multiple ways, including graphics, trees, text and tables. The framework is open, e.g., third-party viewer components may be plugged into the framework.

Generating tools from graph-based specifications

Abstract This paper describes an approach for generating graphical, structure-oriented software engineering tools from graph-based specifications. The approach is based on the formal meta modeling of visual languages using graph rewriting systems. Besides the syntactical and semantical rules of the language, these meta models include knowledge from the application domains. This enables the resulting tools to provide the user with high level operations for editing, analysis and execution of models. Tools are constructed by generating source code from the meta model of the visual language, which is written in the very high level programming language PROGRES. The source code is integrated into a framework which is responsible for the invocation of commands and the visualization of graphs. As a case study, a visual language for modeling development processes together with its formal meta model is introduced. The paper shows how a process management tool based on this meta model is generated and reports on our experiences with this approach.

A Delegation Based Model for Distributed Software Process Management

Complex development processes which cross organizational boundaries require specialized support by process management systems. Such processes are planned in a top-down manner. A suitable cooperation model for these processes is the delegation of process parts. Because the client and the contractor of a delegation may be independent organizations they may have diverging interest concerning autonomy of process execution, information-hiding, control, etc. We propose a concept for delegating process parts which takes these interests into account and describe how delegation is implemented in the process management system AHEAD.

An Adaptive and Reactive Management System for Project Coordination

Design processes in chemical engineering are hard to support. In particular, this applies to conceptual design and basic engineering, in which the fundamental decisions concerning the plant design are performed. The design process is highly creative, many design alternatives are explored, and both unexpected and planned feedback occurs frequently. As a consequence, it is inherently difficult to manage design processes, i.e. to coordinate the effort of experts working on tasks such as creation of flowsheets, steady-state and dynamic simulations, etc. On the other hand, proper management is crucial because of the large economic impact of the performed design decisions. We present a management system which takes the difficulties mentioned above into account by supporting the coordination of dynamic design processes. The management system equally covers products, activities, and resources, and their mutual relationships. In addition to local processes, interorganizational design processes are addressed by delegation of subprocesses to subcontractors. The management system may be adapted to an application domain by a process model which defines types of tasks, documents, etc. Furthermore, process evolution is supported with respect to both process model definitions and process model instances; changes may be propagated from definitions to instances and vice versa (round-trip process evolution).

UPGRADE - A Framework for Graph-Based Visual Applications

This paper gives a brief introduction to the UPGRADE framework which is designed to support generating code for structure-riented software engineering tools from graph-based specifications. The framework is written in Java and contains a variety of mechanisms for configuring the representation of internal models of generated tools. The tool designer can therefore build tools which offer to the user a convenient representation of a visual language instead of restricting him to a predefined notation. Generation of a tool requires no additional programming effort after finishing the specification. It is thus easy to alter the tools internal logic just by changing its specification and by generating a modified tool version from it.

Modeling Management and Coordination in Development Processes

Coordination and management efforts are important activities within every development process. Just as the technical tasks, which directly contribute to the product, coordination and management tasks should be explicitly represented in a process model. Both should clearly be separated to allow the process modeler to modify management and coordination strategies independently from technical tasks, which is important if we consider interorganization cooperation in development processes.