Skip to content
Free planNo credit card requiredStart writing
AI for Research home
AI for Research home
Dashboard
Sign inGet started

Search 250 million research papers

Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.

About 1,272 papers for “aspect-oriented software development”

Software Security using Aspect-Oriented Software Development

بثینة فھران عبد عفاف بدیع قدو عامر عبدالمجید عبدالرحمن · SHILAP Revista de lepidopterología · 2019

Aspect-Oriented Software Development (AOSD) is a technology that helps achieving better Separation of Concern (SOC) by providing mechanisms to identify all relevant points in a program at which aspectual adaptations need to take place. This paper introduces a banking application using of AOSD with security concern in information hiding.

Cited by 0Open access

APPLYING ASPECT-ORIENTED SOFTWARE DEVELOPMENT TO MIDDLEWARE FRAMEWORKS TAL COHENAPPLYING ASPECT-ORIENTED SOFTWARE DEVELOPMENT TO

Middleware Frameworks · 2013

I would like to thank the many people who have directly or indirectly helped me during the long period of research. I thank my supervisor, Yossi Gil, who never ceased to amaze me; my friend and co-student Itay Maman, who greatly helped in large parts of this research; Prof. Shmuel Katz, who first introduced me to the world of aspect-oriented programming; Omer Barkol, who was a wonderful office-mate these last few years; Prof. Ron Pinter, who advised and encouraged; and lastly, Yardena Kolet, the final authority in the CS faculty. This work is dedicated to my family: to my parents, Rachel and Nahum; to my beloved wife Irit; and to my two wonderful children, Stav and Yuval: May you always have reasons for joy!

Cited by 0

Aspect-Oriented Software Development with Java Aspect Components

Renaud Pawlak, Lionel Seinturier, Laurence Duchien et al. · SPIRE - Sciences Po Institutional REpository · 2004

In the last four years, our research project dealt with separation of concerns for distributed programming environments and applications. This research effort led to the implementation of the Java Aspect Component (JAC) framework for aspect-oriented programming (AOP) in Java. Among the many requirements for distribution, flexibility and adaptability play a stringent role. The high variability of executing conditions (in terms of resources, servers availability, faults, ...) also brings the need for powerful programming paradigms. This led us to develop a dynamic model of AOP which, unlike statically compiled approaches, allows to on-the-fly deploy and undeploy aspects on top of running applications. This model comes with an UML notation and an implementation. An IDE is provided with JAC to support all the development steps of an aspect oriented application, from its design, to its implementation, to its deployment.

Cited by 20

Second Workshop on Aspect-Oriented Software Development

Pascal Costanza, Pascal Costanza, Günter Kniesel et al. · 2002

Syntax Trees 59 11 D. Vollmann Visibility of Join-Points in AOP and Implementation Languages 65 Part I Implementing and Reasoning about Aspects Reasoning About a Classification of Crosscutting Concerns in Object-Oriented Systems Constantinos A. Constantinides Department of Computer Science and Information Systems Birkbeck College, University of London cc@dcs.bbk.ac.uk Therapon Skotiniotis College of Computer Science Northeastern University skotthe@ccs.neu.edu and behavior of crosscutting concerns in OO systems. We further argue that aspects must be defined as first-class abstractions in order to be manipulated as such and thus to provide for reusability and dynamic adaptability as well as for the creation of dynamically loadable aspect repositories.

Cited by 0

UML Profile for Aspect-Oriented Software Development

Omar Aldawud, Tzilla Elrad, Atef Bader · 2003

This paper's position is that the time is ripe for initiating a proposal for an AOSD UML Profile. Some of the proposed Profile requirements are: (1) The Profile shall enable specifying, visualizing, and documenting the artifacts of software systems based on Aspect-Orientation. (2) The Profile shall be supported by UML (avoid "Heavy-weight" extension mechanisms), this allows a smooth integrating of existing CASE tools that support UML. (3) The Profile shall support the modular representation of crosscutting concern. And (4) the Profile shall not impose any behavioral implementation for AOSD, however it shall provide a complete set of model elements (or Stereotypes) that enable representing the semantics of the system based on Aspect-Orientation. AOSD Profile will set the stage for AOSD modeling, will enable capturing desired terminology of AOSD and will provide "native" support for AOSD in UML. Initial research publications and workshops on UML for AOSD have set the stage for our proposal.

Cited by 0