Join Point Interfaces (JPI) represent a currentAspect-Oriented Programming (AOP) methodology for solving modularization issues in classic AOP. Nevertheless, as it is for classic AOP, phases of requirement elicitation and software design are needed for the JPI software development process. In order to advance towards the solution of these issues, this article proposes and applies to a case study JPI UML class diagrams and sequence diagrams. After applying JPI UML diagrams and analyzing the code of a modeled program, our article displays theconsistency between models and the program code derived by means of our methodological approach.