A proved approach for building correct instances of UML Associations: Multiplicities satisfaction

Research output: Chapter in Book/Report/Conference proceedingConference contributionpeer-review

Abstract

In UML modeling, class diagrams permit to capture the entities involved in a system but also the associations they have with each other. These associations are characterized by a multiplicity on each role to state the min-max number of instances of the opposite class that can be linked to each instance of the class associated with the role. Since these multiplicities may be conflicting, it becomes necessary to check the global consistency of a class diagram. Such verification will ensure that it is possible to find an instantiation of the diagram that satisfies all the multiplicities. In this paper, we describe an automatized approach that permits to validate a class diagram by exhibiting a particular instance. Basically, this approach proceeds in two main steps: first, the multiplicities are represented as a mathematical model, then a constraint solver is used to determine whether it has at least one solution. The correctness of the approach, which is supported by an automatic tool, has been carried out using the B formal method.

Original languageEnglish
Title of host publicationProceedings - 21st Asia-Pacific Software Engineering Conference, APSEC 2014
EditorsYann-Gael Gueheneuc, Gihwon Kwon, Sungdeok Cha
PublisherIEEE Computer Society
Pages438-445
Number of pages8
ISBN (Electronic)9781479974252
DOIs
Publication statusPublished - 1 Jan 2014
Event21st Asia-Pacific Software Engineering Conference, APSEC 2014 - Jeju Island, Korea, Republic of
Duration: 1 Dec 20144 Dec 2014

Publication series

NameProceedings - Asia-Pacific Software Engineering Conference, APSEC
Volume1
ISSN (Print)1530-1362

Conference

Conference21st Asia-Pacific Software Engineering Conference, APSEC 2014
Country/TerritoryKorea, Republic of
CityJeju Island
Period1/12/144/12/14

Fingerprint

Dive into the research topics of 'A proved approach for building correct instances of UML Associations: Multiplicities satisfaction'. Together they form a unique fingerprint.

Cite this