2006International Conference on Software Engineering AdvancesRequires access

Checking Data Integrity via the UML Class Diagram

Ahmad Alsaadi

Open publisher page 6 citations

Abstract

The class diagram is the most important UML diagram of an object-oriented software system. It includes both the static and behavioral aspects of its system. This can serve as a pattern for a persistent collection of objects, or as a scheme for a database system, and as a set of communication diagrams at the same time. Different types of behavioral diagrams, such as the use case and sequence diagram, are applied to delineate dynamics of the class diagram. This paper describes a framework in which a UML sequence diagram for ensuring data correctness of data objects is deduced from the UML class diagram. That is the derived diagram can be used to check data structures, or data integrities, of objects in respect to persistent collections of objects, or to database systems, when these collections are updated.

About this research paper

What this paper is about

The class diagram is the most important UML diagram of an object-oriented software system. It includes both the static and behavioral aspects of its system. This can serve as a pattern for a persistent collection of objects, or as a scheme for a database system, and as a set of communication diagrams at the same time. Different types of behavioral diagrams, such as the use case and sequence diagram, are applied to delineate dynamics of the class diagram. This paper describes a framework in which a UML sequence diagram for ensuring data correctness of data objects is deduced from the UML class diagram. That is the derived diagram can be used to check data structures, or data integrities, of objects in respect to persistent collections of objects, or to database systems, when these collections are updated.

Why it matters

OpenAlex reports 6 citations for this work. Citation counts describe recorded attention and do not establish research quality.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

The class diagram is the most important UML diagram of an object-oriented software system. It includes both the static and behavioral aspects of its system. This can serve as a pattern for a persistent collection of objects, or as a scheme for a database system, and as a set of communication diagrams at the same time. Different types of behavioral diagrams, such as the use case and sequence diagram, are applied to delineate dynamics of the class diagram. This paper describes a framework in which a UML sequence diagram for ensuring data correctness of data objects is deduced from the UML class diagram. That is the derived diagram can be used to check data structures, or data integrities, of objects in respect to persistent collections of objects, or to database systems, when these collections are updated.

Key concepts: Class diagram, Communication diagram, Sequence diagram, Computer science, System context diagram, Applications of UML, Correctness, UML tool

Related papers

Back to paper searchBrowse research topicsOriginal source
Checking Data Integrity via the UML Class Diagram — Research Paper | ScholarLens