GEA: A Goal-Driven Approach toDiscovering Early Aspects

Hsu, Kuo-Hsun

doi:10.1109/tse.2014.2322368

Cited by 6 publications

(5 citation statements)

References 46 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In [29], an extensive comparative analysis on the Theme/Doc approach and Multidimensional Separation of Concerns for Requirements Engineering (MDSOCRE) was performed, concluding that MDSOCRE focuses on the analyst's domain knowledge, and Theme/Doc analyses the requirements language while looking for the concern name [29]. The performance of the proposed method was verified by comparing it with goal-based AORE [16], viewpoint-based AORE [1], and multidimensional separation of concerns in requirements engineering [15] methods. Table V shows a brief comparison.…”

Section: Comparative Analysis Of Cb-aore With Other Aore Modelsmentioning

confidence: 99%

“…Context is any information that can be used to characterize the situation of an entity, such as a person, place, or object, necessary for the interaction between the user and the application [14]. This model was inspired by the multidimensional approach for separating concerns and identifying homogeneous crosscutting concerns [15][16]. Homogeneous cross-cutting concerns are concerns that add the same behavioral variation at multiple points in the program [11].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Context-Based Aspect-Oriented Requirement Engineering Model

Idate

Rao

Mali³

2023

Eng. Technol. Appl. Sci. Res.

View full text Add to dashboard Cite

Mobile applications are context-oriented systems that involve the use of context information while operating. Mobile applications demand tackling context information in the early phase of software engineering. A context-aware system demands a different approach to handling the influence of the context on a system's requirements. Aspect-oriented Requirement Engineering separates concerns throughout requirements, called crosscutting concerns, in the early phase of software development to improve the modularity of complex applications. Capturing requirements embedded within context is a challenging procedure. This study aimed to identify such contextual characteristics of requirements in the early phase of software engineering, using natural language processing techniques, by proposing Context-Based Aspect-Oriented Requirement Engineering (CB-AORE) to visualize the existence of crosscutting concerns. CB-AORE performs context modeling to analyze the context dependency with base requirements and helps the analyst to visualize the correlation of functional and non-functional requirements with context. A case study analyzed the identification of context and its use to identify crosscutting concerns.

show abstract

Section: Comparative Analysis Of Cb-aore With Other Aore Modelsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Context-Based Aspect-Oriented Requirement Engineering Model

Idate

Rao

Mali³

2023

Eng. Technol. Appl. Sci. Res.

View full text Add to dashboard Cite

show abstract

“…Goal-Driven Approach to Discovering Early Aspects [7] is an extended approach to aspect discovery proposed by Jonathan Lee. Formulation, construction, classification, and identification are four important phases in GEA process.…”

Section: Geamentioning

confidence: 99%

Untitled

2018

IJET

View full text Add to dashboard Cite

Large-scale software applications are complex systems that involve myriad of different concerns .Ideally these concerns should be organized into different modules , but often some of these concerns crosscut each other .Identification of cross cutting concern in the beginning of each phase in software development lifecycle is very important. Crosscutting concerns identification has been neglected in software projects. This paper compares approaches such as Grounded Theory for Crosscutting Concerns Identification (GT4CCI), Discovering Early Aspects through Goals Interactions and Language Extended Lexicon (LEL) which can be a building block to identification of Crosscutting Concerns. Comparison is made on the basis of their type of requirement document which they accept and the end results .

show abstract

“…Although aspect-orientation is flexible and has received some attention by researchers [6,57,61], there are important methodological and technical differences between traits and aspects. Aspects were introduced to deal with crosscutting concerns and provide a mechanism to modulate and reuse them.…”

Section: Aspect-orientationmentioning

confidence: 99%

Promoting traits into model-driven development

Abdelzad

Lethbridge

2015

Softw Syst Model

View full text Add to dashboard Cite

Traits are primitive units of code reuse that serve as building blocks of classes. In this research, we enhance reuse by extending the capabilities of traits; in particular, we add modeling abstractions to them.Traits have a variety of benefits, including facilitating reuse and separation of concerns. They have appeared in several programming languages, particularly derivatives of Smalltalk. However, there is still no support for traits that contain modeling abstractions, and no straightforward support for them in general-purpose programming languages. The latter is due to structural concerns that exist for them at runtime, especially traits that contain modeling abstractions.Model-driven technologies are making inroads into the development community, albeit slowly. Modeling abstractions such as state machines and associations provide new opportunities for reuse, and can be combined with inheritance for even greater reusability.However, issues with inheritance apply also when these new abstractions are inheritable units. This suggests that traits and models ought to be able to be synergistically combined.We perform a comprehensive analysis of using modeling elements in traits. We implement such traits in Umple, which is a model-oriented programming language that permits embedding of programming concepts into models.The contributions of the thesis are: a) Adding new elements including state machines and associations into traits, hence bringing more reusability, modularity, and applications to traits; b) Developing an algorithm that allows reusing, extending, and composing state machines through traits; c) Extending traits with required interfaces so dependencies at the semantic level become part of their usage, rather than simple syntactic capture; d) Adding template parameters with associations in traits, offering new applications for traits in which it is possible to define design patterns and to have a library of most-used functionality; e) The implementation of all the above concepts, including generating code in multiple generalpurpose programming languages through automatic model transformation.iii

show abstract

GEA: A Goal-Driven Approach toDiscovering Early Aspects

Cited by 6 publications

References 46 publications

Context-Based Aspect-Oriented Requirement Engineering Model

Context-Based Aspect-Oriented Requirement Engineering Model

Untitled

Promoting traits into model-driven development

Contact Info

Product

Resources

About