• Documents
  • Authors
  • Tables
  • Log in
  • Sign up
  • MetaCart
  • Donate

CiteSeerX logo

Tools

Sorted by:
Try your query at:
Semantic Scholar Scholar Academic
Google Bing DBLP
Results 1 - 10 of 36
Next 10 →

Aspect Weaving as Component Knitting: Separating Concerns with Knit

by Eric Eide, Alastair Reid, Matthew Flatt, Jay Lepreau , 2001
"... Knit is a new component specification and linking language. It was initially designed for low-level systems software, which requires especially flexible components with especially well-defined interfaces. For example, threads and virtual memory are typically implemented by components within the syst ..."
Abstract - Add to MetaCart
reasonable performance. Component composition with Knit thus acts like aspect weaving: component interfaces determine the "join points" for weaving, while components (some of which may be automatically generated) implement aspects. Knit is not limited to the construction of low-level software

Appeared in the Workshop on Advanced Separation of Concerns in Software Engineering at ICSE 2001,

by Toronto Ontario May, Eric Eide, Alastair Reid, Matthew Flatt, Jay Lepreau
"... Knit is a new component specification and linking language. It was initially designed for low-level systems software, which requires especially flexible components with especially well-defined interfaces. For example, threads and virtual memory are typically implemented by components within the syst ..."
Abstract - Add to MetaCart
Knit is a new component specification and linking language. It was initially designed for low-level systems software, which requires especially flexible components with especially well-defined interfaces. For example, threads and virtual memory are typically implemented by components within

Formal Models for Architecture Aspects and Their Weaving

by Chunhua Yang, Haiyang Wang
"... Abstract—Aspect-oriented concepts are currently introduced in early stages of software development to achieve better separation of concerns. However, at the architecture level, there exists no strict model for aspects and their weaving, which makes it difficult for analyzing and reasoning about the ..."
Abstract - Add to MetaCart
Abstract—Aspect-oriented concepts are currently introduced in early stages of software development to achieve better separation of concerns. However, at the architecture level, there exists no strict model for aspects and their weaving, which makes it difficult for analyzing and reasoning about

Weaving Deployment Aspects into Domain-Specific Models

by Krishnakumar Balasubramanian, Aniruddha Gokhale, Yuehua Lin, Jing Zhang, Jeff Gray - International Journal on Software Engineering and Knowledge Engineering (IJSEKE , 2006
"... Domain-specific models increase the level of abstraction used to develop large-scale component-based systems. Model-driven development (MDD) approaches (e.g., Model-Integrated Computing and Model-Driven Architecture) emphasize the use of models at all stages of system development. Decomposing proble ..."
Abstract - Cited by 12 (9 self) - Add to MetaCart
problems using MDD approaches may result in a separation of the artifacts in a way that impedes comprehension. For example, a single concern (such as deployment of a distributed system) may crosscut different orthogonal activities (such as component specification, interaction, packaging and planning

AOCI: Weaving Components in a Distributed Environment

by Guido Söldner, Sven Schober, Wolfgang Schröder-preikschat, Rüdiger Kapitza
"... Abstract. Mobile and embedded devices like PDAs, mobile phones, and all kinds of consumer hardware populate the world we live in. Despite the vision of ubiquitous computing and its idea of spontaneous interaction among these devices more than fifteen years ago, most of them are still isolated and re ..."
Abstract - Cited by 4 (2 self) - Add to MetaCart
and restricted in their interaction capabilities. One reason for this limitation is the poor support for dynamic adaptation and evolution of software in distributed environments. This paper proposes AOCI, an Aspect-Oriented Component Infrastructure that takes the core ideas of AOP, the separation of concerns

CQML: Aspect-oriented Modeling for Modularization and Weaving QoS Concerns in Componentbased Systems

by Sumant Tambe, Akshay Dabholkar, Aniruddha Gokhale - In Proceedings of the 16th IEEE International Conference and Workshop on the Engineering of Computer Based Systems (ECBS 09 , 2009
"... Current domain-specific modeling (DSM) frameworks for designing component-based systems often consider the system’s structural and behavioral concerns as the two dominant concerns of decomposition while treating non-functional or quality of service (QoS) concerns as an af-ter thought. Such framework ..."
Abstract - Cited by 2 (1 self) - Add to MetaCart
of the modeling frameworks along both the structural and non-functional dimensions. This paper describes Component QoS Modeling Lan-guage (CQML), which is a reusable, extensible, and aspect-oriented modeling approach that provides strong separa-tion between the structural and non-functional dimensions. CQML

An Aspect-Oriented Framework for Weaving Domain-Specific Concerns into Component-Based Systems FrédéricLoiret,RomainRouvoy,LionelSeinturier,DanielRomero

by Kévin Sénéchal , 2011
"... Abstract: Software components are used in various application domains, and many component models and frameworks have been proposed to fulfill domain-specific requirements. The general trend followed by these approaches is to provide ad-hoc models and tools for capturing these requirements and for im ..."
Abstract - Add to MetaCart
) These annotations are implemented as open and extensible component-based containers, achieving full separation of functional and extra-functional concerns. iii) Finally, the full machinery is implemented using the Aspect-Oriented Programming paradigm. We validate our approach with two case studies: the first

Dynamic Aspect Weaving using a Planning-based Adaptation Middleware

by Romain Rouvoy, Mikaël Beauvois, Frank Eliassen
"... The growing complexity of applications has enforced the need for separation concern and modularity. These requirements become critical when considering self-adaptive mobile applications, which are capable of optimizing their behavior depending on their context of execution. In our context, the cross ..."
Abstract - Cited by 1 (0 self) - Add to MetaCart
modeling approach, our adaptation middleware is able to automatically select and configure the aspect(s) to weave into a base component for improving its quality of service.

Separating Concerns in a High-Level Component-Based Context

by Wim Vanderperren Bart, Bart Wydaeghe - Electronic Notes in Theoretical Computer Science, Vol , 2002
"... Building on the work of architectural description languages and aspect-oriented programming, we try to improve current visual component composition environments. In our research, we introduced the concept of a composition pattern to lift the abstraction level of current visual wiring to a protocol r ..."
Abstract - Add to MetaCart
component. We introduce composition adapters as a means to localize crosscutting concerns in a separate entity. We use state information deduced from the composition pattern to weave composition adapters into the component-based application. In this paper, we explain how composition adapters are checked

Localizing crosscutting concerns in visual component based development

by Wim Vanderperren - In Proceedings of Software Engineering Research and Practice (SERP) International Conference. Las Vegas , 2002
"... This work builds on aspect-oriented development ideas and our previous research where we lift the abstraction level of visual component based development. In component based development, the components are the natural unit of modularization. However, there will always be concerns that cannot be conf ..."
Abstract - Cited by 6 (3 self) - Add to MetaCart
This work builds on aspect-oriented development ideas and our previous research where we lift the abstraction level of visual component based development. In component based development, the components are the natural unit of modularization. However, there will always be concerns that cannot
Next 10 →
Results 1 - 10 of 36
Powered by: Apache Solr
  • About CiteSeerX
  • Submit and Index Documents
  • Privacy Policy
  • Help
  • Data
  • Source
  • Contact Us

Developed at and hosted by The College of Information Sciences and Technology

© 2007-2016 The Pennsylvania State University