Reuse is a fundamental concept of ef?cient software development. Object-oriented implementation languages offer reuse on different levels of granularity:method, class, library. While encapsulation of implementation code within methods and classes enables reuse within a project, user-de?ned libraries are widely used toshare implementation code among different projects.The speci?cation language OCL offers language concepts like de?ned attributes and de?ned operations to enable reuse within a project. However, reuse among differentprojects is not possible since OCL does not support the concept of user-de?ned libraries. There is no standardized way to import user-de?ned OCL constraints intoanother project. In this paper, we argue on the need of a standardized mechanism to make reuse of OCL speci?cations within a different context possible.
展开▼
