Keeping track of crosscutting requirements in UML models via context-based constraints

Abstract

One crosscutting requirement (also called aspect) affects several parts of a software system. Handling aspects is well understood at source-code level or at runtime. However, only a few aspectoriented approaches handle other software artefact types, like UML models, configuration files, or database schema definitions. Instead of re-writing the same aspect newly for each artefact type, this paper suggests to write down aspects independent of artefact types.But, wait a minute: Where do we weave in an aspect if its pointcut doesn't refer to artefact details? Which places does such an aspect affect? This paper suggests expressing aspects via ContextBased Constraints (CoCons). They select their constrained system elements according to the element's context. For instance, CoCons affect all system elements used in a certain department, workflow, or location. CoCons are easy to grasp for users and customers because they express business requirements without referring to technical details. This paper focuses on how to express crosscutting requirements in UML models via CoCons and compares CoCons to the Object Constraint Language OCL.

Verification and validation of IM-DeCRuD approach using DESMET for its applicability

“…Requirements crosscutting are related to each other within artifact as well as correlated artifacts across multiple phases [3][4][5]. Consequently, any changes to requirements crosscutting may yield direct or indirect impact to other artifacts.…”