Commercial software component models are frequently based on
object-oriented concepts and terminology with appropriate binding, persistence and distribution support. In this paper, we argue that a
process-oriented view on cooperating software components based on the concepts and terminology of a language/action perspective on cooperative
work provides a more suitable foundation for the analysis, design and implementation of software components in business applications.
We first explain the relationship between data-, object- and process-oriented component modeling and then illustrate our process-oriented
approach to component definition using three case studies from projects with German software companies.
We also report on our experience gained in developing a class framework and a set of tools to assist in the systematic process-oriented
development of business application components. This part of the paper also clarifies that a process-oriented perspective
fits well with today’s object-oriented language and system models.