Some methods of defining and viewing relationships between elements in EAE 3.3 no longer exist in System Modeler. However, despite the differences in modifying and/or viewing relationships in System Modeler, all actual relationships between model elements defined in EAE 3.3 continue to exist.

Matrixes

Matrixes, used in EAE 3.3 to enable you to view and manipulate element relationships, are not migrated as part of the model into System Modeler. The various model views in System Modeler serve a similar purpose to the old Matrixes.

Graphs

Any Graphs from EAE 3.3 that you used to display element relationships are not migrated. Graphs have been replaced in System Modeler by UML diagrams (Refer to Using the UML Designer).

Members of Functional Areas/Activities

Element memberships of existing functional areas and activities are automatically migrated. Basically, this means that the structural relationships of all elements in your model hierarchy are maintained during migration.

This is true for all elements except Profiles, which are now members of the Ispec that they are over. For example, for EVENT ispecs the profiles become members of the internally created “Event” event.

Once migrated, functional areas and activities are converted to folders. You can use folders in System Modeler to group elements into new functional areas and activities. You can nest folders within a single folder—the elements in the nested folders belong to their containing class, just as they do for single level folders.

Using folders allows you to organize complex applications or applications built from a number of discrete functions. You can group related elements within a folder and perform bulk operations on all the elements.

SameAs Relationships

The SameAs relationship is now formed by the setting of the Template property on an attribute.

Existing SameAs relationships between GSDs / SDs and Data Items on ispecs, GLGs, and other items are maintained during migration.

Same As relationships between items and Keywords are also maintained (including when the Keyword has members).

Automatic Lookup

Automatic Lookup dependencies between different ispecs are preserved after migration.