Date: Tue, 19 Mar 2024 04:14:09 +0100 (CET)
Message-ID: <162596239.4456.1710818049890@nm-docs>
Subject: Exported From Confluence
MIME-Version: 1.0
Content-Type: multipart/related;
boundary="----=_Part_4455_25117587.1710818049890"
------=_Part_4455_25117587.1710818049890
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Content-Location: file:///C:/exported.html
A Class diagram falls under the structural diagramming fa=
mily. It is a graphic representation of the static structural mod=
el. It shows
classes =
and
interfaces, a=
long with their internal structure and relationships. The classes represent=
types of objects that are handled in a system. A Class diagram does not sh=
ow temporal information, it describes only the classification. The instance=
s of those types (objects) are instantiated only on the runtime and are rep=
resented by an object and the interaction diagrams.
The classes can be related to each other in a number of ways: associated (=
connected to each other), dependent (one class depends/uses another class),=
specialized (one class is a subtype of another class), or packaged (groupe=
d together as a unit =E2=80=93 package). A Class diagram does not express a=
nything specific about the relationships of a given object, but it does abs=
tractly describe the potential relationships of one object with other objec=
ts.
A system typically has a number of Class diagrams =E2=80=93 not all classe=
s are inserted into a single Class diagram. A class can have multiple =
levels of meaning and participate in several Class diagrams. A Class diagra=
m is the logical map of an existing or future source code.=20
Related pages
------=_Part_4455_25117587.1710818049890--