Refinement of Software Architectures by Recursive Model Transformations

  • Ricardo J. Machado
  • João M. Fernandes
  • Paula Monteiro
  • Helena Rodrigues
Part of the Lecture Notes in Computer Science book series (LNCS, volume 4034)


The main aim of this paper is to present how to refine software logical architectures by application of a recursive model-based transformation approach called 4SRS (four step rule set). It is essentially based on the mapping of UML use case diagrams into UML object diagrams. The technique is based on a sequence of steps that are inscribed in a tabular representation that is used to derive the software architecture for a focused part of the global system.


Software Architecture User Requirement Software Product Line Architectural Level Case 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.
    Bosch, J., Molin, P.: Software Architecture Design: Evaluation and Transformation. In: 7th IEEE Int. Conf. on the Engineering of Computer Based Systems (ECBS 1999), Nashville, Tennessee, U.S.A, pp. 4–10. IEEE CS Press, Los Alamitos (1999)Google Scholar
  2. 2.
    Machado, R.J., Fernandes, J.M., Monteiro, P., Rodrigues, H.: Transformation of UML Models for Service Oriented Software Architectures. In: 12th IEEE Int. Conf. on the Engineering of Computer Based Systems (ECBS 2005), Greenbelt, Maryland, U.S.A., pp. 173–182. IEEE CS Press, Los Alamitos (2005)Google Scholar
  3. 3.
    Fernandes, J.M., Machado, R.J., Santos, H.D.: Modeling Industrial Embedded Systems with UML. In: 8th IEEE/IFIP/ACM Int. Workshop on Hardware/Software Co Design (CODES 2000), San Diego, California, U.S.A., pp. 18–22. ACM Press, New York (2000)CrossRefGoogle Scholar
  4. 4.
    Fernandes, J.M., Machado, R.J.: From Use Cases to Objects: An Industrial Information Systems. In: 7th Int. Conf. on Object Oriented Information Systems (OOIS 2001), Calgary, Canada, pp. 319–328. Springer, Heidelberg (2001)Google Scholar
  5. 5.
    Jacobson, I., Christerson, M., Jonsson, P., Övergaard, G.: Object Oriented Software Engineering: A Use Case Driven Approach. Addison-Wesley, Reading (1992)MATHGoogle Scholar
  6. 6.
    Bragança, A., Machado, R.J.: Deriving Software Product Line’s Architectural Requirements from Use Cases: An Experimental Approach. In: 2nd Int. Workshop on Model Based Methodologies for Pervasive and Embedded Software (MOMPES 2005), Rennes, France, pp. 77–91 (June 2005)Google Scholar
  7. 7.
    Muthig, D., John, I., Anastasopoulos, M., Forster, T., Dörr, J., Schmid, K.: GoPhone: A Software Product Line in the Mobile Phone Domain. IESE Technical Report no. 025.04/E (2004)Google Scholar
  8. 8.
    Buschmann, F., Meunier, R., Rohnert, H., Sommerlad, P., Stal, M.: Pattern Oriented Software Architecture: A System of Patterns. John Wiley & Sons, Chichester (1996)Google Scholar
  9. 9.
    Ahlgren, R., Markkula, J.: Design Patterns and Organisational Memory in Mobile Application Development. In: 6th Int. Conf. on Product-Focused Software Process Improvement (PROFES 2005), Oulu, Finland, pp. 143–156. Springer, Heidelberg (2005)CrossRefGoogle Scholar
  10. 10.
    Fernandes, J.M., Machado, R.J.: System Level Object Orientation in the Specification and Validation of Embedded Systems. In: 14th SBC/IFIP/ACM Symposium on Integrated Circuits and System Design (SBCCI 2001), Pirenópolis, Brazil, pp. 8–13. IEEE Computer Society Press, Los Alamitos (2001)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2006

Authors and Affiliations

  • Ricardo J. Machado
    • 1
  • João M. Fernandes
    • 2
  • Paula Monteiro
    • 1
  • Helena Rodrigues
    • 1
  1. 1.Dept. of Information Systems 
  2. 2.Dept. of InformaticsUniversity of MinhoPortugal

Personalised recommendations