Aspect assumptions

Zschaler, Steffen; Rashid, Awais

doi:10.1145/1960275.1960288

Cited by 6 publications

References 22 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

Modularizing Early Architectural Assumptions in Scenario-Based Requirements

Landuyt

Joosen

2014

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

Abstract. Early architectural assumptions (EAAs) are initial assumptions about the architectural solution that are made already during requirements elicitation. Such EAAs are inherently present when applying requirements engineering methods and techniques situated at the transition to architecture, for example those adhering to the Twin Peaks model to software engineering.In the current state-of-the-art, early architectural assumptions (EAAs) are documented implicitly, and they are tangled within and scattered across heterogeneous requirement artifacts. This makes it hard to distinguish EAAs from actual requirements, analyze their relevance, and bring them in relation to architectural decisions taken in later development stages. As a consequence, early development activities in the transition to architecture are hindered by the lack of explicit support for EAAs.In this paper, we address this problem in the context of scenario-based requirements (use cases and quality attribute scenarios). We present a system meta-model for EAAs, and provide an aspect-oriented requirements language that allows the instantiation of EAAs in terms of use case-level pointcuts. We employ our prototype implementation of abovementioned techniques to evaluate and illustrate the benefits of making EAAs explicit in the early stages of development, specifically in terms of modularity and requirements navigability.

show abstract

Modularizing Early Architectural Assumptions in Scenario-Based Requirements

Landuyt

Joosen

2014

Fundamental Approaches to Software Engineering

View full text Add to dashboard Cite

show abstract

AspectJ code analysis and verification with GASR

Fabry

Roover

Noguera

et al. 2016

Journal of Systems and Software

Self Cite

View full text Add to dashboard Cite

• We argue for a general-purpose source code analysis tool that is aware of aspects.• We present the logic program querying tool GASR, the first such tool..• We discuss its implementation along with its library of logical predicates.• We show how it can automatically verify previously published aspectual assumptions. AbstractAspect-oriented programming languages extend existing languages with new features for supporting modularization of crosscutting concerns. These features however make existing source code analysis tools unable to reason over this code. Consequently, all code analysis efforts of aspect-oriented code that we are aware of have either built limited analysis tools or were performed manually. Given the significant complexity of building them or manual analysis, a lot of duplication of effort could have been avoided by using a general-purpose tool.To address this, in this paper we present Gasr: a source code analysis tool that reasons over AspectJ source code, which may contain metadata in the form of annotations. Gasr provides multiple kinds of analyses that are general enough such that they are reusable, tailorable and can reason over annotations. We demonstrate the use of Gasr in two ways: we first automate the recognition of previously identified aspectual source code assumptions. Second, we turn implicit assumptions into explicit assumptions through annotations and automate their verification. In both uses Gasr performs detection and verification of aspect assumptions on two well-known case studies that were manually investigated in earlier work. Gasr finds already known aspect assumptions and adds instances that had been previously overlooked.

show abstract

Aspectual source code analysis with GASR

Fabry

Roover

Jonckers

2013

2013 IEEE 13th International Working Conference on Source Code Analysis and Manipulation (SCAM)

View full text Add to dashboard Cite

Abstract-To be able to modularize crosscutting concerns, aspects introduce new programming language features, often in a new language, with a specific syntax. These new features lead to new needs for source code analysis tools, resulting in the requirement for a general-purpose aspectual source code analysis tool. Ignoring this requirement has led to a nontrivial duplication of effort in the aspect-oriented software development community. This is because all code analysis efforts that we are aware of have either built ad-hoc analysis tools or were performed manually. In this paper we present GASR: a source code analysis tool in the tradition of logic program querying that reasons over ASPECTJ source code. By hooking into the IDE plugins for ASPECTJ, GASR provides a library of predicates that can be used to query aspectual source code. We demonstrate the use of GASR by automating the recognition of a number of previously identified aspectual source code assumptions. We then detect assumption instances on two well-known case studies that were manually investigated in the earlier work. In addition to finding the already known aspect assumptions, GASR encounters assumption instances that were overlooked before.

show abstract

Aspect assumptions

Cited by 6 publications

References 22 publications

Modularizing Early Architectural Assumptions in Scenario-Based Requirements

Modularizing Early Architectural Assumptions in Scenario-Based Requirements

AspectJ code analysis and verification with GASR

Aspectual source code analysis with GASR

Contact Info

Product

Resources

About