| T. Mens and T. Tourwe. A declarative evolution framework for objectoriented design patterns. In Proceedings of Int. Conf. on Software Maintenance. IEEE Computer Society Press, 2001. |
No context found.
Tom Mens and Tom Tourwe. A Declarative Evolution Framework for ObjectOriented Design Patterns. In Proc. Int. Conf. Software Maintenance, 2001.
No context found.
T. Mens and T. Tourw e. A Declarative Evolution Framework for Object-Oriented Design Patterns. In Proc. Int. Conf. Software Maintenance. IEEE Computer Society, 2001.
.... (including naming and programming conventions [MMW 2001] design pattern extraction [W 1998] type inferencing, UML model extraction, architectural views [MW 1999] Declaratively generate code (including source code templates, aspect oriented programming, design pattern code generation [MT 2001], Support software evolution (including refactoring, software merging [MT 2001] During the second part of the presentation, we take a closer look at the technical details. We show how high level software artifacts can be expressed in terms of logic facts and rules. For this, we ....
.... [W 1998] type inferencing, UML model extraction, architectural views [MW 1999] Declaratively generate code (including source code templates, aspect oriented programming, design pattern code generation [MT 2001] Support software evolution (including refactoring, software merging [MT 2001], During the second part of the presentation, we take a closer look at the technical details. We show how high level software artifacts can be expressed in terms of logic facts and rules. For this, we require that the logic meta programming language lives in symbiosis with the ....
Tom Mens, Tom Tourwe. A Declarative Evolution Framework for Object-Oriented Design Patterns, Proc. Int. Conf. Software Maintenance, Barcelona, 2001.
....in SOUL . Verification of source code (e.g. conformance checking, coding conventions [MMW01] design models [Wuy98] architectural description [Men00a] Extraction of information out of source code (e.g. code metrics [MD01] Transformation of source code (e.g. refactoring,translation,evolution [MT01]. Generation of source code [Wuy01] Aspect Oriented Programming [Bri00] DVD99] 3.4 Logic Meta Programming with SOUL As we already discussed in a previous section, a strong interaction is possible between SOUL and the language it is implemented in: Smalltalk. This is not a coincidence. ....
T. Mens and T. Tourwe. A declarative evolution framework for object-oriented design patterns. In Int. Conf. Software Maintenance, 2001.
.... programs in a straightforward and intuitive way [31] The technique has already been used to check and enforce programming conventions and best practice patterns [17] to detect design pattern instances in existing source code [30] to specify and reason about (the evolution of) design patterns [18], 27] and to check conformance of a software implementation to its intended architecture [16] The LMP technique is independent of the particular base language that is used. Up till now, we experimented with both Smalltalk and Java as the base language [31] 8] All experiments reported on in ....
Tom Mens and Tom Tourw e. A Declarative Evolution Framework for Object-Oriented Design Patterns. In Proc. Int. Conf. Software Maintenance, pages 570--579. IEEE Computer Society, 2001.
....and which can be applied on its instances. Refactorings can be combined to form design pattern transformations that can be used to evolve design pattern instances in such a way that their constraints are not violated (similar to the design pattern transformations provided by Florijn [FMvW97] and [MT01] When such a design pattern transformation adds a class to a particular class hierarchy, for example, it will consult the documentation to check the design pattern instances in which this class will participate. Based on this information, it can derive which methods this class should ....
....Constraints To alleviate design drift as much as possible, to guide a developer when manually evolving a framework and to support unanticipated evolution up to a certain extent, we will explicitly document the design constraints of the framework. Design patterns can also be used for this purpose [MT01] A design pattern constrains the implementation of a framework. Participants in a design pattern instance should adhere to the specific relationships, collaborations and interactions defined by the design pattern. When a new class is added to the framework, for example, it will participate in ....
[Article contains additional citation context not shown here]
Tom Mens and Tom Tourwe. A Declarative Evolution Framework for ObjectOriented Design Patterns. In Proc. Int. Conf. Software Maintenance, 2001.
....general purpose aspect language which allows to express many kinds of aspects as well as combinations and interactions between them. The latter becomes more complex when the aspects are implemented in di#erent aspect specific languages. Our approach to AOP is based on logic metaprogramming (LMP) [20, 21, 14, 12, 13]. In a previous paper [4] we explored the use of LMP as an open and extensible aspectweaver mechanism that facilitates the specialization of a general purpose aspect language and, as such, facilitates the building of aspect specific languages (ASLs) In this paper we focus on the combinations and ....
T. Mens and T. Tourwe. A declarative evolution framework for object-oriented design patterns. In Proceedings of Int. Conf. on Software Maintenance. IEEE Computer Society Press, 2001.
No context found.
T. Mens and T. Tourwe. A declarative evolution framework for objectoriented design patterns. In Proceedings of Int. Conf. on Software Maintenance. IEEE Computer Society Press, 2001.
No context found.
T. Mens and T. Tourwe, "A Declarative Evolution Framework for Object-Oriented Design Patterns," In Software Maintenance, IEEE Computer Society, 2001.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC