Extending Object-Oriented Frameworks with Aspects for Enabling Automatic Support for Domain-Specic Modeling

In the context of framework-based development, Domain-Specic Modeling (DSM) is a paradigm that raises the level of abstraction of application engineering. Using a Domain-Specic Modeling Language (DSML), applications are described by domain concepts in a model from which the application code is generated. This paper presents an approach for automating the construction of a DSM infrastructure for an object-oriented framework, where a DSML and a code generator for building applications are automatically derived. The approach is able to signicantly reduce the cost of adopting and evolving a DSM infrastructure. The high degree of automation is possible by enhancing frameworks with an additional layer of specialization modules, relying on our previous work on framework specialization aspects. The approach was implemented in our ALFAMA tool, and validated by a case study on the Eclipse RC

Designing a Framework by Stepwise Generalization

Frameworks are class collections that capture the common aspects of applications in a certain problem domain. It is argued that conventional object-oriented design methods do not suit well to frameworks. As an alternative, we suggest a two-phase design method. The first phase is a stepwise generalization of a problem to its most general form. The second phase proceeds in the opposite direction, giving an implementation for every generalization level. The implementation of a certain level can be regarded as a framework for implementing the next more specific level. The main advantage of our method is that it enhances the generality (and therefore reusability) of the framework architecture, and explains the design decisions in the simplest possible context. As a case study, we describe a framework supporting the analysis of formal languages. 1 Introduction A framework is a collection of collaborating classes that captures the applicationindependent behaviour of systems in a particular ..

Viewing Object-Oriented Programs through Scenario Diagrams

Scenario diagrams are a well-known graphical notation for illustrating a sequence of communication events occurring during a particular run of an objectoriented system. Traditionally scenario diagrams are used in the analysis and design phases of software development to visualize the expected dynamic behavior of a system. We show how scenario diagrams can be used reversely as the basis of understanding existing systems. A prototype tool has been implemented with the ability to automatically produce scenario diagrams for existing systems and to scan these diagrams in various ways. The tool has additional properties typical for highlevel debuggers, program profilers, and program animators. Categories and Subject Descriptors: D.1.5 [Object-Oriented Programming], D.2.5 [Testing and Debugging], D.2.6 [Programming Environments] Key Words and Phrases: Object-orientation, program visualization, scenarios 1 Introduction Scenario diagrams (or event trace diagrams [10], interaction diagrams [3]) ..