ENOVIA LCA

The ENOVIA Model Objects

The ENOVIA model objects are modeled as classes declared in XML files and gathered in packages that deal with a given ENOVIA LCA modeler. Each class usually has one or several attributes. The structure of a package is as follows:

<Package Name="ACTION"
         Uuid="80A92508-0000-02A4-38B1372C0000C54B"
         ...
         ExpositionLevel="CAA">
  <Class Name="AFLAction"
         Uuid="80A92508-0000-02A4-38B1372C0000CDA5"
         ...
         ExpositionLevel="CAA">
    <Simple Name="V_name"
            Uuid="80A92508-0000-02A4-38B1372C000324EB"
            ...
            ExpositionLevel="CAA">
    </Simple>
    ...
    <Relationship Name="C_histories"
                  ...
                  TargetRef="80A92508-0000-02A4-38B1372C0003EDFB"
                  ...
                  ExpositionLevel="CAA">
    </Relationship>
    ....
  </Class>
  ...
</Package>

This declares that the ACTION package contains the AFLAction class that has the V_name and the C_histories attributes. V_name is a Simple model object attribute because it only contains a value, such as a string. C_histories is a Relationship model object attribute because it points to another class thanks to the TargetRef XML attribute, within or outside of the ACTION package, that contains the Uuid of the pointed class.

[Top]

The Exposed Packages

The following packages are exposed:

• Action modeler: ACTION
• Workflow modeler: VPMFWL
• Document modeler: DOCDIR
• Engineering changes: APLAFL and APLECO
• Configuration modeler: CONFIG
• Product modeler: PRODUCT and TEMPLAT
• Graph modeler: GRAPH
• Security/P & O: PEOPLE

In each of these packages, a subset of objects are exposed, and for each object, a subset of its attributes are exposed.

[Top]

The UML Representation of the Exposed Packages

Each package is described using an UML representation.

• ACTION
• APLAFL
• APLECO
• CONFIG
• DOCDIR
• GRAPH
• PEOPLE
• PRODUCT
• TEMPLAT
• VPMFWL

The following conventions apply to these UML representations:

• Only Relationship attributes are shown
• Classes that from other packages are shown with a blue background
• Classes that are linked but not exposed are shown with a grey background

[Top]

The Description of the Exposed Packages

The packages are also described thanks to information extracted from the XML files, making a set of interlinked html files. The ENOVIA LCA Exposed Model Object Reference contains a link to each package that in turn contains links to each of its objects.

The following conventions apply to this description:

• The class detailed description include:
  • The class name
  • The class type
  • Possibly the class role
  • The class UUID
  • The class visibility in the user interface: Public if the class is visible, and Private otherwise
  • The possible base class
  • The class possible extensibility: Yes or No
  • The class possible CAA derivation: Yes or No
• An index of the exposed attributes appears before the attribute descriptions, which may show the following icons, each having a specific meaning that describes a characteristic of the attribute. Locating the mouse above the icon shows the meaning in a tooltip. The meanings are:

  	The attribute is mandatory
  	The attribute is unique
  	The attribute is inherited, and the tooltip displays the object from which it is inherited
  	The attribute is a relationship to another object. The tooltip display the object and the package to which this object belongs. If the object is exposed, clicking the icon displays the object documentation
  	The attribute is an external relationship

• The attribute detailed description includes the following information
  • Possibly the attribute role
  • The attribute type: String, Integer, Boolean, Relationship, external relationship,
  • The attribute UUID
  • The attribute visibility in the user interface: Public if the attribute is visible, and Private otherwise
  • The mandatory characteristic: Yes or No
  • The attribute length
  • The attribute access mode: Read or Write
  • The possible aggregation type
  • The target object if the attribute is a relationship
  • The possible multivaluation: Yes or No

[Top]

References

History

Copyright © 1994-2003, Dassault Systèmes. All rights reserved.