Table 6.189—DRM_Overload_Priority_Index
Property |
Description |
||||||
Superclass |
|||||||
Class |
· <DRM Overload Priority Index> |
||||||
Subclass |
· none |
||||||
Definition |
The <DRM Overload Priority Index> allows a modeler to assign an overload management priority to the definition of a <DRM Model> or to the reference of a <DRM Model> (a <DRM Geometry Model Instance>). The actual effect of the <DRM Overload Priority Index> within an application is entirely dependent on the application. The <DRM Overload Priority Index> is intended to allow a modeler to mark certain <DRM Model>s as more important than other <DRM Model>s, so that the more important <DRM Model>s will be displayed and the <DRM Model>s of lesser importance may be simplified or dropped from the display in an overload situation. |
||||||
Example(s) |
· In a SEDRIS transmittal designed for a simulation that is more interested in rotary-winged aircraft than fixed-winged aircraft, all of the helicopter <DRM Model>s may have an <DRM Overload Priority Index> of 1, while all of the airplane <DRM Model>s have an <DRM Overload Priority Index> of 2. |
||||||
Inherited field elements |
|
||||||
Field elements |
|
||||||
Associated to (one-way) (inherited) |
· none |
||||||
Associated to (one-way) |
· none |
||||||
Associated by (one-way) (inherited) |
· none |
||||||
Associated by (one-way) |
· none |
||||||
Associated with (two-way) (inherited) |
· none |
||||||
Associated with (two-way) |
· none |
||||||
Composed of (two-way) (inherited) |
· none |
||||||
Composed of (two-way) |
· none |
||||||
Composed of (two-way metadata) (inherited) |
· none |
||||||
Composed of (two-way metadata) |
· none |
||||||
Component of (two-way) (inherited) |
· none |
||||||
Component of (two-way) |
· zero or more <DRM Aggregate Geometry>s · zero or more <DRM Geometry Model Instance>s · zero or more <DRM Model>s |
||||||
Constraints |
· none |
||||||
Notes |
1 1 = Highest Priority; 2 = Next Highest Priority, ... |
||||||
Class diagram |