About

This is the archive page for The Enterprise Architect. Click to go to the frontpage of this site.

Last Comments

Johan den Haan (Aspect-Oriented P…): Viakos, It depends on how…
viakos (Aspect-Oriented P…): great script. !!! it’s ma…
Gertjo Tigelaar (Heuristic): very true, however, testi…
JoHaan (The art of Object…): Michiel, thanks for the c…
Michiel (The art of Object…): OOP basically is about mo…

Calendar

« September 2010
S M T W T F S
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30    

Archives

Next Archive Previous Archive

01 Apr - 30 Apr 2007
01 Feb - 28 Feb 2007
01 Jan - 31 Jan 2007
01 Dec - 31 Dec 2006
01 Nov - 30 Nov 2006
01 Oct - 31 Oct 2006
01 Sep - 30 Sep 2006

triDesign
Mendix
Random observations
Extreme Business Make-over

Miscellany

Powered by Pivot - 1.40.1: 'Dreadwind' 
XML: RSS Feed 

11 January 07 - 19:30Aspect-Oriented Programming (AOP)

Tags: , , , ,
One of the primary evolutions in software engineering is the separation and encapsulation of concerns. This has been progressed from machine language to imperative languages with procedures/methods. After that we’ve seen the progression from imperative languages to object-oriented languages. In object-oriented languages new ‘levels of encapsulation’ are introduced: classes and packages. Nowadays we see the upcoming thinking in components. But unless all this techniques we still have concerns defying these forms of encapsulation. We call them crosscutting concerns, because they cut across many modules in a program. Logging is the most used example of such a concern. Logging affects every logged part of the system and thereby crosscuts all logged classes and methods. So we still have redundant code in our programs. How can we solve that?

Gregor Kiczales and his team at Xerox PARC originated the concept of Aspect-Oriented Programming (AOP) read more

- Software Engineering - two comments / No trackbacks - §

Heuristic

Quality can't be tested in, it has to be built in