A Problem Frame-Based Approach to Evolvability: The Case of the Multi-translation

  • Gianna Reggio
  • Egidio Astesiano
  • Filippo Ricca
  • Maurizio Leotta
Part of the Lecture Notes in Computer Science book series (LNCS, volume 6662)


The problem frame approach allows to precisely pin the software development problems before starting to work on them, thus avoiding to solve the wrong problems. Furthermore, the problem frames allow to develop tailored methods and schematic solutions to handle the tasks required to solve the corresponding problems. In this paper we adopt this approach to study the problem of developing a large class of software systems able to translate in different ways some inputs in outputs (e.g., hybrid mail or big brothers filtering digital communications for suspicious words). Our interest in this kind of systems has been prompted by a cooperation with a big company producing systems of this kind and by their search of techniques and approaches to handle predictable and unpredictable changes. We want to investigate how and if the problem frame based approach will help to master the aspects relative to predictable and unpredictable changes in the context, in the domain and in the requirements. We thus present the Multi-Translation Frame.


Problem Frame Translation Function Business Process Modeling Notation Unpredictable Change Translation Block 
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.
    Astesiano, E., Reggio, G.: Knowledge Structuring and Representation in Requirement Specification. In: Proceedings 14th International Conference on Software Engineering and Knowledge Engineering, pp. 143–150. ACM Press, New York (2002)Google Scholar
  2. 2.
    Astesiano, E., Reggio, G.: Towards a well-founded UML-based development method. In: 1st International Conference on Software Engineering and Formal Methods, Brisbane, Australia, September 22-27 (2003)Google Scholar
  3. 3.
    Astesiano, E., Reggio, G.: Tight Structuring for Precise UML-Based Requirement Specifications. In: Wirsing, M., Knapp, A., Balsamo, S. (eds.) RISSEF 2002. LNCS, vol. 2941, pp. 16–34. Springer, Heidelberg (2004)CrossRefGoogle Scholar
  4. 4.
    Bastani, B.: A requirements analysis framework for open systems requirements engineering. SIGSOFT Software Engineering Notes 32(2), 47–55 (2007)CrossRefGoogle Scholar
  5. 5.
    Beck, K., Andres, C.: Extreme Programming Explained: Embrace Change, 2nd edn. Addison-Wesley, Boston (2004)Google Scholar
  6. 6.
    Boness, K., Harrison, R.: Goal sketching: Towards agile requirements engineering. In: Proceedings of International Conference on Software Engineering Advances, Cap Esterel, pp. 71–77 (2007)Google Scholar
  7. 7.
    Brcina, R., Bode, S., Riebisch, M.: Optimization process for maintaining evolvability during software evolution. In: IEEE International Conference on the Engineering of Computer-Based Systems, pp. 196–205 (2009)Google Scholar
  8. 8.
    Breivold, H.P.: Software Architecture evolution and software evolvability, PhD thesis. Mälardalen University Press Licentiate Theses No. 97 (2009)Google Scholar
  9. 9.
    Business Process Management Initiative (BPMI). Business Process Modeling Notation (BPMN) (2004), (website, last access December 13, 2007)
  10. 10.
    Choppy, C., Reggio, G.: A UML-Based Approach for Problem Frame Oriented Software Development. Journal of Information and Software Technology (2005)Google Scholar
  11. 11.
    Choppy, C., Reggio, G.: Requirements capture and specification for enterprise applications: a UML based attempt. In: Han, J., Staples, M. (eds.) Proc. ASWEC 2006, pp. 19–28. IEEE Computer Society, Los Alamitos (2006)Google Scholar
  12. 12.
    Clements, P., Bass, L., Kazman, R., Abowd, G.: Predicting software quality by architecture-level evaluation. In: Proceedings of the Fifth International Conference on Software Quality, Austin, Texas, vol. 5, pp. 485–497. Software Engineering Institute (1995)Google Scholar
  13. 13.
    Erl, T.: SOA Principles of Service Design. The Prentice Hall Service-Oriented Computing Series from Thomas Erl (2007)Google Scholar
  14. 14.
    Ganter, B., Wille, R.: Formal Concept Analysis: Mathematical Foundations. Springer, New York (1997)zbMATHGoogle Scholar
  15. 15.
    Jackson, M.: Problem Frames: Analyzing and Structuring Software Development Problems. Addison-Wesley, Reading (2001)Google Scholar
  16. 16.
    Kazman, R., Abowd, G., Bass, L., Clements, P.: Scenario-based analysis of software architecture. IEEE Software 13(6), 47–55 (1996), doi:10.1109/52.542294CrossRefGoogle Scholar
  17. 17.
    Moore, K.E., Kirshenbaum, E.R.: Building Evolvable Systems: The ORBlite Project (1997), (website, last access November 7, 2010)
  18. 18.
    Leotta, M., Ricca, F., Reggio, G., Astesiano, E.: Comparing the maintainability of two alternative architectures of a postal system: SOA vs. non-SOA. In: Proceedings of 15th European Conference on Software Maintenance and Reengineering (CSMR 2011), Oldenburg, Germany, March 1-4, pp. 317–320 (2011), DOI:
  19. 19.
    Parnas, D.L.: On the criteria to be used in decomposing systems into modules. Commun. ACM 15, 1053–1058 (1972)CrossRefGoogle Scholar
  20. 20.
    Parnas, D.L.: Software aging. In: Proceedings of the 16th International Conference on Software Engineering, Sorrento, Italy, pp. 279–287. IEEE Computer Society Press, Los Alamitos (1994)CrossRefGoogle Scholar
  21. 21.
    Schmidt, V.A.: Using service oriented architecture for evolvable software systems. In: 11th International Command and Control Technology Symposium (2006)Google Scholar
  22. 22.
    Shiri, M., Hassine, J., Rilling, J.: A requirement level modification analysis support framework. In: IEEE International Workshop on Software Evolvability, pp. 67–74 (2007)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Gianna Reggio
    • 1
  • Egidio Astesiano
    • 1
  • Filippo Ricca
    • 1
  • Maurizio Leotta
    • 1
  1. 1.DISIUniversità di GenovaItaly

Personalised recommendations