Subjects vs. Objects – A Top-Down Approach

  • Clemens Krauthausen
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 104)


This article demonstrates how to improve the link between the requirements of the business and the capabilities of IT. The fundamental starting point is to define business objects solely from the business point of view, thus establishing the predominance of business requirements when interpreting and using established IT functions.

Starting from business objects, the content of the business - what to do – is to be identified and determined. The general principle is that all the business functions as well as the communication needs should be determined and decided by the people responsible for the business: These are defined as the subjects responsible for determining and processing business activities.

As opposed to that, the IT functions have a supporting role. In particular, the many IT functions which result from various technical needs should be identified and be placed under the sole and entire responsibility of the IT. This way a clear focus of the IT on the defined business needs can be maintained.


S-BPM business object business task business object services workflow transaction services 


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Allweyer, T.: Geschäftsprozess-Management. W3L GmbH (2005)Google Scholar
  2. 2.
    Allweyer, T.: BPMN - Business Process Modeling Notation. Books on Demand (2009)Google Scholar
  3. 3.
    Buchwald, H.: The Power of ‘As-Is’ Processes. In: Buchwald, H., Fleischmann, A., Seese, D., Stary, C. (eds.) S-BPM ONE 2009. CCIS, vol. 85, pp. 13–23. Springer, Heidelberg (2010)CrossRefGoogle Scholar
  4. 4.
    Buchwald, H., Fleischmann, A., Seese, D., Stary, C. (eds.): S-BPM ONE 2009. CCIS, vol. 85. Springer, Heidelberg (2010)Google Scholar
  5. 5.
    Chao, T., Cohn, D., Flatgard, A., Hahn, S., Linehan, M., Nandi, P., Nigam, A., Pinel, F., Vergo, J., Wu, F.Y.: Artifact-Based Transformation of IBM Global Financing. In: Dayal, U., Eder, J., Koehler, J., Reijers, H.A. (eds.) BPM 2009. LNCS, vol. 5701, pp. 261–277. Springer, Heidelberg (2009)CrossRefGoogle Scholar
  6. 6.
    Chappell, D.A.: Enterprise Service Bus. O’Reilly Media Inc. (2001)Google Scholar
  7. 7.
    Davenport, T.H.: Process Innovation: Reengineering Work Through Information Technology. Harard Business School (1992)Google Scholar
  8. 8.
    Encyclopedia, W.T.F.: Artifact (software development),
  9. 9.
    Encyclopedia, W.T.F.: Business,
  10. 10.
  11. 11.
    Fischer, H., Fleischmann, A., Obermeier, S.: Geschäftsprozesse realisieren. Vieweg (2006)Google Scholar
  12. 12.
    Fleischmann, A.: What Is S-BPM? In: Buchwald, H., Fleischmann, A., Seese, D., Stary, C. (eds.) S-BPM ONE 2009. CCIS, vol. 85, pp. 85–106. Springer, Heidelberg (2010)CrossRefGoogle Scholar
  13. 13.
    Fleischmann, A., Schmidt, W., Singer, R., Seese, D. (eds.): S-BPM ONE 2010. CCIS, vol. 138. Springer, Heidelberg (2011)Google Scholar
  14. 14.
    Grässle, P., Baumann, H., Baumann, P.: UML projektorientiert. Galileo Press (2001)Google Scholar
  15. 15.
    Komus, A.: Key Lessons from Wikimanagement and BPM Best Practices: Aspiring for a Truly Holistic Approach in BPM. In: Fleischmann, A., Schmidt, W., Singer, R., Seese, D. (eds.) S-BPM ONE 2010. CCIS, vol. 138, pp. 3–16. Springer, Heidelberg (2011)CrossRefGoogle Scholar
  16. 16.
    Leymann, F., Roller, D.: Production Workflow: Concepts and Techniques. Prentice Hall (1999)Google Scholar
  17. 17.
    Luhmann, N.: Einführung in die Systemtheorie. Carl-Auer (2009)Google Scholar
  18. 18.
    Melton, J., Buxton, S.: Quering XML - XQuery, XPath, and SQL/XML in Context. Morgan Kaufmann Publishers (2006)Google Scholar
  19. 19.
    Metasonic: Metasonic site,
  20. 20.
    Oestereich, B.: Analyse und Design mit UML 2. Oldenbourg (2005)Google Scholar
  21. 21.
    Pant, K.: Business Process Driven SOA Using BPMN and BPEL. Packt Publishing Ltd. (2008)Google Scholar
  22. 22.
    Paper, O.W.: Oracle application integration architecture enterprise business objects (ebo) concepts (2009),
  23. 23.
    Popper, K.R.: Objektive Erkenntnis. Hoffmann und Campe (1984)Google Scholar
  24. 24.
    Porter, M.E.: Competitive Advantage. Free Press (1985)Google Scholar
  25. 25.
    Tidwell, D., Laurent, S.S., Romano, R.: XSLT. O’Reilly Media (2008)Google Scholar
  26. 26.
    UN/CEFACT: Core components technical specification,
  27. 27.
    van der Vlist, E.: XML Schema. O’Reilly Media (2002)Google Scholar
  28. 28.
    Weske, M.: Business Process Management. Springer, Heidelberg (2007)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  • Clemens Krauthausen
    • 1
  1. 1.IT EngineeringPöckingGermany

Personalised recommendations