Abstract
Programming techniques have been passed through many development stages in their progressing path to cope with the increasing complexity of systems requirements. So, one of the main goals of the programming languages designers is how to develop programming language that can handle and manage the spread and overlapping of different functionality concerns. Because unmanageable and uncontrollable scattering of concerns inside the system may cause many problems during system running in present or/and during applying maintenance and developing the system in future. One of the most recent and powerful solutions to overcome these problems is via using Aspect-Oriented Programming (AOP) approach. This research is demonstrates the features and the problems with implying AOP techniques in the software development process.
Highlights
Any system developing process depends on its core module-level requirements and system-level requirements
Crosscutting concerns are comprised by a distinctive enterprise relevance like logging, authentication, pooling, resource, management, performance and storage management
An every stateful business object is affected by a storage-management concern [1]. Implementing these crosscutting concerns is considered to be a challenging issue that conventional programming approaches, such as Object-Oriented Programming (OOP) and Procedural-Oriented Programming (POP), cannot modularize very effectively
Summary
Any system developing process depends on its core module-level requirements and system-level requirements. There are three basic programming paradigms attempt to support programmers to apply the concerns' separation, especially cross-cutting concerns, to achieve better modularization. These paradigms are: Aspect-Oriented Programming (AOP), Aspect-Oriented Software Development (AOSD) and Post Object-Oriented Programming (POOP). The operation must be entered in the system log in a database transaction to prohibit incidental data loss Those new concerns will be in a comprehensible version like this: Transactions, security, and logging are various new concerns (cross-cutting concerns) which have begun to be tangled with the essential functionality (occasionally termed the business logic concern) of the code. Any modifications need to be done on any of these concerns would require huge work
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
