Modeling Business and Requirements Relationships for Architectural Pattern Selection

  • Javier BerrocalEmail author
  • José García-Alonso
  • Juan Manuel Murillo
Conference paper
Part of the Studies in Computational Intelligence book series (SCI, volume 496)


In analysis of the business and the system requirements, the identified elements are modeled using notations that fully describe their characteristics. Nevertheless, implicit relationships often exist between different types of elements that subsequently have to be identified and explicitly represented during the design of the system. This requires an in-depth analysis of the generated models on behalf of the architect in order to interpret their content. Misunderstandings that take place during this stage can lead to an incorrect design and difficult compliance with the business goals. Here we present a series of profiles that explicitly represent these relationships during the initial development phases, and which are derived to the system design. They are reusable by the architect, thereby decreasing the risk of their misinterpretation.


Business Process Modeling Business System Requirement Sequence Diagram Activity Diagram 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.


  1. 1.
    Aburub, F., Odeh, M., Beeson, I.: Modelling non-functional requirements of business processes. Inf. Softw. Technol. 49, 1162–1171 (2007), doi:10.1016/j.infsof.2006.12.002CrossRefGoogle Scholar
  2. 2.
    Avgeriou, P., Grundy, J., Hall, J.G., Lago, P., Mistrík, I. (eds.): Relating Software Requirements and Architectures. Springer (2011)Google Scholar
  3. 3.
    Bachmann, F., Bass, L., Klein, M., Shelton, C.: Designing software architectures to achieve quality attribute requirements. IEE Proceedings Software 152(4), 153–165 (2005), doi:10.1049/ip-sen:20045037CrossRefGoogle Scholar
  4. 4.
    Berrocal, J., García-Alonso, J., Murillo, J.M.: Patrones para la extracción de casos de uso a partir de procesos de negocio. In: II Taller de Procesos de Negocio e Ingenierć-a de Servicios, pp. 1–11 (2009)Google Scholar
  5. 5.
    Berrocal, J., García-Alonso, J., Murillo, J.M.: Facilitating the selection of architectural patterns by means of a marked requirements model. In: Babar, M.A., Gorton, I. (eds.) ECSA 2010. LNCS, vol. 6285, pp. 384–391. Springer, Heidelberg (2010)CrossRefGoogle Scholar
  6. 6.
    BMM: Business motivation model version 1.1,
  7. 7.
    BPMN: Business process modeling notation version 2.0,
  8. 8.
    Cardoso, E., Almeida, J., Guizzardi, G.: Requirements engineering based on business process models: A case study. In: 13th Enterprise Distributed Object Computing Conference Workshops, EDOCW 2009, pp. 320–327 (2009), doi:10.1109/EDOCW.2009.5331974Google Scholar
  9. 9.
    Chung, L., do Prado Leite, J.C.S.: On non-functional requirements in software engineering. In: Borgida, A.T., Chaudhri, V.K., Giorgini, P., Yu, E.S. (eds.) Conceptual Modeling: Foundations and Applications. LNCS, vol. 5600, pp. 363–379. Springer, Heidelberg (2009)CrossRefGoogle Scholar
  10. 10.
    Cockburn, A.: Writing Effective Use Cases, 1st edn. Addison-Wesley Longman Publishing Co., Inc., Boston (2000)Google Scholar
  11. 11.
    Czarnecki, K., Helsen, S., Eisenecker, U.W.: Formalizing cardinality-based feature models and their specialization. Software Process: Improvement and Practice 10(1), 7–29 (2005)CrossRefGoogle Scholar
  12. 12.
    Dijkman, R.M., Joosten, S.M.M.: Deriving use case diagrams from business process models. Tech. Rep. TR-CTIT-02-08, University of Twente (2002)Google Scholar
  13. 13.
    Dörr, J.: Elicitation of a complete set of non-functional requirements. Ph.D. thesis, University of Kaiserslautern (2011)Google Scholar
  14. 14.
    García-Alonso, J., Berrocal, J., Murillo, J.M.: Modelado de la variabilidad en arquitecturas multicapa. Jornadas de Ingeniera del Software y Bases de Datos (JISBD), 895–900 (2011)Google Scholar
  15. 15.
    Grau, G., Franch, X., Maiden, N.A.M.: Prim: An i*-based process reengineering method for information systems specification. Inf. Softw. Technol. 50(1-2), 76–100 (2008)CrossRefGoogle Scholar
  16. 16.
    Harrison, N.B., Avgeriou, P.: Leveraging architecture patterns to satisfy quality attributes. In: Oquendo, F. (ed.) ECSA 2007. LNCS, vol. 4758, pp. 263–270. Springer, Heidelberg (2007)CrossRefGoogle Scholar
  17. 17.
    Harrison, N.B., Avgeriou, P.: How do architecture patterns and tactics interact? a model and annotation. Journal of Systems and Software 83(10), 1735–1758 (2010)CrossRefGoogle Scholar
  18. 18.
    International Standard Organization (ISO/IEC): Informational technology – product quality: Quality model. International Standard ISO/IEC 9126 (2001)Google Scholar
  19. 19.
    Kim, S., Kim, D.K., Lu, L., Park, S.: Quality-driven architecture development using architectural tactics. J. Syst. Softw. 82, 1211–1231 (2009), doi:10.1016/j.jss.2009.03.102CrossRefGoogle Scholar
  20. 20.
    OpenUP: Open unified process (2013),
  21. 21.
    Pavlovski, C.J., Zou, J.: Non-functional requirements in business process modeling. In: Proceedings of the Fifth Asia-Pacific Conference on Conceptual Modelling, APCCM 2008, vol. 79, pp. 103–112. Australian Computer Society, Inc., Darlinghurst (2008)Google Scholar
  22. 22.
    Rodríguez, A., de Guzmán, I.G.R., Fernández-Medina, E., Piattini, M.: Semi-formal transformation of secure business processes into analysis class and use case models: An mda approach. Information & Software Technology 52(9), 945–971 (2010)CrossRefGoogle Scholar
  23. 23.
    Siqueira, F., Silva, P.: Transforming an enterprise model into a use case model using existing heuristics. In: Model-Driven Requirements Engineering Workshop (MoDRE), pp. 21–30 (2011)Google Scholar
  24. 24.
    Stolfa, S., Vondrak, I.: Mapping from business processes to requirements specification. Tech. rep., CUniversitat Trier (2006)Google Scholar
  25. 25.
    Traetteberg, H., Krogstie, J.: Enhancing the usability of bpm-solutions by combining process and user-interface modelling. In: Stirna, J., Persson, A. (eds.) PoEM 2008. LNBIP, vol. 15, pp. 86–97. Springer, Heidelberg (2009)CrossRefGoogle Scholar
  26. 26.
    Ullah, A., Lai, R.: Modeling business goal for business/it alignment using requirements engineering. Journal of Computer Information Systems 51(3), 21–28 (2011)Google Scholar
  27. 27.
    UML: Unified modeling language,
  28. 28.
    de la Vara, J.L., Sánchez, J.: BPMN-based specification of task descriptions: Approach and lessons learnt. In: Glinz, M., Heymans, P. (eds.) REFSQ 2009. LNCS, vol. 5512, pp. 124–138. Springer, Heidelberg (2009)CrossRefGoogle Scholar

Copyright information

© Springer International Publishing Switzerland 2014

Authors and Affiliations

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

Personalised recommendations