Aspect-Oriented Programming (AOP) has been proposed in literature to overcome modularization shortcomings such as the tyranny of the dominant decomposition. However, the new language constructs introduced by AOP also raise new issues on their own–one of them is potential interference among aspects. In this paper we focus on a special case of this problem and demonstrate how undefined advice precedence can easily jeopardize correctness of a program. We present an interference analysis to detect and thus help programmers to avoid advice order related problems. 1 Motivation Aspect-Oriented Programming (AOP) as introduced in [10] has been promoted in recent years as a mechanism to overcome the tyranny of the dominant decomposition [15]. Even in well-designed systems it can happen that some requirements cannot be implemented well-localized as a separate module. Such requirements are called crosscutting concerns, as their implementation scatters code cross several modules. This scattered...