Evolution of object behavior using context relations

Seiter, Linda M.; Palsberg, Jens; Lieberherr, Karl

doi:10.1109/32.663999

Cited by 52 publications

(7 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The structure describes how the different parts in a software system are arranged, and the behaviour of a system describes the way in which it functions or operates. According to [SPL98], objects are dynamic entities, changing their state and behaviour throughout their existence. Object-oriented design models such as UML (Unified Modelling Language) [UML], provide several diagrams for capturing the static and dynamic aspects of a particular domain.…”

Section: Complementariness With Other Techniquesmentioning

confidence: 99%

Architectural description

2019

The Hypogeum of the Aurelii

View full text Add to dashboard Cite

Parameterization: This ADL allows any part of the description of a type to be replaced with a placeholder, which is then filled with a parameter when the type is instantiated. So the type of a port or role, a computation, the name of an interface are all parameterizable. For example, in the Unix pipe-filter style, all components have one input, named Stdin, and two outputs, named Stdout and Stderr. The interface to all Unix filters is the same. But the computation performed by each Unix filter is different. We can describe the Unix filter as a parameterized component type, as follows:

show abstract

Section: Complementariness With Other Techniquesmentioning

confidence: 99%

Architectural description

2019

The Hypogeum of the Aurelii

View full text Add to dashboard Cite

show abstract

“…A new relation between classes, called a context relation, is proposed in [Seiter98]. Through a context relation a class (i.e., context class) can override the behavior of several classes (i.e., base classes).…”

Section: Related Workmentioning

confidence: 99%

Integration of Independently Developed Components through Aliased Multi-Object Type Widening.

Jôrgensen¹

2004

JOT

View full text Add to dashboard Cite

The aim of component-based software development is to assemble applications from existing components, writing as little extra code as possible. For programmers, the assembling of applications from existing components should increase reuse, thus allowing them to concentrate on value-added tasks and to produce high-quality software within a shorter time. For users, component-based software development promises tailor made functionality from the customization of ready-made components, and that at a lower cost than applications developed from scratch. However, this ideal scenario has yet to become reality! Today, the majority of all applications are still developed from scratch, and there are still relatively few ready-made components that can be easily reused in the construction of new applications. In this paper, we argue that the present situation is primary caused by the conventional object-oriented programming languages in which we try to assemble components. When Assembling independently developed components in a conventional object-oriented programming language, it leads to a number of complex integration problems. We describe these problems in turn before we discuss how the new language features of Lasagne/J, an extension of the Java programming language, can be used to tackle them.

show abstract

“…Seiter et al [23] proposed a context relation to link the static and dynamic aspects of a class. While supporting multiple dynamic collaboration schemes, the approach is based on dynamically altering a class definition for the duration of a method invocation, thus affecting all class instances, whereas we propose a model for scoping the different collaboration schemes, thus we can be selective as to which objects are affected.…”

Section: Related Workmentioning

confidence: 99%

Integrating independent components with on-demand remodularization

MeziniMira

OstermannKlaus

2002

SIGPLAN Not.

View full text Add to dashboard Cite

This paper proposes language concepts that facilitate the separation of an application into independent reusable building blocks and the integration of pre-build generic software components into applications that have been developed by third party vendors. A key element of our approach are ondemand remodularizations, meaning that the abstractions and vocabulary of an existing code base are translated into the vocabulary understood by a set of components that are connected by a common collaboration interface. This general concept allows us to mix-and-match remodularizations and components on demand.

show abstract

Evolution of object behavior using context relations

Cited by 52 publications

References 15 publications

Architectural description

Architectural description

Integration of Independently Developed Components through Aliased Multi-Object Type Widening.

Integrating independent components with on-demand remodularization

Contact Info

Product

Resources

About