Pizza into Java: translating theory into practice
Proceedings of the 24th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
The object constraint language: precise modeling with UML
The object constraint language: precise modeling with UML
Reflections on the Object Constraint Language
«UML» '98 Selected papers from the First International Workshop on The Unified Modeling Language «UML»'98: Beyond the Notation
Interpreting the Object Constraint Language
APSEC '98 Proceedings of the Fifth Asia Pacific Software Engineering Conference
UML Distilled: A Brief Guide to the Standard Object Modeling Language
UML Distilled: A Brief Guide to the Standard Object Modeling Language
Adaptations to OCL for ensuring quality of geographic data (poster session)
OOPSLA '00 Addendum to the 2000 proceedings of the conference on Object-oriented programming, systems, languages, and applications (Addendum)
Hi-index | 0.00 |
Geographic data is the backbone of sophisticated applications such as car navigation systems and Geographic Information Systems (GIS). Complexity quickly arises in the production of geographic data when trying to ensure quality. We define quality as the integrity and well-formedness of the contents of the geographic data, usually enforced by external applications where constraints ensuring quality (referred to as quality constraints) are implicit, low-level and scattered throughout the application code. This has significant consequences with respect to manageability, adaptability and reuse of these constraints. This paper explains our use of UML class diagrams as conceptual model for geographic data, and how we exploited the Object Constraint Language (OCL) for describing the quality constraints in an explicit, declarative and high-level way. As our use of OCL is slightly different than it was originally intended, we present our adaptations and explain the main issues of evaluating the resulting OCL. We are confident that our specific application of OCL can be put to use in other domains where complex constraints need to be expressed in a knowledge-oriented domain.