<i>N</i>
            degrees of separation

Tarr, Peri; Ossher, Harold; Harrison, William; Sutton, Stanley M.

doi:10.1145/302405.302457

Cited by 739 publications

(34 citation statements)

References 19 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Feature-oriented programming (FOP) (Batory et al [2004], Kästner et al [2008) is a compositional approach for implementing SPLs in which code fragments are associated with product features and assembled to implement a particular configuration of features. Other compositional approaches use aspects (Kästner et al [2007], Aracic et al [2006]), mixins (Smaragdakis and Batory [2002]), hyperslices (Tarr et al [1999]) or traits (Ducasse et al [2006]) to implement product line variability (see Lopez-Herrejon et al [2005] as well as Bettini et al [2013c] for a discussion of some of them with respect to FOP).…”

Section: Feature-oriented Programming (Fop)mentioning

confidence: 99%

A core calculus for dynamic delta-oriented programming

et al. 2017

View full text Add to dashboard Cite

Delta-oriented programming (DOP) is a flexible approach to the implementation of software product lines (SPLs). Delta-oriented SPLs consist of a code base (a set of delta modules encapsulating changes to object-oriented programs) and a product line declaration (providing the connection of the delta modules with the product features). In this paper, we present a core calculus that extends DOP with the capability to switch the implemented product configuration at runtime. A dynamic delta-oriented SPL is a delta-oriented SPL with a dynamic reconfiguration graph that specifies how to switch between different feature configurations. Dynamic DOP supports also (unanticipated) software evolution such that at runtime, the product line declaration, the code base and the dynamic reconfiguration graph can be changed in any (unanticipated) way that preserves the currently running product, which is essential when evolution affects existing features. The type system of our dynamic DOP core calculus ensures that the dynamic reconfigurations lead to type safe products and do not cause runtime type errors.

show abstract

Section: Feature-oriented Programming (Fop)mentioning

confidence: 99%

A core calculus for dynamic delta-oriented programming

et al. 2017

View full text Add to dashboard Cite

show abstract

“…This vision is built on the fundamental principles of separation of concerns (SoC) [6], i.e., the ability to focus on a concern while temporarily forgetting other ones, as well as encapsulation and information hiding [26], but also on more recent advances in software engineering regarding model-driven engineering (MDE, e.g., OMG's MDA [25]) and how to encapsulate crosscutting concerns with aspect technology [31]. While the latter two are relatively young, enabling technologies for this vision, SoC, encapsulation, and information hiding have a long history of success from procedures (hiding algorithms behind signatures) to objects (hiding data and associated behavior behind interfaces) and from components (hiding collaborating objects behind provided and required interfaces) to aspects (encapsulating crosscutting concerns).…”

Section: Vision: Concern-oriented Requirements Reusementioning

confidence: 99%

A vision for generic concern-oriented requirements reuse<sup>re@21</sup>

Mussbacher

Kienzle

2013

2013 21st IEEE International Requirements Engineering Conference (RE)

View full text Add to dashboard Cite

Reuse is a powerful tool for improving the productivity of software development. The paper puts forward arguments in favor of generic requirements reuse rooted in the vision that effectiveness requires a focus on coordinated composition of reusable artifacts across the whole software development life cycle. A survey of publications on requirements reuse from the International Requirements Engineering (RE) Conference series determines the research landscape in this area over the last twenty years, assessing the hypothesis that there is no or little research reported at RE about generic reuse of requirements models that spans the software development life cycle. The paper then outlines, for the RE community, a research agenda associated with the presented vision for such an approach to requirements reuse that builds on concern-orientation, i.e., the ability to modularize and compose important requirements concerns throughout the software development life cycle, and modeldriven engineering principles. In addition, early research results are briefly presented that illustrate favorably the feasibility of such an approach.

show abstract

“…The analysis is made in light of the contribution that type classes can be expected to bring to software extension and software integration. To drive the analysis, Lämmel and Ostermann used formulations of a number of extension or integration problems, namely the expression problem [63,64], the framework integration problem [66], the tyranny of dominant decomposition [3], scattering and tangling [2] and the component integration problem [67]. By means of an analysis of the published state of the art, Lämmel and Ostermann concluded that type classes provide a principled mechanism for software extension and integration from which useful insights can be derived.…”

Section: Other Assessment Approachesmentioning

confidence: 99%

“…Aspect-oriented programming (AOP) is an emerging programming model primarily focused on the modularization of crosscutting concerns [1][2][3][4][5]. AOP is undergoing maturation, and many aspectoriented programming languages (AOPLs) have been proposed [6].…”

Section: Introductionmentioning

confidence: 99%

Implementing design patterns in Object Teams

Monteiro

Gomes

2012

Softw Pract Exp

View full text Add to dashboard Cite

SUMMARY This paper presents a study of the support for modularity of Object Teams, an aspect‐oriented language backwards compatible with Java. The study is based on implementations in Object Teams of two complete collections of the Gang‐of‐Four design patterns. An analysis of the implementations is provided, in terms of advantages of Object Teams over Java with respect to modularity, module composition and reuse. We present a systematic comparison with a functionally equivalent collection of implementations in AspectJ, regarding five modularity properties: locality, reusability, composition transparency, (un)pluggability and extensibility. Object Teams yields broadly comparable results in terms of the first four properties. Object Teams yields better results as regards flexible module extensibility, composition at the instance level and enclosing multiple pattern participants into a larger, cohesive module. AspectJ is more successful than Object Teams in the Singleton pattern because of its ability to intercept constructor events. Copyright © 2012 John Wiley & Sons, Ltd.

show abstract

N degrees of separation

Abstract: Done well, separation of concerns can provide many software engineering benefits, including reduced complexity, im-

Cited by 739 publications

References 19 publications

A core calculus for dynamic delta-oriented programming

A core calculus for dynamic delta-oriented programming

A vision for generic concern-oriented requirements reuse<sup>re@21</sup>

Implementing design patterns in Object Teams

Contact Info

Product

Resources

About

N degrees of separation

Abstract: Done well, separation of concerns can provide many software engineering benefits, including reduced complexity, im-

Cited by 739 publications

References 19 publications

A core calculus for dynamic delta-oriented programming

A core calculus for dynamic delta-oriented programming

A vision for generic concern-oriented requirements reuse<sup>re&#x0040;21</sup>

Implementing design patterns in Object Teams

Contact Info

Product

Resources

About

A vision for generic concern-oriented requirements reuse<sup>re@21</sup>