Skip to main content
Log in

Automating Support for Software Evolution in UML

  • Published:
Automated Software Engineering Aims and scope Submit manuscript

Abstract

Disciplined support for evolution of software artifacts is important in all phases of the software life-cycle. In order to achieve this support, a uniform underlying foundation for software evolution is necessary. While, in the past, reuse contracts have been proposed as such a formalism in a number of different domains, this paper generalises the formalism, and integrates it into the UML metamodel. As such, support for evolution becomes readily available for many kinds of UML models, ranging from requirements to the implementation phase.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Similar content being viewed by others

References

  • Bohner, S.A. and Arnold, R.S. 1996. Software Change Impact Analysis. IEEE Press.

  • De Hondt, K. 1998. A novel approach to architectural recovery in evolving object-oriented systems. Ph.D. Dissertation, Department of Computer Science, Vrije Universiteit Brussel, Belgium.

    Google Scholar 

  • D'Hondt, M. 1998. Managing evolution of changing software requirements. Dissertation, Department of Computer Science, Vrije Universiteit Brussel, Belgium.

    Google Scholar 

  • Ecklund, E.F., Jr. Delcambre, L.M.L., and Freiling, M.J. 1996. Change cases: Use cases that identify future requirements. In Proc.'96.ACM SIGPLAN Notices, 31(10):342–358.

    Google Scholar 

  • Evans, A., France, R., Lano, K., and Rumpe, B. 1999. The UML as a formal modelling notation. In Selected Papers of <<UML>>'98 International Workshop. Lecture Notes in Computer Science, Vol. 1618, Springer-Verlag, pp. 336–348.

    Google Scholar 

  • Gogolla, M. and Richters, M. 1998. On constraints and queries in UML. The Unified Modeling Language— Technical Aspects and Applications. Physica-Verlag.

  • Hamie, A., Howse, J., Kent, S., Mitchell, R., and Civello, F. 1999. Reflections on the object constraint language. In Selected Papers of <<UML>>'98 International Workshop. Lecture Notes in Computer Science, Vol. 1618, Springer-Verlag, pp. 162–172.

    Google Scholar 

  • Helm, R., Holland, I.M., and Gangopadhyay, D. 1990. Contracts: specifying behavioral compositions in objectoriented systems. In Proc.OOPSLA/ECOOP'90.ACM SIGPLAN Notices, 25(10):169–180.

    Google Scholar 

  • Jacobson, I., Griss, M., Jonsson, P. 1997. Making the reuse business work. IEEE Computer.

  • Kent, S., Evans, A., and Rumpe, B. 1999. UML semantics FAQ. In ECOOP '99 Workshop Reader. Lecture Notes in Computer Science, Springer-Verlag.

  • Kiczales, G. and Lamping. J. 1992. Issues in the design and documentation of class libraries. In Proc.OOPSLA'92. ACM SIGPLAN Notices, 27(10):435–451.

    Google Scholar 

  • Lamping, J. 1993. Typing the specialisation interface. In Proc.OOPSLA'93.ACMSIGPLAN Notices, 28(10):201–214.

    Google Scholar 

  • Lucas, C. 1997. Documenting reuse and evolution with reuse contracts. Ph.D. Dissertation, Department of Computer Science, Vrije Universiteit Brussel, Belgium.

    Google Scholar 

  • Mens, T. 1999. A formal foundation for object-oriented software evolution. Ph.D. Dissertation, Department of Computer Science, Vrije Universiteit Brussel, Belgium.

    Google Scholar 

  • Mens, T., Lucas, C., and Steyaert, P. 1999. Supporting reuse and evolution of UML models. In Selected Papers of <<UML>>'98 International Workshop. Lecture Notes in Computer Science, Vol. 1618, Springer-Verlag, pp. 378–392.

    Google Scholar 

  • Mezini, M. 1997. Maintaining the consistency of class libraries during their evolution. In Proc.OOPSLA'97.ACM SIGPLAN Notices, 32(10):1–21.

    Google Scholar 

  • Object Management Group. 1999. Unified modeling language specification version 1.3. OMG Document ad/99–06–08.

  • Opdyke,W.F. 1992. Refactoring object-oriented frameworks. Ph.D. Dissertation, University of Illinois at Urbana-Champaign. Technical Report UIUC-DCS-R–92–1759.

  • Övergaard, G. and Palmkvist, K. 1999. A formal approach to use cases and their relationships. In Selected Papers of <<UML>>'98 International Workshop. Lecture Notes in Computer Science, Vol. 1618, Springer-Verlag, pp. 406–418.

    Google Scholar 

  • Richters, M. and Gogolla, M. 1998. On formalizing the UML object constraint language OCL. In Proc.Int.Conf. Conceptual Modeling, Springer-Verlag.

  • Romero, M. 1999. Managing architectural evolution with reuse contracts. Masters Dissertation, Department of Computer Science, Vrije Universiteit Brussel, Belgium.

    Google Scholar 

  • Rubin, K.S. and Goldberg, A. 1992. Object behaviour analysis. Communications of the ACM (Special Issue on Object-Oriented Methodologies), 35(9):48–62.

    Google Scholar 

  • Steyaert, P., Lucas, C., Mens, K., and D'Hondt, T. 1996. Reuse contracts: Managing the evolution of reusable assets. In Proc.OOPSLA '96.ACM SIGPLAN Notices, 31(10):268–286.

    Google Scholar 

  • Westfechtel, B. 1991. Structure-oriented merging of revisions of software documents. In Proc.3rd Int.Workshop on Software Configuration Management, ACM Press, pp. 68–79.

Download references

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

About this article

Cite this article

Mens, T., D'Hondt, T. Automating Support for Software Evolution in UML. Automated Software Engineering 7, 39–59 (2000). https://doi.org/10.1023/A:1008765200695

Download citation

  • Issue Date:

  • DOI: https://doi.org/10.1023/A:1008765200695

Navigation