{"title":"Heterogeneous pointcut expressions","authors":"G. Mussbacher, Daniel Amyot","doi":"10.1109/EA.2009.5071577","DOIUrl":"https://doi.org/10.1109/EA.2009.5071577","url":null,"abstract":"Over the last decade, many aspect-oriented (AO) programming and modeling languages have been developed. Pointcut expressions are a key concept of each of these languages as they define the patterns that must be matched for aspects to be applied to the base. To date, most pointcut expressions are constrained to one particular notation - the one for which they were designed - even though a goal of aspect-oriented software development should be to encapsulate a concern through all phases of software development. Motivated by examples of aspects that require characteristics expressed in different notations to be matched by their pointcut expressions, we argue that there should be more focus on heterogeneous pointcut expressions that can span several notations from potentially different development phases. We demonstrate such pointcuts in an example modeled with the Aspect-oriented User Requirements Notation (AoURN) which combines notations for goal-oriented, scenario-based, and aspectoriented modeling in one framework for requirements engineering.","PeriodicalId":118313,"journal":{"name":"2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116950342","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
H. Ossher, David Amid, Ateret Anaby-Tavor, R. Bellamy, M. Callery, Michael Desmond, Jackie De Vries, A. Fisher, Sophia Krasikov, I. Simmonds, Calvin Swart
{"title":"Using tagging to identify and organize concerns during pre-requirements analysis","authors":"H. Ossher, David Amid, Ateret Anaby-Tavor, R. Bellamy, M. Callery, Michael Desmond, Jackie De Vries, A. Fisher, Sophia Krasikov, I. Simmonds, Calvin Swart","doi":"10.1109/EA.2009.5071580","DOIUrl":"https://doi.org/10.1109/EA.2009.5071580","url":null,"abstract":"Before requirements analysis takes place in a business context, business analysis is usually performed. Important concerns emerge during this analysis that need to be captured and communicated to requirements engineers. In this paper, we take the position that tagging is a promising approach for identifying and organizing these concerns. The fact that tags can be attached freely to entities, often with multiple tags attached to the same entity and the same tag attached to multiple entities, leads to multi-dimensional structures that are suitable for representing crosscutting concerns and exploring their relationships. The resulting tag structures can be hardened into classifications that capture and communicate important concerns.","PeriodicalId":118313,"journal":{"name":"2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design","volume":"50 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115039660","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Runtime monitoring of cross-cutting policy","authors":"S. Nakajima, Naoyasu Ubayashi, Keiji Hokamura","doi":"10.1109/EA.2009.5071579","DOIUrl":"https://doi.org/10.1109/EA.2009.5071579","url":null,"abstract":"In open systems, certain unfavorable situations due to unanticipated user behavior may be seen, which results in a violation of cross-cutting policy. This paper proposes a runtime monitoring method to check such problems. Since there is a large gap, a certain link is needed between the policy and runtime execution method. We employ a two-step checking approach; an offline symptom checking and a runtime monitoring. The ingredient to tie the two steps is a Linear-time Temporal Logic formula for the cross-cutting policy to look at.","PeriodicalId":118313,"journal":{"name":"2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design","volume":"30 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"123945232","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"On modeling interactions of early aspects with goals","authors":"G. Mussbacher, Daniel Amyot","doi":"10.1109/EA.2009.5071578","DOIUrl":"https://doi.org/10.1109/EA.2009.5071578","url":null,"abstract":"Interactions in aspect-oriented models must be detected, documented, and resolved for aspects to be composed as desired. Generally, aspect interactions can be categorized as intrinsic (those that inherently exist among concerns) or technical (those that are dependent on technology and may change over time). Consequently, these types of interactions should be encapsulated properly. Goal models support reasoning about qualitative and quantitative relationships and are therefore ideally positioned to describe and reason about intrinsic interactions, because they are often of a qualitative nature. On the other hand, technical interactions are typically syntactic conflicts and dependencies which are modeled with different techniques. We present the Concern Interaction Graph (CIG), a goal model specialized for technical interactions in aspect-oriented models, which is integrated with other goal models for intrinsic concern interactions and stakeholder intentions. The CIG therefore allows global trade-offs among concerns that take intrinsic and technical interactions into account as well as the needs of stakeholders, while maintaining proper separation of concerns between intrinsic and technical interactions.","PeriodicalId":118313,"journal":{"name":"2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design","volume":"16 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"134356360","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
M. Pinto, L. Fuentes, Juan A. Valenzuela, Paulo F. Pires, Flávia Coimbra Delicato
{"title":"Promoting the software evolution in AOSD with early aspects: Architecture-oriented model-based pointcuts","authors":"M. Pinto, L. Fuentes, Juan A. Valenzuela, Paulo F. Pires, Flávia Coimbra Delicato","doi":"10.1109/EA.2009.5071581","DOIUrl":"https://doi.org/10.1109/EA.2009.5071581","url":null,"abstract":"Aspect oriented systems suffer from an issue named pointcut fragility problem, which occurs when a poincut unintentionally captures or misses a given join point as a consequence of apparently harmless modifications of the base elements or system structure. One promising approach to cope with this problem is the definition of pointcuts in terms of elements of an intermediary conceptual model. In this paper we investigate the benefits of defining these conceptual models at early stages of the development. Concretely, we use the AO-ADL architectural language and, in particular, its support to define: (1) semantics-based compositions, and (2) parameterized architectural templates. We also demonstrate the feasibility of our approach through a case study.","PeriodicalId":118313,"journal":{"name":"2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design","volume":"4 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"127240767","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
Carla Silva, Márcia Lucena, J. Castro, J. Araújo, A. Moreira, F. Alencar
{"title":"Support for aspectual modeling to Multiagent system architecture","authors":"Carla Silva, Márcia Lucena, J. Castro, J. Araújo, A. Moreira, F. Alencar","doi":"10.1109/EA.2009.5071582","DOIUrl":"https://doi.org/10.1109/EA.2009.5071582","url":null,"abstract":"A Multiagent system (MAS) architecture is structured in terms of autonomous and communicating components. Agent orientation does not support the modularization of some system properties that affect several system components. These properties are called “crosscutting concerns” and need to be explicitly captured in the architectural design of MAS. Aspect-orientation provides abstractions to identity and modularize crosscutting concerns throughout the software lifecycle. This work uses aspect-oriented abstractions to define a modeling language to describe and modularize crosscutting concerns in MAS architecture. An e-commerce example is used to illustrate the application of the proposed modeling language.","PeriodicalId":118313,"journal":{"name":"2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design","volume":"86 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"116220158","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Automating the discovery of stable domain abstractions for reusable aspects","authors":"D. Landuyt, E. Truyen, W. Joosen","doi":"10.1109/EA.2009.5071576","DOIUrl":"https://doi.org/10.1109/EA.2009.5071576","url":null,"abstract":"Domain-driven aspect design aims to support effective reuse of aspects within a product-line or family of software systems. In this paper, we explore the feasibility of automating our approach to discover stable domain abstractions in requirements for the purpose of defining reusable pointcuts. This approach was introduced in earlier work mainly as a manual method. This paper defines an algorithmic procedure for each activity, and discusses to which degree each activity can be automated. The generalization activity (activity 3) is given specific attention, as it is the most complex activity at the heart of the approach. The end result is an algorithmic procedure for (semi-)automatically discovering stable domain abstractions to design effectively reusable pointcuts.","PeriodicalId":118313,"journal":{"name":"2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design","volume":"47 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"115222767","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Model Driven Development with non-functional aspects","authors":"Liming Zhu, Y. Liu","doi":"10.1109/EA.2009.5071584","DOIUrl":"https://doi.org/10.1109/EA.2009.5071584","url":null,"abstract":"Model Driven Development (MDD) refers to the systematic use of models as primary engineering artifacts throughout a software development life cycle. In recently years, MDD has been increasingly employed to guide development with a focus on system modeling, code generation from models and white-box analysis of models. However, compositional system analysis regarding early Non-Functional Aspects/Properties (NFP) remains difficult. In this paper, we critically review the state-of-the-art of MDD in the context of non-functional aspects and shed some lights on the following two questions: 1) How to model Non-Functional Aspect/Property (NFP). The focus is to understand the different subtypes of a non-functional aspects and its compositional and emergent nature. 2) How models can be used for analyzing Non-functional Aspect/Property (NFP). This focuses on the analysis models in the form of reasoning frameworks (both qualitative and quantitative) behind each non-functional aspect.","PeriodicalId":118313,"journal":{"name":"2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design","volume":"29 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"117172039","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Concern tracing and change impact analysis: An exploratory study","authors":"Safoora Shakil Khan, S. Lock","doi":"10.1109/EA.2009.5071583","DOIUrl":"https://doi.org/10.1109/EA.2009.5071583","url":null,"abstract":"A few AO Requirement Engineering approaches support traceability by providing mapping and influence of requirements-level concerns on subsequent phase artefacts. This is not sufficient to ensure that the architecture actually meets the specified requirements (as some requirements lead to architectural decisions, establish trade-offs, etc). Equally, without knowledge of such traceability relationships it becomes very difficult to predict change impact and thus understand the causes of system instability. In order to improve this situation, we have developed a concern-oriented dependency taxonomy that enables us to capture the dependency relationships between requirements-level concerns and their manifestation at the architectural level. We have applied the dependency taxonomy on a real-world case study to explore and identify unstable architectural components, which are most likely to be impacted by change.","PeriodicalId":118313,"journal":{"name":"2009 ICSE Workshop on Aspect-Oriented Requirements Engineering and Architecture Design","volume":"9 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2009-05-18","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"133523292","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}