Editing Cross-cutting concern (section)

==Background==
Cross-cutting concerns are parts of a program that rely on or must affect many other parts of the system. They form the basis for the development of [[aspect (computer science)|aspects]].<ref name="Patent 4">{{harvnb|Kiczales et al.|2002|p=4}}</ref> Such cross-cutting concerns do not fit cleanly into [[object-oriented programming]] or [[procedural programming]].<ref name="Seminal 1">{{harvnb|Kiczales|Lamping|Mendhekar|Maeda|1997|p=1}}</ref>

Cross-cutting concerns can be directly responsible for ''tangling'', or system inter-dependencies, within a [[computer program|program]]. Because procedural and [[functional language]] constructs consist entirely of procedure calling, there is no semantic through which two goals (the capability to be implemented and the related cross-cutting concern) can be addressed simultaneously.<ref name="Seminal 6">{{harvnb|Kiczales|Lamping|Mendhekar|Maeda|1997|p=6}}</ref> As a result, the code addressing the cross-cutting concern must be ''scattered'', or duplicated, across the various related locations, resulting in a loss of [[modularity (programming)|modularity]].<ref name="Seminal 1" />

[[Aspect-oriented programming]] aims to [[encapsulation (computer science)|encapsulate]] cross-cutting concerns into [[aspect (computer science)|aspects]] to retain modularity. This allows for the clean isolation and reuse of code addressing the cross-cutting concern.<ref name="Seminal 2">{{harvnb|Kiczales|Lamping|Mendhekar|Maeda|1997|p=2}}</ref> By basing designs on cross-cutting concerns, [[software engineering]] benefits can include modularity and simplified maintenance.<ref name="Li 1">{{harvnb|Li|Krishnamurthi|Fisler|2002|p=1}}</ref>