Consistent Adaptation and Evolution of Class Diagrams during Refinement

Abstract

Abstract. Software models are key in separating and solving independent development concerns. However, there is still a gap on how to transition design information among these separate, but related models during development and maintenance. This paper addresses the problem on how to maintain the consistency of UML class diagrams during various levels of refinement. We present a new approach to automated consistency checking called ViewIntegra. Our approach separates consistency checking into transformation and comparison. It uses transformation to translate model elements to simplify their subsequent comparison. Transformation-based consistency checking, in the manner we use it, is new since we use transformation to bridge the gap between software models. No intermediate models or model checkers are required; developers need only be familiar with the models they design with and none other. The separation of transformation and comparison makes our approach to consistency checking more transparent. It also makes our approach useful for both propagating design changes among models and validating consistency. This gives developers added flexibility in deciding when to re-generate a model from scratch or when to resolve its inconsistencies. Although this paper emphasizes the adaptation and evaluation of class diagrams, we found our technique to be equally useful on other models. Our approach is tool supported.

Automated traceability analysis for UML model refinements

“…Some of the relevant articles [41,42] classify refinement at a very low level (e.g., addition and deletion of a model element); others only take into account a few simple refinements which are not organized in a systematic way [14,21]. Another body of work only focuses on refactoring (a special type of refinement), in particular those defined by Fowler [18].…”

“…A number of class diagram refinements are discussed in [14]. Their (semi-)automated identification however requires that traceability links be already established.…”

“…Then, traceability links are established automatically, based on the identified refinements (e.g., part (b) of Figs. 7,13,14). These traceability links are stored in the Traceability Repository for later consumption by the VIA Performing Engine.…”

“…These atomic changes are then used to determine refinement(s) by trying to identify instances of all the refinements available in the Refinement Repository, using the corresponding OCL rules (e.g., part (a) of Figs. 7,13,14). The OCL Engine is used to check those OCL expressions.…”

Software Design and Architecture The once and future focus of software engineering

“…Separate stakeholders likely require (or at least request) views onto an emerging design which are idiosyncratic to their perspectives. Supporting multiple viewpoints while ensuring consistency among them constitutes a current challenge towards which the community has made progress (e.g., the 4+1 model [50], analyses to discover inconsistencies [26], and an understanding that certain forms of inconsistency must be tolerated [15,28]), but for which much work remains to be done.…”