Top Down Versus Bottom Up in Service-Oriented Integration: An MDA-Based Solution for Minimizing Technology Coupling

  • Theo Dirk Meijler
  • Gert Kruithof
  • Nick van Beest
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4294)

Abstract

Service-oriented integration typically combines top-down development with bottom-up reverse engineering. Top-down development starts from requirements and ends with implementation. Bottom-up reverse engineering starts from available components and data sources. Often, the integrating business processes are directly linked to the reverse-engineered web services, resulting in a high degree of technology coupling. This in turn leads to a low level of maintainability and low reusability. The Model-Driven Architecture (MDA) provides an approach aimed at achieving technology independency through full top-down development. However, this approach does not handle the bottom-up reverse-engineered components very well. In this paper, an approach is introduced that combines top-down with bottom-up realization, while minimizing the technology coupling. This is achieved by an explicit buffer between top-down and bottom-up. “High-level” web services are derived through top-down development, whereas “Low-level” web services are reverse-engineered, and a mapping is created between the two. The approach focuses on engineering web services reversely, while retaining the advantages of the MDA with respect to platform independency, maintainability and reusability.

Topics: Business Service Modeling, Service Assembly.

Scientific Area: Service-oriented software engineering.

References

  1. 1.
    Hubert, R.: Convergent Architecture. Wiley Computer Publishing, Chichester (2002)Google Scholar
  2. 2.
    Frankel, D.S.: Model Driven Architecture Applying MDA to Enterprise Computing. OMG Press – Wiley Publishing (2003) ISBN 0-471-31920-1Google Scholar
  3. 3.
    Erl, T.: A Field Guide to Integrating XML and Web Services. Pearson Education, Publishing as Prentice Hall Technical Reference (2004) ISBN 0-13-142898-5Google Scholar
  4. 4.
    Skogan, D., Groenmo, R., Solheim, I.: Web service composition in UML. In: Proceedings of the Eighth IEEE International Enterprise Distributed Object Computing Conference (EDOC 2004). IEEE, Los Alamitos (2004)Google Scholar
  5. 5.
    Orriëns, B., Yang, J., Papazoglou, M.P.: Model Driven Service Composition. In: Orlowska, M.E., Weerawarana, S., Papazoglou, M.P., Yang, J. (eds.) ICSOC 2003. LNCS, vol. 2910, pp. 75–90. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  6. 6.
    Aiello, M., Papzoglou, M., Yang, J., Carman, M., Pistore, M., Serafini, L., Traverso, P.: A request language for web-services based on planning and constraint satisfaction. In: Proceedings of the VLDB workshop on Technologies for E-Services, Hongkong, China (2002)Google Scholar
  7. 7.
    Cardoso, J., Sheth, A., Miller, J., Arnold, J., Kochut, K.: Quality of Service for Workflows and Web Service Processes. Journal of Web Semantics 1(3), 281–308 (2004)Google Scholar
  8. 8.
    Rajasekaran, P., Miller, J., Verma, K., Sheth, A.: Enhancing Web Services Description and Discovery to Facilitate Composition. In: Cardoso, J., Sheth, A.P. (eds.) SWSWPC 2004. LNCS, vol. 3387, pp. 55–68. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  9. 9.
    Balsters, H., de Brock, E.O.: An object-oriented framework for managing cooperating legacy databases. In: Konstantas, D., Léonard, M., Pigneur, Y., Patel, S. (eds.) OOIS 2003. LNCS, vol. 2817, pp. 311–316. Springer, Heidelberg (2003)CrossRefGoogle Scholar
  10. 10.
    Fowler, M.: Patterns of Enterprise Application Architecture. Eddison Wesley Pearson Education (2003) ISBN 0-321-12742-0Google Scholar
  11. 11.
    Gamma, E., Helm, R., Johnson, R., Vlissides, J.: Design patterns: elements of reusable object-oriented software. Addison-Wesley Longman Publishing Co., Inc., Boston (1995)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Theo Dirk Meijler
    • 1
  • Gert Kruithof
    • 1
  • Nick van Beest
    • 1
  1. 1.Information Systems, Faculty of Management and Organization 

Personalised recommendations