Cross-cutting concern - Factbites
 Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Cross-cutting concern


    Note: these results are not from the primary (high quality) database.


  
 Concern - Wikipedia, the free encyclopedia
A concern is cross-cutting to the extent that it scattered and tangled amongst other concerns.
For example, when programmers simply insert calls to cross-cutting concerns (such as logging, object persistence, etc.) everywhere in the source code where needed, the resultant program leads to a highly-coupled system.
Cross-cutting concerns are generally considered a bad thing when creating software.
en.wikipedia.org /wiki/Concern   (179 words)

  
 Gender and Development- ADB.org
Given that poverty is one of the major causes of human trafficking, especially in women and children, it is a global development concern.
To better understand the nature and underlying causes of trafficking in women and children and identify how ADB can contribute to addressing anti-trafficking concerns through its country programs and regional policy dialogue, ADB started a Regional Technical Assistance (RETA) Project in South Asia in July 2001.
ADB recognizes that it can significantly contribute to preventing and reducing vulnerability to trafficking through its poverty reduction operations in various sectors.
www.adb.org /Gender/reta5948.asp   (437 words)

  
 Cross-cutting concern - Wikipedia, the free encyclopedia
If writing an application for handling medical records, the bookkeeping and indexing of such records is a core concern, while logging a history of changes to the record database or user database, or an authentication system, would be cross-cutting concerns since they touch more parts of the program.
In computer science, cross-cutting concerns, or crosscutting concerns, are aspects of a program, that do not relate to the core concerns directly, but are needed for proper program execution.
Bergmans, L., M. Aksit (2001): Composing Multiple Concerns Using Composition Filters, http://trese.cs.utwente.nl/ (24.
en.wikipedia.org /wiki/Cross-cutting_concern   (238 words)

  
 East Timor - Livelihood Security - Our Work - ConcernUSA.org
HIV/AIDS awareness will also be introduced into this program as part of Concern's cross-cutting initiatives to ensure that this issue becomes part and parcel of all activities from education, health and sanitation, to disaster preparedness.
Concern has been running a livelihood security program in two remote rural areas of the country (Turiscai and Luro sub-districts) since 2003.
Concern Marathon Madness team will set off again on Sunday, November 6 in the ING New York City Marathon.
www.concernusa.org /ourwork/programs.asp?pid=91   (400 words)

  
 Aspect
Another possible view is, that every major feature of the program, core concern (business logic) or cross-cutting concern (additional features), is an aspect, and by weaving them together, you finally produce a whole out of the separate aspects.
In computer science, an aspect is part of a program that cross-cuts its core concern s, therefore violating its Separation of concerns.
Isolating such aspects as logging and persistence from business logic is the aim of the aspect-oriented programming paradigm.
www.serebella.com /encyclopedia/article-Aspect.html   (979 words)

  
 MSDN Home
The level of coupling when a concern is maintained in a separate class is quite low.
In general, the functionality required by the concern will be implemented in a single class.
The difficult part is in integrating the functionality provided by the concern into existing classes without impacting the class itself.
msdn.microsoft.com /canada/btl/novwinner   (2128 words)

  
 NRC: EA-030-060 - Callaway (Union Electric Co.)
Our primary cross cutting concern related to the White finding was the failure of your audit programs and supervisory oversight of surveillance activities to identify the inaccurate tone alert radio database prior to the occurrence of an external event (change in electric service providers) which prompted its discovery.
The cross cutting aspects of the White finding were documented in Section 4OA2 to facilitate future NRC inspection.
This letter confirmed your acceptance of the White finding as preliminarily characterized, but also requested clarification of our characterization of the cross cutting aspects of the finding which are documented in the subject inspection report.
www.nrc.gov /reading-rm/doc-collections/enforcement/actions/reactors/ea03060.html   (1006 words)

  
 Glossary of Terms
A cross-cutting concern that does not directly relate to the core concern.
However, there usually exists additional, required algorithms ("cross-cutting concerns") that support underlying functionality.
A concern has a purpose which it must fulfill during the life of a program.
www.cs.utah.edu /~swalton/Documents/Glossary.html   (95 words)

  
 Aspect oriented programming in C#, Attribute programming, AOP in C#, AOP in VB.net, AOP in .NET
In compile time Core concern code and the cross cut code is weaved before been compiled to MSIL code.
So create modules for Cross cut and Core Concerns separately and then feed both the modules to the compiler.
In short all the cross cut code is moved to a separate module, thus increasing more modularity and bringing in ease of maintenance.
www.geocities.com /aspectdotnet   (1546 words)

  
 Committee on Information
