Search by property
This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.
List of results
- Seminar/2008-03-26 + (Separation of concerns is the idea of brea … Separation of concerns is the idea of breaking down a program into</br>encapsulated pieces that overlap in functionality as little as</br>possible. Encapsulated entities, such as classes, methods or modules,</br>are more manageable, easier to test and maintain, and may be reused</br>more easily than a large, entangled program. A cross-cutting concern</br>is something that cannot be encapsulated using normal abstraction</br>mechanisms, thus defeating separation of concerns. A classical example</br>of this is logging (e.g., logging calls and returns to a file while</br>the program is running) - the logging code needs to be added to every</br>applicable method in the program. The logging code for each method may</br>be almost identical, creating an undesirable overlap in</br>functionality. Aspects let a programmer implement a cross-cutting</br>concern as a separate entity, through advice (how a concern should be</br>implemented) and join points (where it should be implemented). I will</br>give an introduction to aspect-orientation and aspect languages, and</br>also talk a bit about domain-specific aspect languages.it about domain-specific aspect languages.)