A Pattern-Based and Model-Driven Approach for Deriving IT System Functional Models from Annotated Business Models

  • Javier BerrocalEmail author
  • José García-Alonso
  • Cristina Vicente-Chicote
  • Juan Manuel Murillo
Conference paper


Companies increasingly demand IT systems to support (part of) their business. In order to maximize return on investment, these systems need to be perfectly aligned both with the business and with the legacy applications with which they will be integrated. In this vein, this paper presents a pattern-based and model-driven approach for deriving IT system functional models from annotated business models. First, we explain how to annotate the BPMN 2 business models with information useful for deriving the functionalities. Then, we introduce a set of patterns aimed to help identifying the functionalities and the relationships existing among them from the annotated business models. Finally, we present an ATL model transformation that, based on the previous patterns, allows us to obtain UML2 Use Case Diagrams.


Business-IT alignment Business Process Models Requirements Models Requirements Relationships Pattern-Based Model Transformations 



This research was supported by the Spanish Ministry of Science and Innovation under Project TIN2012-34945, and from the Department of Employment, Enterprise, and Innovation of the Government of Extremadura as part of Project GR10129.


  1. 1.
    Allweyer T (2010) BPMN 20: introduction to the standard for business process modeling. Books on Demand GmbH, NorderstedtGoogle Scholar
  2. 2.
    ATLAS team: ATLAS Transformation Language (ATL).
  3. 3.
    Baltzan P, Phillips A (2008) Business driven information systems, 2nd edn. McGraw-Hill, New YorkGoogle Scholar
  4. 4.
    Berrocal J, García-Alonso J, Murillo JM (2013) Modeling business and requirements relationships for architectural pattern selection. In: Kacprzyk J (ed) Software engineering research, management and applications 2013, Springer SCI. Springer, New YorkGoogle Scholar
  5. 5.
    BMM: Business Motivation Model.
  6. 6.
    BPMN: Business Process Modeling Notation 2.0.
  7. 7.
    Cardoso E, Almeida J, Guizzardi G (2009) Requirements engineering based on business process models: a case study. In: Enterprise distributed object computing conference workshops, 2009. EDOCW 2009. 13th, pp 320–327Google Scholar
  8. 8.
    Cockburn A (2000) Writing effective use cases, 1st edn. Addison-Wesley Longman, BostonGoogle Scholar
  9. 9.
    Dahlstedt AG, Persson A (2003) Requirements interdependencies—moulding the state of research into a research agenda. In: Ninth international workshop on requirements engineering: foundation for software quality (REFSQ 2003), pp 71–80Google Scholar
  10. 10.
    Dijkman RM, Joosten SMM (2002) Deriving use case diagrams from business process models. Tech. Rep. TR-CTIT-02-08, University of TwenteGoogle Scholar
  11. 11.
  12. 12.
    Gao S, Krogstie J (2009) A combined framework for development of business process support systems. In: Persson A, Stirna J, Aalst W, Mylopoulos J, Rosemann M, Shaw MJ, Szyperski C (eds) The practice of enterprise modeling, vol 39. Springer, Heidelberg, pp 115–129CrossRefGoogle Scholar
  13. 13.
  14. 14.
    Kotonya G, Sommerville I (1998) Requirements engineering: processes and techniques, Worldwide series in computer science. Wiley, ChichesterGoogle Scholar
  15. 15.
    Perez-Castillo R (2012) Marble: Modernization approach for recovering business processes from legacy information systems. In: Software Maintenance (ICSM), 2012 28th IEEE International Conference on, pp 671–676Google Scholar
  16. 16.
    Siqueira F, Silva P (2011) Transforming an enterprise model into a use case model using existing heuristics. In: Model-driven requirements engineering workshop, pp 21–30Google Scholar
  17. 17.
    Stahl T, Voelter M, Czarnecki K (2006) Model-driven software development: technology, engineering management. Wiley, ChichesterGoogle Scholar
  18. 18.
    Stolfa S, Vondrak I (2006) Mapping from business processes to requirements specification. Tech. rep., CUniversitat TrierGoogle Scholar
  19. 19.
    Traetteberg H, Krogstie J (2009) Enhancing the usability of BPM-solutions by combining process and user-interface modelling. In: Stirna J, Persson A, Aalst W, Mylopoulos J, Rosemann M, Shaw MJ, Szyperski C (eds) The practice of enterprise modeling, vol 15. Springer, Berlin, pp 86–97CrossRefGoogle Scholar
  20. 20.
    Ullah A, Lai R (2011) Modeling business goal for business/it alignment using requirements engineering. Journal of Computer Information Systems 51(3):21–28Google Scholar
  21. 21.
    de la Vara J, Sánchez J (2009) BPMN-based specification of task descriptions: Approach and lessons learnt. In: Glinz M, Heymans P (eds) Requirements Engineering: Foundation for Software Quality, vol 5512. Springer, Berlin, pp 124–138Google Scholar
  22. 22.
    Wiegers KE (2003) Software requirements, 2nd edn. Microsoft, RedmondGoogle Scholar

Copyright information

© Springer International Publishing Switzerland 2014

Authors and Affiliations

  • Javier Berrocal
    • 1
    Email author
  • José García-Alonso
    • 1
  • Cristina Vicente-Chicote
    • 1
  • Juan Manuel Murillo
    • 1
  1. 1.University of ExtremaduraCáceresSpain

Personalised recommendations