A concern architecture view for aspect-oriented software design

Katara, Mika; Katz, Shmuel

doi:10.1007/s10270-006-0032-x

Cited by 14 publications

(4 citation statements)

References 21 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Katara and Katz [28] view aspects as augmentations that map an existing design artifact into a new one with changes or additions. Their framework, which is applied to UML, has some similarities to our approach, but since they use UML, they must treat each diagram type separately, requiring special consistency treatment.…”

Section: Reuse Of Design Modules In Modeling Techniquesmentioning

confidence: 99%

Reusing semi-specified behavior models in systems analysis and design

2008

Self Cite

View full text Add to dashboard Cite

As the structural and behavioral complexity of systems has increased, so has interest in reusing modules in early development phases. Developing reusable modules and then weaving them into specific systems has been addressed by many approaches, including plug-and-play software component technologies, aspect-oriented techniques, design patterns, superimposition, and product line techniques. Most of these ideas are expressed in an object-oriented framework, so they reuse behaviors after dividing them into methods that are owned by classes. In this paper, we present a crosscutting reuse approach that applies object-process methodology (OPM). OPM, which unifies system structure and behavior in a single view, supports the notion of a process class that does not belong to and is not encapsulated in an object class, but rather stands alone, capable of getting input objects and producing output objects. The approach features the ability to specify modules generically and concretize them in the target application. This is done in a three-step process: designing generic and target modules, weaving them into the system under development, and refining the combined specification in a way that enables the individual modules to be modified after their reuse. Rules for specifying and combining modules are defined and exemplified, showing the flexibility and benefits of this approach.

show abstract

Section: Reuse Of Design Modules In Modeling Techniquesmentioning

confidence: 99%

Reusing semi-specified behavior models in systems analysis and design

2008

Self Cite

View full text Add to dashboard Cite

show abstract

“…Numerous applications of the aspect-oriented approach exist, including the design of aspectoriented learning management systems (Al-Hudhud, 2015). Katara and Katz (2007) defined an architecture model for AOSD concerns. Any aspect changes can be analyzed using the aspect views, as tracking changes across multiple aspects is challenging.…”

Section: Aspect-oriented Approachmentioning

confidence: 99%

Software Development for Educational Information Services Using Multilayering Semantics Adaptation

Rukhiran

Buaroong

Netinant

2022

International Journal of Service Science, Management, Engineering, and Technology

View full text Add to dashboard Cite

Electronic information services are robust platforms that impact daily life and facilitate new research. Increasing software modularity and reusability saves time and money. Numerous designs and programming are challenging when developing a complex educational information system. This article proposes a new paradigm of multi-dimensional information layers, aspects, functional data, and composition rules in software development to create practical educational information platforms. The proposed approach uses aspect orientation throughout educational information's software development life cycle, from planning to implementation and evaluation. Finally, the authors demonstrate and evaluate the design model's modularity and adaptation through fine-granularity design and class reuse. The result reduces invasive changes, promotes modularity and reuse, and eliminates duplication in component-based software design.

show abstract

“…Moreover, visibility declarations and interfaces can be used to establish which parts of an aspect are visibile to or hidden from other aspects. This enables modellers to use aspect-composition frameworks, such as the one proposed in [19].…”

Section: Aspect Uml Extensionmentioning

confidence: 99%

A Meta-Level Specification and Profile for AspectJ in UML.

Evermann¹

2007

JOT

View full text Add to dashboard Cite

Aspect-oriented programming (AOP) has become a mature technology. Increasingly, calls for support of AOP on the software model level are being voiced. This paper addresses these calls by offering a meta-model of AspectJ in UML. Using the UML extension mechanisms, the resulting meta-model is also a UML profile for supporting AspectJ modelling in UML. In contrast to previous work, this profile offers complete meta-level integration of all AspectJ concepts. Moreover, the use of standard XMI based modelling allows the use of the profile in commercially available CASE tools and supports easy code generation.

show abstract

A concern architecture view for aspect-oriented software design

Cited by 14 publications

References 21 publications

Reusing semi-specified behavior models in systems analysis and design

Reusing semi-specified behavior models in systems analysis and design

Software Development for Educational Information Services Using Multilayering Semantics Adaptation

A Meta-Level Specification and Profile for AspectJ in UML.

Contact Info

Product

Resources

About