The STUDIA UNIVERSITATIS BABE┼×-BOLYAI issue article summary

The summary of the selected article appears at the bottom of the page. In order to get back to the contents of the issue this article belongs to you have to access the link from the title. In order to see all the articles of the archive which have as author/co-author one of the authors mentioned below, you have to access the link from the author's name.

    STUDIA INFORMATICA - Issue no. 1 / 2014  

  Abstract:   Separation of concerns was always an important factor in designing easily maintainable and evolvable software systems. However, practice has shown that it is not easy to clearly separate all the concerns from a software system in analysis, design and implementation phases. Using just one programming paradigm most concerns can be clearly separated, but there are still a few concerns whose design and implementation is entangled with other concerns. New programming paradigms that try to complement the existing ones by providing new ways for a better separation of concerns have been developed. Aspect oriented paradigm is one of the new paradigms. Although the number of languages supporting aspect oriented programming has increased, there is no generally accepted notation for aspects in UML. In this paper we provide an analysis of the existing UML-based notation for aspects in the class diagram using a set of comparison criteria.

2010 Mathematics Subject Classi fication. 68N19, 68N99.1998 CR Categories and Descriptors. D.2.2[Software Engineering]: Design Tools andTechniques - Computer-aided software engineering; D.1.m [Software]: Programming Techniques - Miscellaneous.

Key words and phrases. aspect oriented paradigm, design, UML class diagram.
      Back to previous page