Abstract
In Aspect Oriented Software Development (AOSD) has been considered one of the most promising abstractions to make software structure more maintainable and configurable. It also helps to overcome two big issues of current object oriented programming principles, to reduce the problem of code tangling and code scattering. Aspect Oriented Programming (AOP) has been focused largely in the implementation/ specifications. This will allow software developers to identify, specify and realize aspects in the coding phase. But nowadays the AOP has been matured enough to turn into AOSD, as it the main objective of separation of concerns right through the process of software development. In this paper we deal with the impact of aspect in development of software especially in requirements engineering phase. We propose visual models to incorporate aspect as an extension to Unified Modeling Language (UML) without breaking current UML specifications. Proposal is made as new extensions for aspect modelling into existing UML design and implementation phase explicitly. The proposed visual models, supports Aspect and its related components to be incorporated into UML use case model at abstract level as well as at architectural level. Aspect Oriented Use case model is an approach which allows designers extends and compiles Aspects into design models.
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 callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
