Extending the UN/CEFACT Modeling Methodology and Core Components for Intra-organizational Service Orchestration

  • Philipp Offermann
  • Christian Schröpfer
  • Maximilian Ahrens
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4652)


When creating a company’s IT structure based on a service-oriented architecture (SOA), it is necessary to first analyze the business domains and process areas of the company, then to model the business processes to be supported by the SOA and finally to convert the models into a service orchestration description. Currently, few methodologies exist to support this. At our department, we have proven that the UN/CEFACT Modeling Methodology (UMM) can be used for intra-organizational process integration. In this article we analyze if the UMM is sufficient for SOA, which artifacts are missing and how the UMM could be extended. The UMM was created to model the collaboration between different legal entities to perform collaborative business processes. There exist methods to convert these models into executable service choreography descriptions expressed in the Business Process Specification Schema (BPSS) or the Business Process Execution Language (BPEL). However, the business process models can also be used as a basis for an intra-organizational service orchestration. By extending the UMM it is possible to enable the automated generation of service orchestrations using Core Components and the Business Process Modeling Notation (BPMN).


UN/CEFACT Modeling Methodology (UMM) Core Components (CC) Business Process Execution Language (BPEL) Business Process Modeling Notation (BPMN) Service Orchestration Service-Oriented Architecture (SOA) 


  1. 1.
    Dietrich, J.: Nutzung von Modellierungssprachen und -methodologien standardisierter B2B-Architekturen für die Integration unternehmensinterner Geschäftsprozesse (unpublished Dissertation). TU Berlin, Fachgebiet Systemeanalyse und EDV (2006)Google Scholar
  2. 2.
    International Business Machines Corporation: developerWorks : SOA and Web services (2006),
  3. 3.
    Microsoft Corporation: .NET Architecture Center: Service Oriented Architecture (2006),
  4. 4.
    BEA Systems: Dev2Dev Online: Service-oriented Architecture (2006),
  5. 5.
    SAP AG: SAP - Enterprise Service-Oriented Architecture: Blueprint for Service-Based Business Solutions (2006),
  6. 6.
    World Wide Web Consortium: Web Services Architecture (2004),
  7. 7.
    OASIS Open: OASIS Commitees by Category: SOA (2006),
  8. 8.
    Object Management Group: Business Process Modeling Notation Specification (2006),
  9. 9.
    McCoy, D., Natis, Y.: Service-Oriented Architecture: Mainstream Straight Ahead. Gartner Research (2003)Google Scholar
  10. 10.
    Szyperski, C.: Component Oriented Programming. Springer, Heidelberg (1998)Google Scholar
  11. 11.
    Schmelzer, R.: Solving the Service Granularity Challenge (2005),
  12. 12.
  13. 13.
    Leymann, F., Roller, D., Schmidt, M.T.: Web services and business process management. IBM Systems Journal 41, 198–211 (2002)CrossRefGoogle Scholar
  14. 14.
    Newcomer, E., Lomow, G.: Understanding SOA with Web Services. Addison-Wesley, Reading (2005)Google Scholar
  15. 15.
    Andrews, T., Curbera, F., Dholakia, H., Goland, Y., Klein, J., Leymann, F., Liu, K., Roller, D., Smith, D., Trickovic, I., Weerawarana, S.: Business Process Execution Language for Web Services Version 1.1 (2003),
  16. 16.
    Skogan, D., Gronmo, R., Solheim, I.: Web service composition in UML. Enterprise Distributed Object Computing Conference, 2004. In: EDOC 2004. Proceedings. Eighth IEEE International, pp. 47–57 (2004)Google Scholar
  17. 17.
  18. 18.
    Object Management Group: Unified Modeling Language Specification Version 1.4.2 (2004),
  19. 19.
    UN/CEFACT: ISO\DTS 15000-5: 2006 Core Components Technical Specification 2nd edn. UN/CEFACT Version 2.2 (2006),
  20. 20.
    United Nations Economic Commission for Europe: Core Component Library (UN/CCL) (2006),
  21. 21.
    UN/CEFACT: UN/CEFACT – ebXML Business Process Specification Schema (2003),
  22. 22.
    White, S.A.: Introduction to BPMN. IBM Corporation (2004),
  23. 23.
    White, S.A.: Using BPMN to Model a BPEL Process. IBM Corp., United States (2005),
  24. 24.
    White, S.A.: Process Modeling Notations and Workflow Patterns. IBM Corp., United States (2004),

Copyright information

© Springer-Verlag Berlin Heidelberg 2007

Authors and Affiliations

  • Philipp Offermann
    • 1
  • Christian Schröpfer
    • 1
  • Maximilian Ahrens
    • 2
  1. 1.Faculty of Electrical Engineering and Computer Sciences, Technische Universität BerlinGermany
  2. 2.Deutsche Telekom Laboratories, BerlinGermany

Personalised recommendations