Aspect Oriented Programing - Introduction
Download as PPTX, PDF2 likes1,132 views
Aspect-oriented programming (AOP) addresses the shortcomings of object-oriented programming (OOP) by separating cross-cutting concerns such as logging, validation, and security from business logic. This method improves modularity and reduces issues related to strong coupling and scattered code. AOP involves identifying concerns, writing plugin code (advices), and determining when to apply these plugins (pointcuts).
Aspect Oriented Programing - Introduction
- 2. What is the problem with OOP? Any custom software development necessarily needs to address cross-cutting concerns. Pooling Validation Caching Synchronisation Profiling Transaction Logging LoadBalancing Reomoting Persistance Security How to share these behaviors without "dirty" code?
- 3. What is the problem with OOP? Business Logic Code Logging Monitoring Validation Transaction
- 4. What is the problem with OOP? • The OOP provides a good level of abstraction and modularity • Complex problems often arrive at the following cases – Too many abstractions – Difficulty in breaking code – Strong Coupling between components – Scattered code • Principles of software development S.O.L.I.D – SRP
- 5. AOP • aspect-oriented programming (AOP) is a programming paradigm that aims to increase modularity by allowing the separation of cross-cutting concerns - wikipedia
- 6. A simplistic example Identification of cross-cutting Concerns
- 7. A simplistic example Writing the advice
- 8. A simplistic example Select the action points (pointcut) In our example: Pointcut = "At the beginning of each method"
- 9. In summary, AOP is • Identify needs transverse (cross cutting concerns) • Write one or more plugin code (advices) – Representation aspect – Encapsulation of behavior. • Choosing where to apply these plugin(pointcuts)
- 10. OOP + AOP
- 11. Who links the code ? Weaver
- 12. When to use AOP ?
- 13. Q & A ?
Editor's Notes
- #2: I would like to remind you that this task is not meant to conclude anything on AOP or OOP or any other programming paradigm ..
- #3: How to share these behaviors without "dirty" code by a ton of abstraction?
- #6: NearlyEvery programming language supports some level of grouping & encapsulating concerns into separate independent entities by providing abstractions …But some concerns defy these forms of abstractions and are called cross-cutting concerns because they “cut-across” multiple abstractions...
- #8: Whenever I heard a web-talk or read an article on AOP.. .. Every one just give some basic example of using AOP to logging if not to security.