For Full-Text PDF, please login, if you are a member of IEICE,|
or go to Pay Per View on menu list, if you are a nonmember of IEICE.
Detecting Architectural Violations Using Responsibility and Dependency Constraints of Components
Shinpei HAYASHI Fumiki MINAMI Motoshi SAEKI
IEICE TRANSACTIONS on Information and Systems
Publication Date: 2018/07/01
Online ISSN: 1745-1361
Type of Manuscript: Special Section PAPER (Special Section on Knowledge-Based Software Engineering)
architecture pattern, code smell, program dependence graph,
Full Text: PDF(915.8KB)
>>Buy this Article
Utilizing software architecture patterns is important for reducing maintenance costs. However, maintaining code according to the constraints defined by the architecture patterns is time-consuming work. As described herein, we propose a technique to detect code fragments that are incompliant to the architecture as fine-grained architectural violations. For this technique, the dependence graph among code fragments extracted from the source code and the inference rules according to the architecture are the inputs. A set of candidate components to which a code fragment can be affiliated is attached to each node of the graph and is updated step-by-step. The inference rules express the components' responsibilities and dependency constraints. They remove candidate components of each node that do not satisfy the constraints from the current estimated state of the surrounding code fragment. If the inferred role of a code fragment does not include the component that the code fragment currently belongs to, then it is detected as a violation. We have implemented our technique for the Model-View-Controller for Web Application architecture pattern. By applying the technique to web applications implemented using Play Framework, we obtained accurate detection results. We also investigated how much does each inference rule contribute to the detection of violations.