Many object-oriented software applications contain implicit business rules. Although there exist many approaches that advocate the separation of rules, the rules' connections still crosscut the core application functionality, which impedes reuse, either anticipated or not. Moreover, ultimately business rules are implemented in a programming language, which decreases understandability and accessibility by domain experts. We propose a high-level domain model for representing domain concepts, business rules about these concepts, and connections of business rules to the core application in terms of these concepts. The link to the implementation is invisible to domain experts and encapsulated in a mapping. The novelty and contribution of our approach is the use of Aspect-Oriented Programming (AOP) on two levels. First of all, elements from the high-level domain model are mapped to existing implementation entities of an application developed in Object-Oriented Programming (OOP) or AOP. ...