Date: Fri, 29 Mar 2024 11:20:44 +0100 (CET) Message-ID: <1539589502.3659.1711707644625@263d865a522e> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_3658_1934878446.1711707644625" ------=_Part_3658_1934878446.1711707644625 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The point of using UML for integration modeling is to unify the =
view on software artifacts. This includes also a unification of various dat=
a models as class structures. This chapter shows how different data models =
are mapped to UML classes by Bridge Importer modules.
For example, the Importers map WSDL definitions, XML Schemas, or SAP IDoc g=
rammars to UML class models. The semantic differs in these models. The UML =
classes are handled by stereotypes and tagged values.
This section is divided into the following parts: