Aspect-oriented
From FUKTwiki
Contents |
[edit] Aspect-Oriented Software Development
“Aspect-oriented software development (AOSD) methods propose new software modularization boundaries that provide additional opportunities for reuse and easier maintenance”.[1]
Modularization is the key aspect in any programming especially in the case of object oriented and aspect oriented. In aspect oriented the main emphasis is to improve modularization in the systems.
[edit] Crosscutting Concerns
“Crosscutting concerns are domain specific concepts that do not fit into an object abstraction.”[1] i am not satisfied with this definition
[edit] Aspect
- “It is an artifact to address a requirement”.
- “It is a crosscutting concern”.
- “Aspects are behaviors that are tangled and scattered across a system”.
- “An aspect is an element of functionality that is woven throughout other system behaviors.”[1]
[edit] Early Aspects
“Early aspects are crosscutting concerns that are identified in the early phases of the software development life cycle, including requirements analysis, domain analysis and architecture design. Secondly, early aspects also impact aspects in the subsequent phases.”[1]
[edit] References
- ↑ 1.0 1.1 1.2 1.3 Rashid A., Moreira A., Tekinerdogan B. (2004), “Editorial Early Aspects: Aspect-Oriented Requirements Engineering and Architecture Design”, IEEE Proc.-Softw., Vol. 151, No. 4.
[edit] Useful Links
-
There is an article about this subject on Wikipedia, the free online encyclopedia.