In fact, a UN that is kept permanently in chronic insolvency or at the brink of bankruptcy, and which therefore cannot effectively respond to the legitimate developmental aspirations of the majority of its members, the developing nations, is a cross cutting concern, affecting all areas of activity of our organisation.
We fully share his concern, as expressed in paragraph 61, that existing staffing and budgetary procedures hamper the ability of the organization to respond as effectively and as quickly as desired.
With regard to paragraph 23.8 of the same report, we strongly believe that the themes of campaigns must be truly reflective of the concerns of the international community.
www.un.int /india/ind432.htm   (1370 words)

  
 Enabling Aspect-Oriented Programming in WebLogic Server using the JRockit Management API
A cross-cutting concern is a concern that affects several classes or modules, a concern that is not well localized and modularized.
It solves this by adding an extra dimension to the design space and introduces constructs that allows us to define the cross-cutting concerns, to lift them out into the new dimension and to package them in a modular way.
A concern is a particular concept or area of interest.
dev2dev.bea.com /pub/a/2004/05/boner_vasseur.html   (2381 words)

  
 A Hybrid Approach to Separation of Concerns: The Story of SADES (SMEALSearch) - Pal,Rangaswamy,Giles,Debnath
Although all these approaches form suitable candidates for separating cross-cutting concerns in a system, one approach can be more suitable for implementing certain types of concerns as compared to the others.
The approach is based on using the most suitable approach for implementing each cross-cutting concern in a system.
The discussion is based on using three different approaches: composition filters, adaptive programming and aspect-oriented programming to implement cross-cutting concerns in SADES, a customisable and extensible object database evolution system.
gunther.smeal.psu.edu /75093.html   (281 words)

  
 2003_03_01_blog_archive.php
Salvation would be a cross-cutting concern, and a completely valid aspect of the divine, but the distinction between members of the Trinity goes far deeper.
Having been reading the news and rumnours sites for a while it's interesting to see the final cut of the movie; recent headline news of the shuttle disaster caused a major headache at the film studio and the last minute reshoot and reedit to avoid a cultural faux pas.
For example, logging, where a message should be written to a log file when particular points are reached in an application.
paul.caffeinatedbliss.com /2003_03_01_blog_archive.php   (1482 words)

  
 Research Statement for David Coppit
In contrast, software plans is a language-independent approach that treats cross-cutting concerns as inherently different than the functionality that has been traditionally encapsulated using functional and object-oriented language abstractions.
My research seeks to replace the single code listing that has dominated software development for thirty years, instead using multiple orthogonal views, each of which presents a cross-cutting concern of interest along with any contextual code that is necessary to understand it.
In particular, he has designed and implemented an algorithm for automatically computing the contextual code for cross-cutting concerns of interest.
www.cs.wm.edu /~coppit/research_statement.php   (2954 words)

  
 How to Address Crosscutting Concerns in Aspect Oriented Software Development
How to Address Crosscutting Concerns in Aspect Oriented Software Development
A successful solution to this problem involves two things: an engineering technique to separate such concerns from requirements all the way to code and a composition mechanism to merge the design and implementation for each concern to result in the desired system.
They keep concerns about a kind of object or an abstraction of a real-world phenomena separate.
www.informit.com /articles/article.asp?p=375541&rl=1   (1122 words)

  
 Mitch is tightly coupled to extender providers
