Gerd Moosmann

TL;DR: In this article, a plurality of process components and context independent interactions among the process components are defined, each of the process component characterizes software implementing a respective and distinct process, and each process component defines at least one respective service interface for interacting with business objects associated with other process components.

TL;DR: In this article, a plurality of deployment units, each deployment unit associated with at least one identified group of process components, are formed, and each process component is entirely included in exactly one deployment unit.

TL;DR: In this article, the authors define a plurality of process components, each of which characterizes software implementing a respective and distinct process, and each of the process components defines a respective at least one service interface for communicating and interacting with other process components.

TL;DR: In this paper, a plurality of business objects and interactions between these business objects are defined, and each business object is operable to encapsulate business data and can be associated with exactly one process component.

TL;DR: In this article, the authors present an architectural design for application software implementing requests and management commands, which is divided into multiple processes of components interacting with each other through service interfaces and multiple service interfaces operations.