Explicit and implicit join point designation in aspect-oriented business modeling

Abstract

The aspect-oriented paradigm can be applied at different stages of the software development lifecycle. Its use in the business modeling phase does not have a large number of proposals, and existing ones only cover the part of requirements engineering known as “requirements development”, regardless of “requirements management” practices. Additionally, most of these proposals do not use standard notations. For this reason, in this article we propose a modeling technique that allows the implicit designation of join points to support business requirements management, in addition to adapting the explicit form in a way that is strictly based on BPMN 2.0, the OMG's standard notation.