Handling crosscutting constraints in domain-specific modeling

Gray, Jeff; Bapty, Ted; Neema, Sandeep; Tuck, James

doi:10.1145/383845.383864

Cited by 106 publications

(65 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the same manner that crosscutting code detracts from the cohesiveness of an implementation, the utility of specifying constraints within a model is often diminished due to their scattering throughout the model hierarchy [14]. It is often the case that the meta-model forces the emergence of a "dominant decomposition" (i.e., the primordial criteria for modular decomposition) [8,36] that imposes the subjugation of other concerns, such as those captured by constraints.…”

Section: Model Weavers For Separating Crosscutting Constraintsmentioning

confidence: 99%

“…An AOSD approach can be beneficial at different stages of the software lifecycle and at various levels of abstraction. In particular, it can be advantageous to apply AOSD principles at levels closer to the problem space, e.g., architectural analysis [18], requirements engineering [30], and modeling [14], as well as the solution space, e.g, design [5,10,33], and implementation/coding [4,19,21,36].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

An Approach for Supporting Aspect-Oriented Domain Modeling

Gray¹,

Bapty²,

Neema³

et al. 2003

Generative Programming and Component Engineering

Self Cite

View full text Add to dashboard Cite

Abstract. This paper describes a technique for improving separation of concerns at the level of domain modeling. A contribution of this new approach is the construction of support tools that facilitate the elevation of crosscutting modeling concerns to first-class constructs in a type-system. The key idea is the application of a variant of the OMG Object Constraint Language to models that are stored persistently in XML. With this approach, weavers are generated from domain-specific descriptions to assist a modeler in exploring various alternative modeling scenarios. The paper examines several facets of Aspect-Oriented Domain Modeling (AODM), including: domain-specific model weavers, a language to support the concern separation, an overview of code generation issues within a meta-weaver framework, and a comparison between AODM and AOP. An example of the approach is provided, as well as a description of several future concepts for extending the flexibility within AODM.

show abstract

Section: Model Weavers For Separating Crosscutting Constraintsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

An Approach for Supporting Aspect-Oriented Domain Modeling

Gray¹,

Bapty²,

Neema³

et al. 2003

Generative Programming and Component Engineering

Self Cite

View full text Add to dashboard Cite

show abstract

“…Aspect-Oriented Modeling (AOM) [7,17,38] has emerged as a powerful method of untangling and managing scattered concerns in large enterprise application models [19,21]. With AOM, any scattered concern can be extracted into its own view.…”

Section: Introductionmentioning

confidence: 99%

“…Most current model weavers [9,16,21,38,45] rely on techniques, such as specifying queries or patterns to match against model elements, that are ideal for matching advice against methods and constructors in application code, but are not necessarily ideal for static weaving problems. Many enterprise applications require developers to incorporate global constraints into the weaving process that can only be solved in a static weaving problem.…”

Section: Introductionmentioning

confidence: 99%

Constraint-Based Model Weaving

White

Gray

Schmidt

2009

Lecture Notes in Computer Science

Self Cite

View full text Add to dashboard Cite

Abstract. Aspect-Oriented Modeling (AOM) is a promising technique for untangling the concerns of complex enterprise software systems. AOM decomposes the cross-cutting concerns of a model into separate models that can be woven together to form a composite solution model. In many domains, such as multi-tiered e-commerce web applications, separating concerns is much easier than deducing the proper way to weave the concerns back together into a solution model. For example, modeling the types and sizes of caches that can be leveraged by a web application is much easier than deducing the optimal way to weave the caches back into the solution architecture to achieve high system throughput.This paper presents a technique called constraint-based weaving that maps model weaving to a constraint satisfaction problem (CSP) and uses a constraintsolver to deduce the appropriate weaving strategy. By mapping model weaving to a CSP and leveraging a constraint solver, our technique (1) generates solutions that are correct with respect to the weaving constraints, (2) can incorporate complex global weaving constraints, (3) can provide weaving solutions that are optimal with respect to a weaving cost function, and (4) can eliminate manual effort that would normally be required to specify pointcuts and maintain them as target models change. The paper also presents the results of a case study that applies our CSP weaving technique to a representative enterprise Java application. Our evaluation of this case study showed a reduction in manual effort that our technique provides.

show abstract

“…In this second approach, after the unified metamodel is formulated, we use an "SQL-like" declarative language that allows one to query and change the model to define model transformation rules. The Embedded Constraint Language (ECL), used by the C-SAW GME plug-in (Gray, 2001), is such a language. ECL is a textual language for describing transformations on visual models.…”

Section: Integration Of Syntactic-based and Semantic-based Domain Modmentioning

confidence: 99%