Transforming Object-Oriented Models to Process-Oriented Models

  • Guy Redding
  • Marlon Dumas
  • Arthur H. M. ter Hofstede
  • Adrian Iordachescu
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4928)

Abstract

Object-oriented modelling is an established approach to document the information systems. In an object model, a system is captured in terms of object types and associations, state machines, collaboration diagrams, etc. Process modeling on the other hand, provides a different approach whereby behaviour is captured in terms of activities, flow dependencies, resources, etc. These two approaches have their relative advantages. In object models, behaviour is split across object types, whereas in process models, behaviour is captured along chains of logically related tasks. Also, object models and process models lend themselves to different styles of implementation. There is an opportunity to leverage the relative advantages of object models and process models by creating integrated meta-models and transformations so that modellers can switch between these views. In this paper we define a transformation from a meta-model for object behavior modeling to a meta-model for process modeling. The transformation relies on the identification of causal relations in the object model. These relations are encoded in a heuristics net from which a process model is derived.

Keywords

Process model object model model transformation 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Kueng, P., Bichler, P., Kawalek, P., Schrefl, M.: How to compose an object-oriented business process model? In: Proceedings of IFIP TC8, WG8.1/8.2 working conference on method engineering, pp. 94–110. Chapman and Hall, London, UK (1996)Google Scholar
  2. 2.
    Booch, G., Rumbaugh, J., Jacobson, I.: The Unified Modeling Language User Guide. Addison-Wesley Professional, Reading (1998)Google Scholar
  3. 3.
    Object Management Group: Business Process Modelling Notation, Ver 1.0 (2006), http://www.bpmn.org
  4. 4.
    Andrews, T., Curbera, F., Dholakia, H., Goland, Y., Klein, J., Leymann, F., Liu, K., Roller, D., Smith, D., Thatte, S., Trickovic, I., Weerawarana, S.: Business Process Execution Language for Web Services, Version 1.1 (2003), http://dev2dev.bea.com/webservices/BPEL4WS.html
  5. 5.
    van der Aalst, W.M.P., ter Hofstede, A.H.M.: YAWL: Yet Another Workflow Language. Information Systems 30, 245–275 (2005)CrossRefGoogle Scholar
  6. 6.
    Becker, J., Kugeler, M., Rosemann, M.: Process Management. Springer, Heidelberg (2003)Google Scholar
  7. 7.
    Shared Web Services Pty. Ltd.: FlowConnect Model (August 2003)Google Scholar
  8. 8.
    Halpin, T.: Information modeling and relational databases: from conceptual analysis to logical design. Morgan Kaufmann Publishers Inc., San Francisco (2001)Google Scholar
  9. 9.
    van der Aalst, W.M.P., Barthelmess, P., Ellis, C.A., Wainer, J.: Proclets: A Framework for Lightweight Interacting Workflow Processes. International Journal of Cooperative Information Systems 10, 443–481 (2001)CrossRefGoogle Scholar
  10. 10.
    Snoeck, M., Poelmans, S., Dedene, G.: An architecture for bridging OO and business process modelling. In: 33rd International Conference on Technology of Object-Oriented Languages (TOOLS), Mont-Saint-Michel, France, pp. 132–143 (2000)Google Scholar
  11. 11.
    Wirtz, G., Weske, M., Giese, H.: The OCoN Approach to Workflow Modeling in Object-Oriented Systems. Information Systems Frontiers 3, 357–376 (2001)CrossRefGoogle Scholar
  12. 12.
    van der Aalst, W.M.P., de Medeiros, A.K.A., Weijters, A.J.M.M.: Genetic Process Mining. In: Ciardo, G., Darondeau, P. (eds.) ICATPN 2005. LNCS, vol. 3536, pp. 48–69. Springer, Heidelberg (2005)Google Scholar
  13. 13.
    van Dongen, B.F., de Medeiros, A.K.A., Verbeek, H.M.W., Weijters, A.J.M.M., van der Aalst, W.M.P.: The ProM Framework: A New Era in Process Mining Tool Support. In: 26th International Conference on Applications and Theory of Petri Nets (ICATPN), Miami, USA, pp. 444–454 (2005)Google Scholar
  14. 14.
    Reijers, H.A., Limam, S., van der Aalst, W.M.P.: Product-Based Workflow Design. Journal of Management Information Systems 20, 229–262 (2003)Google Scholar
  15. 15.
    Nigam, A., Caswell, N.S.: Business artifacts: An approach to operational specification. IBM Systems Journal 42, 428–445 (2003)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2008

Authors and Affiliations

  • Guy Redding
    • 1
  • Marlon Dumas
    • 1
  • Arthur H. M. ter Hofstede
    • 1
  • Adrian Iordachescu
    • 2
  1. 1.Queensland University of TechnologyBrisbaneAustralia
  2. 2.Shared Web Services Pty LtdSydneyAustralia

Personalised recommendations