An Agile Modeling Oriented Process for Logical Architecture Design

  • Nuno SantosEmail author
  • Jaime Pereira
  • Francisco Morais
  • Júlio Barros
  • Nuno Ferreira
  • Ricardo J. Machado
Conference paper
Part of the Lecture Notes in Business Information Processing book series (LNBIP, volume 318)


Stakeholders are crucial participants for eliciting requirements towards a new software solution. However, agreeing a common understanding among them is a complex task in a project’s initial phase when solution requirements and design need to be refined and/or are unknown. In order to not delay the initial phase and thus endanger the entire project, this paper proposes a process to elicit functional requirements and to design a candidate logical architecture (i.e., without refining information), called Agile Modeling Process for Logical Architectures (AMPLA). By eliciting a set of “just-enough” UML Use Cases, i.e., that includes at least the core requirements information, it is proposed the use of a logical architecture derivation method, the Four-Step-Rule-Set (4SRS). This approach is suitable in agile software development contexts, where the solution’s architecture is not known upfront.


Agile modeling, agile RE Incremental design Logical architectures “Just-enough” architecture 



This work was developed within the project UH4SP: Unified Hub 4 Smart Plants (Project ID 017871), under Portuguese National Grants Program for R&D projects (P2020 – SI IDT), COMPETE: POCI-01-0145-FEDER-007043 and FCT – Fundação para a Ciência e Tecnologia within the Project Scope: UID/CEC/00319/2013.


  1. 1.
    IIBA: Agile Extension to the BABOK Guide. International Institute of Business Analysis (2013)Google Scholar
  2. 2.
    Ambler, S.: Agile Modeling: Effective Practices for Extreme Programming and the Unified Process. Wiley, New York (2002)Google Scholar
  3. 3.
    Kruchten, P.: The 4 + 1 view model of architecture. IEEE Softw. 12, 42–50 (1995)CrossRefGoogle Scholar
  4. 4.
    Machado, R.J., Fernandes, J.M., Monteiro, P., Rodrigues, H.: Refinement of software architectures by recursive model transformations. In: Münch, J., Vierimaa, M. (eds.) PROFES 2006. LNCS, vol. 4034, pp. 422–428. Springer, Heidelberg (2006). Scholar
  5. 5.
    Regnell, B., Brinkkemper, S.: Market-driven requirements engineering for software products. In: Aurum, A., Wohlin, C. (eds.) Engineering and Managing Software Requirements, pp. 287–308. Springer, Heidelberg (2005). Scholar
  6. 6.
    Machado, R.J., Fernandes, J.M., Monteiro, P., Rodrigues, H.: Transformation of UML models for service-oriented software architectures (2005)Google Scholar
  7. 7.
    Grau, B.R., Lauenroth, K.: Requirements engineering and agile development - collaborative, just enough, just in time, sustainable. International Requirements Engineering Board (2014)Google Scholar
  8. 8.
    Ambler, S.: Agile Model driven development (AMDD). In: XOOTIC Mag., February 2007Google Scholar
  9. 9.
  10. 10.
    Clements, P., Ivers, J., Little, R., Nord, R., Stafford, J.: Documenting Software Architectures in an Agile World. DTIC Document (2003)Google Scholar
  11. 11.
    Erdogmus, H.: Architecture meets agility. IEEE Softw. 26, 2–4 (2009)CrossRefGoogle Scholar
  12. 12.
    Abrahamsson, P., Babar, M.A., Kruchten, P.: Agility and architecture: Can they coexist? Softw. IEEE 27, 16–22 (2010)CrossRefGoogle Scholar
  13. 13.
    Waterman, M., Noble, J., Allan, G.: How much architecture? Reducing the up-front effort. In: AGILE India, pp. 56–59. IEEE (2012)Google Scholar
  14. 14.
    Coplien, J.O., Bjørnvig, G.: Lean Architecture: for Agile Software Development. Wiley, Hoboken (2011)Google Scholar
  15. 15.
    Farhan, S., Tauseef, H., Fahiem, M.A.: Adding agility to architecture tradeoff analysis method for mapping on crystal. In: WRI World Congress on Software Engineering, WCSE 2009, pp. 121–125. IEEE (2009)Google Scholar
  16. 16.
    Kazman, R.: Foreword - bringing the two together: agile architecting or architecting for agile? In: Agile Software Architecture: Aligning Agile Processes and Software Architectures, pp. xxix–xxx (2013)Google Scholar
  17. 17.
    Cockburn, A.: Agile Software Development: the Cooperative Game. Pearson Education, Upper Saddle River (2006)Google Scholar
  18. 18.
    Madison, J.: Agile architecture interactions. Softw. IEEE 27, 41–48 (2010)CrossRefGoogle Scholar
  19. 19.
    Jeon, S., Han, M., Lee, E., Lee, K.: Quality attribute driven agile development. In: 9th International Conference on Software Engineering Research, Management and Applications (SERA), pp. 203–210. IEEE (2011)Google Scholar
  20. 20.
    Nord, R.L., Tomayko, J.E.: Software architecture-centric methods and agile development. Softw. IEEE 23, 47–53 (2006)CrossRefGoogle Scholar
  21. 21.
    Bellomo, S., Kruchten, P., Nord, R., Ozkaya, I.: How to agilely architect an agile architecture. Cut. IT J. 27(2), 12–17 (2014)Google Scholar
  22. 22.
    Nord, R.L., Ozkaya, I., Kruchten, P.: Agile in distress: architecture to the rescue. In: Dingsøyr, T., Moe, N.B., Tonelli, R., Counsell, S., Gencel, C., Petersen, K. (eds.) XP 2014. LNBIP, vol. 199, pp. 43–57. Springer, Cham (2014). Scholar
  23. 23.
    Costa, N., Santos, N., Ferreira, N., Machado, R.J.: Delivering user stories for implementing logical software architectures by multiple scrum teams. In: Murgante, B., Misra, S., Rocha, A.M.A.C., Torre, C., Rocha, J.G., Falcão, M.I., Taniar, D., Apduhan, B.O., Gervasi, O. (eds.) ICCSA 2014. LNCS, vol. 8581, pp. 747–762. Springer, Cham (2014). Scholar

Copyright information

© Springer International Publishing AG, part of Springer Nature 2018

Authors and Affiliations

  1. 1.CCG/ZGDV InstituteGuimarãesPortugal
  2. 2.School of Engineering, ALGORITMI CentreUniversity of MinhoGuimarãesPortugal
  3. 3.I2S Insurance Knowledge, SAPortoPortugal

Personalised recommendations