http://debianws.lexgopc.com/wiki143/index.php?action=history&feed=atom&title=Aspect_%28computer_programming%29 2026-10-26T17:23:28Z Revision history for this page on the wiki MediaWiki 1.43.1 http://debianws.lexgopc.com/wiki143/index.php?title=Aspect_(computer_programming)&diff=450003&oldid=prev 2024-06-30T14:03:11Z

<p><span class="autocomment">top: </span> Clean up/copyedit</p> <p><b>New page</b></p><div>{{Short description|Feature linked to many parts of a program, unrelated to program&#039;s primary function}}<br /> {{Refimprove|date=June 2008}}<br /> {{single source|date=June 2008}}<br /> In [[computer programming]], an &#039;&#039;&#039;aspect&#039;&#039;&#039; of a program is a [[Software feature|feature]] linked to many other parts of the program, but is not related to the program&#039;s primary function. An aspect [[Cross-cutting concern|crosscuts]] the program&#039;s core concerns, therefore violating its [[separation of concerns]] that tries to encapsulate unrelated functions. For example, [[Data logging|logging]] code can crosscut many modules, yet the aspect of logging should be separate from the functional concerns of the module it cross-cuts. Isolating such aspects as logging and [[persistence (computer science)|persistence]] from [[business logic]] is at the core of the [[aspect-oriented programming]] (AOP) [[programming paradigm|paradigm]].&lt;ref&gt;{{cite book|title=Aspect-Oriented Database Systems|url=https://archive.org/details/springer_10.1007-978-3-662-05851-0|author=Awais Rashid|year= 2004|publisher=Springer|isbn=3-540-00948-5}}&lt;/ref&gt;<br /> <br /> Aspect-orientation is not limited to programming since it is useful to identify, analyse, trace and modularise concerns through requirements elicitation, specification, and design. Aspects can be multi-dimensional by allowing both functional and non-functional behaviour to crosscut any other concerns, instead of just mapping non-functional concerns to functional requirements.{{Citation needed|date=April 2010}}<br /> <br /> One view of aspect-oriented software development is that every major feature of the program, core concern (business logic), or cross-cutting concern (additional features), is an aspect, and by [[aspect weaver|weaving]] them together (a process also called composition), one finally produces a whole out of the separate aspects. This approach is known as pure aspect programming, but hybrid approaches are more common. It is possible for functional concerns to crosscut non-functional or functional concerns (e.g., the need for more features harms mobility). A uniform approach to representation and composition, similar to the pure approach in AOP, is termed multidimensional representation.{{Citation needed|date=April 2010}}<br /> <br /> == References ==<br /> {{reflist}}<br /> <br /> {{aosd}}<br /> [[Category:Aspect-oriented software development]]<br /> [[Category:Aspect-oriented programming]]</div>

imported>MtPenguinMonster