In the area of cross-cutting concerns there are approaches in.NET other than extender providers (such as attributes + interception, or attributes + reflection in some kind of container class or pipeline).
Extender providers are a way of applying a “cross-cutting concern” or “aspect” to a series of otherwise un-related or loosely related controls.
Not the most elegant solution (since we're now adding non-obvious magical “hey why did all my buttons just change colour” behavior to our base form class) but sometimes it is appropriate.
jcooney.net /archive/2005/07/06/4464.aspx   (517 words)

  
 Attribute Oriented Programming != Aspect Oriented Programming
The key to AOP is to capture and modularize cross-cutting concerns.
The idea is that you should only do so to aid in the implementation of cross-cutting concerns.
We call this cross-cutting because the modularization we are seeking cross-cuts the hierarchical structure of OO (actually AOP complements procedural languages as well…but that is another topic).
weblogs.asp.net /Mnolton/archive/2004/04/23/119181.aspx   (1652 words)

  
 Component Based Software Development - Introduction: Adaptation and Assembly
An aspect is a modular unit representing a cross-cutting concern — separable units of behaviour common to multiple classes.
The join point model provides a framework for defining the structure of cross-cutting concerns and describing the hooks where enhancements may be made.
Session beans cover the first model, which is concerned with the execution of operations on behalf of the client, and entity beans cover the second, which covers client access to entities within databases.
cbs.colognet.org /adaptation.php   (1672 words)

  
 Aspect-oriented Programming
An unwanted result of cross-cutting concerns written in a traditional programming language is tangling.
It is being realized that AOP can even be useful in configurable programs, such as platform-portable, multiple-functionality, mobile, or distributed applications in which cross-cutting concerns span only small parts of the system.
That is, programmers can develop aspects to create software modules for issues that cut across various parts of an application.
www.peterindia.net /AOP.html   (1076 words)

  
 Quoderat » Aspects
But I’ve also found that the biggest problem seems to be that AOP is seen as dealing with a specific set of cross-cutting concerns only (that would be the logging/security/caching type of group).
I buy a lot of the argument that it makes sense for cross-application concerns, but I don’t know how many concerns there really are: Logging, Security, and possibly performance monitoring seem to be about it.
Concern models do provide some support here as do some approaches to bring AOSD to the architectural languages (can’t find the reference just now… It was at the last AOSD).
www.megginson.com /blogs/quoderat/archives/2005/07/29/aspects   (1240 words)

  
 FTPOnline - VSLive! SF 2005 - 6 Myths of Aspect-Oriented Programming
AOP certainly is different from the traditional object paradigm, but it's a solution to a distinct class of problem: the cross-cutting concern.
Instead, AOP solves only one class of problem: the cross-cutting concern.
This is "separation of concerns" at its finest.
www.fawcette.com /reports/vslivesf/2005/barnaby   (848 words)

  
 Master's Projects
Other concerns, such as logging, will intertwine with many highly unrelated modules.While the tendency in OOP is to find commonality among classes and push it up in the inheritance tree, AOP attempts to realize scattered concerns as first-class elements, and eject them horizontally from the object structure.
AOP is based on the idea that computer systems are better programmed by separately specifying the various concerns properties or area of interest of a system and some description of their relationships, and then relying on mechanisms in the underlying AOP environment to automatically weave or compose them together into a coherent program.
Multidimensional Separation of Concerns (MDSOC) addresses the issues of software evolution and permits effective encapsulation of arbitrary kinds of concerns simultaneously (even when concerns were not anticipated originally) and the integration of separate concerns.
gaia.ecs.csus.edu /~zhangc/projects.html   (10447 words)

  
 ONJava.com: Aspect-Oriented Annotations
A cross-cutting concern is the code sprinkled throughout your codebase, code that has structure, but cannot be organized or declared using traditional OO techniques.
Metrics present a perfect, tiny, small example of what a cross-cutting concern is. JBoss AOP provides a simple way of encapsulating and applying such a concern in an implicit way so that something like metrics code does not pollute your codebase.
If you wanted to expand this functionality to include a method or failure count, or even to register these statistics to a more sophisticated reporting mechanism, you'd have to modify a lot of different files (again).
www.onjava.com /pub/a/onjava/2004/08/25/aoa.html   (980 words)

  
 Department of State Washington File: Text: "Serious Concern" about Some Chinese WTO Compliance Efforts
While concerns over market access for U.S. agriculture products are not unique to China, particularly serious problems were encountered on many fronts, including China's regulation of agricultural goods made with biotechnology, the administration of China's tariff-rate quota (TRQ) system for bulk agricultural commodities, the application of sanitary and phytosanitary measures and inspection requirements.
At the same time, serious concerns arose in some areas, where implementation had not yet occurred or was inadequate.
China is taking steps to address both of these concerns, through more effective inter-ministerial mechanisms at the national level, and through a more concerted effort to reinforce the importance of WTO-consistency with sub-national authorities.
usinfo.org /wf-archive/2003/030319/epf312.htm   (1566 words)

  
 Encyclopedia article on Concern [EncycloZine]
Programmers write programs in order to address one or more core concerns (such as credit card billing, or sending email), whereas cross-cutting concerns form aspects of a program that do not relate to the core concerns directly, but which proper program execution nevertheless requires.
Isolating these cross-cutting concerns forms the goal of aspect-oriented programming.
In computer science, a concern is a problem which a program tries to solve.
encyclozine.com /Concern   (164 words)

  
 AOP Continued
A cross-cutting concern is an indication that we're trying to model something in the wrong dimension.
The first article was meant to give a glimpse of what AOP does for cross-cutting concerns.
The basic premise is this: say you build a domain model for an HR system, and later are asked to build a system for sales.
www.volantec.biz /aop2.htm   (495 words)

  
 LtU Classic Archives
But I still think that if you have a lot of cross-cutting concerns then you're using the wrong paradigm.
What concerns me is that maybe there's a simpler program waiting to get out rather than a need to slice up the complexity itself into "aspects".
And although it's not sanctioned by the AOP powers that be, it is the most tangible AOP-related work I've seen, and it actually whet my appetite enough to read more of the "official" stuff.
lambda-the-ultimate.org /classic/message9237.html   (1854 words)

  
 A look at aspect-oriented programming
AOP is designed to handle cross-cutting concerns by providing a mechanism, the aspect, for expressing these concerns and automatically incorporating them into a system.
The danger is that you may develop software that incorporates cross-cutting concerns, and your implementation approach will either cease to be supported or will change significantly.
The multi-dimensional separation of concerns paradigm, for example, has been under development at IBM Research, and an implementation is available in the HyperJ tool (http://www.alphaworks.ibm.com/tech/hyperj).
www-128.ibm.com /developerworks/rational/library/2782.html   (3420 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.