Specification and automatic checking of architecture constraints on object oriented programs

Abstract

Context: Architecture constraints are specifications of conditions to which an architecture model must adhere in order to satisfy an architecture decision imposed by a given design principle. These constraints can be specified with predicate languages like OCL at design time and checked on design artifacts. Objective: Many works in the literature studied the importance of checking these constraints to guarantee quality on design models, and to prevent technical debt and maintenance difficulties. In this paper, we propose a process whose ultimate goal is to enable the checking of these constraints in the implementation stage. Method: The proposed process takes as input a textual specification of an architecture constraint specified at design stage. It translates this specification into meta-programs and then it uses them with aspect-oriented programming to check constraints at the implementation stage and at run-time on objectoriented programs. Results: We experimented an implementation of this process on a set of 12 architecture constraints. The results of this experimentation showed that our process is able to statically and dynamically detect architecture constraint violations on toy object-oriented applications, but also on real-world ones. Conclusion: The automatic checking of architecture constraints is important

Standard Verification using Model Based Systems Engineering

“…3 Architecture constraints are valuable for preserving architecture styles, patterns or general design principles. 4 Cameo Systems Modeler (CSM) labels architecture constraints as validation rules, which are organized as a set in a validation suite. The built-in CSM validation suites are coded as a part of the Unified Modeling Language (UML) base of the Systems Modeling Language (SysML).…”