HLA

Card Set Information

Author:
jjkaile
ID:
265150
Filename:
HLA
Updated:
2014-03-05 10:04:10
Tags:
HLA rti federate DIS
Folders:

Description:
Definitions in IEEE 1516.2010
Show Answers:

Home > Flashcards > Print Preview

The flashcards below were created by user jjkaile on FreezingBlue Flashcards. What would you like to do?


  1. candidate received class
    The sent class of an interaction, if subscribed. If the sent class of an interaction is not subscribed, the closest super class of the sent class of the interaction to which the joined federate is subscribed. Candidate received class pertains to interactions only.
  2. class attribute
    A named characteristic of an object class denoted by a pair composed of an object class designator and an attribute designator.
  3. collection
    A group of elements in which an element may occur multiple times (this definition corresponds to the mathematical notion of a bag).
  4. current federation object model (FOM)
    The union of the FOM modules and one Management Object Model (MOM) and Initialization Module (MIM) that have been specified in the creation of the federation execution or by any federate that has joined the federation execution. The sum operation is carried out according to the rules as prescribed in IEEE Std 1516.2-2010. When all FOM modules have been provided,the current FOM will be equal to the FOM; and before this step has happened, the current FOM will be a true subset of the FOM.
  5. corresponding instance attributes of a class attribute
    The instance attributes that, from the perspective of a given joined federate, are a

    a) Unowned instance attributes of object instances that have a known class at the joined federate equal to the object class of the class attribute and that have the same attribute designator as the class attribute, or

    b) Instance attributes owned by the joined federate that belong to object instances that have a known class at the owning federate equal to the object class of the class attribute and that have the same attribute designator as the class attribute
  6. corresponding class attribute of an instance attribute
    The class attribute that, from the perspective of a given joined federate, is the class attribute of the joined federate’s known class for the object instance containing the instance attribute that has the same attribute designator as the instance attribute.
  7. constrained set of pairs
    A group of pairs in which no two pairs have the same first component (this definition corresponds to the mathematical notion of a function). An example would be a group of instance attribute and value pairs; each instance attribute may have at most one value associated with it.
  8. compliant object model
    A High Level Architecture (HLA) federation object model (FOM) or simulation object model (SOM) that fully conforms with all of the rules and constraints specified in object model template (OMT).
  9. collection of pairs
    A group of pairs in which multiple pairs may have the same first component and a givenpair may occur multiple times.
  10. coadunate
    To attach an object instance handle and an object instance name to an object instance. The object instance name can be provided specifically by the federate or implicitly by the runtime infrastructure(RTI).
  11. class hierarchy
    A specification of a class-subclass or “is-a” relationship between classes in a given domain.
  12. class
    A description of a group of items with similar properties, common behavior, common relationships,and common semantics.
  13. best effort
    A transportation type that does not provide any guarantee regarding delivery (messages may be out of order, duplicate, or dropped).
  14. base object model (BOM)
    A piece-part of a conceptual model, simulation object model (SOM), or federation object model (FOM) that can be used as a building block in the development and/or extension of a simulation or federation.
  15. available parameters
    The set of declared parameters of an interaction class in union with the set of inherited parameters of that interaction class
  16. available dimensions
    a) Pertaining to an attribute: the dimensions associated with the class attribute in the federation object model (FOM). The available dimensions of an instance attribute are the available dimensions of the corresponding class attribute.

    b) Pertaining to an interaction class: the dimensions associated with that interaction class in the FOM.The available dimensions of a sent interaction are the available dimensions of the interaction classspecified in the Send Interaction With Regions service invocation.
  17. available attributes
    The set of declared attributes of an object class in union with the set of inherited attributes of that object class.
  18. attribute ownership
    The property of an instance attribute that gives a joined federate the capability to supply values for that instance attribute to its federation execution. See also: instance attribute.
  19. attribute
    A named characteristic of an object class or object instance. See also: class attribute; instance attribute.
  20. active subscription
    A request to the runtime infrastructure (RTI) for the kinds of data (class attributes as well as interactions) that the joined federate is currently interested in receiving. The RTI uses these data along with publication data received from other joined federates to support services, such as

    a) Start/Stop Registration

    b) Turn On/Off Updates

    c) Turn On/Off Interactions
  21. accuracy
    The measure of the maximum deviation of an attribute or a parameter value in the simulation orfederation from reality or some other chosen standard or referent.
  22. datatype
    A representation convention for a data element establishing its format, resolution, cardinality, and ordinality
  23. current federation object model (FOM) Document Data (FDD)
    The data and information used to configure the federation execution that is the union of the FOM modules and one Management ObjectModel (MOM) and Initialization Module (MIM) that have been specified in the creation of the federation execution or by any federate that has joined the federation execution. The sum operation is carried out according to the rules as prescribed in IEEE Std 1516.2-2010. When all FOM modules have been provided,the current FDD will be equal to the FDD; and before this step has happened, the current FDD will be a true subset of the FDD.
  24. declared attributes
    The set of class attributes of a particular object class that are listed in the federationobject model (FOM) as being associated with that object class in the object class hierarchy tree.
  25. declared parameters
    The set of parameters of a particular interaction class that are listed in the federation object model (FOM) as being associated with that interaction class in the interaction class hierarchy tree.
  26. default range
    A range lower bound and a range upper bound, defined in the federation object model(FOM) Document Data (FDD) and specified in terms of [0, the dimension’s upper bound), for a dimension.
  27. default region
    A multidimensional region provided by the runtime infrastructure (RTI) that is composed of one range for each dimension found in the federation object model (FOM) Document Data (FDD). The bounds of each of these ranges are [0, the range’s dimension’s upper bound). There is no way for a federate to refer to the default region.

    NOTE—See 9.1 in IEEE Std 1516.1-2010.
  28. delete
    To invoke the Delete Object Instance service to eliminate a particular object instance. See also:remove.

    NOTE—See 6.10 in IEEE Std 1516.1-2010.
  29. designator
    A generic view of arguments referenced in service descriptions. This view improves clarity in situations when arguments (mostly identifiers) to services have different views (implementations) due to a particular programming language or application programmer’s interface (API).
  30. dimension
    A named interval. The interval is defined by an ordered pair of values, the first being the dimension lower bound and the second being the dimension upper bound. A runtime infrastructure (RTI) provides a predefined interval, whose lower and upper bounds are fixed as [0, the dimension’s upper bound)as specified in the federation object model (FOM) Document Data (FDD). This interval provides a single basis for communication of all dimension-related data with an RTI. All normalized intervals communicated to the RTI will be subsets of this interval.

    NOTE—See 9.1 of IEEE Std 1516.1-2010.
  31. discover
    To receive an invocation of the Discover Object Instance † 5 service for a particular object instance.

    NOTE—See 6.5 of IEEE Std 1516.1-2010.
  32. discovered class
    The class that was an object instance’s candidate discovery class at a joined federate when that object instance was discovered by that joined federate. See also: candidate discovery class.

    NOTE—See 5.1.2 in IEEE Std 1516.1-2010.
  33. exception
    Notification of any irregularity that may occur during a service invocation.
  34. fault
    An event that prevents the entire federation from executing in a High Level Architecture (HLA) compliant manner.
  35. federate
    An application that may be or is currently coupled with other software applications under afederation object model (FOM) Document Data (FDD) and a runtime infrastructure (RTI). See also:federate application; joined federate.
  36. federate application
    An application that supports the High Level Architecture (HLA) interface to a runtime infrastructure (RTI) and that is capable of joining a federation execution. A federate application may join the same federation execution multiple times or may join multiple federation executions. However, each time a federate application joins a federation execution, it is creating a new joined federate. See also: joined federate.
  37. federation
    A named set of federate applications and a common federation object model (FOM) that are used as a whole to achieve some specific objective.
  38. federation execution
    The actual operation, over time, of a set of joined federates that are interconnected bya runtime infrastructure (RTI).
  39. federation objectives
    The statement of the problem that is to be addressed by the establishment andexecution of a federation.
  40. federation object model (FOM)
    A specification defining the information exchanged at runtime to achieve a given set of federation objectives. This information includes object classes, object class attributes,interaction classes, interaction parameters, and other relevant information. The FOM is specified to the runtime infrastructure (RTI) using one or more FOM modules. The RTI assembles a FOM using these FOM modules and one Management Object Model (MOM) and Initialization Module (MIM), which is provided automatically by the RTI or, optionally, provided to the RTI when the federation execution is created.
  41. federation object model (FOM) Document Data (FDD)
    The data and information in a FOM that are used by the Create Federation Execution service and successive Join Federation Execution service invocations to configure the federation execution.
  42. federation object model (FOM) module
    A partial FOM (containing some or all object model template(OMT) tables) that specifies a modular component of a FOM. A FOM module may contain classes not inherent to it but upon which the FOM module depends, i.e., super classes to the modular components. These superclasses will be included in the FOM module as either complete or scaffolding definitions.
  43. federation requirements
    A statement that identifies a federation characteristic, constraint, process, or product that is unambiguous and testable and that is necessary for a federation to be acceptable for its intended use.
  44. federation scenario
    A set of initial conditions and timeline of significant events used within a federation execution to achieve federation objectives.
  45. handle
    An identifier originated/created by the runtime infrastructure (RTI) that is unique to a federation execution.
  46. High Level Architecture (HLA) time axis
    A totally ordered sequence of values in which each value typically represents an HLA instant of time in the physical system being modeled. For any two points, T1 and T2, on the time axis, if T1 < T2, T1 represents an instant of time that occurs before the instant represented by T2.
  47. inherited attribute
    A class attribute of an object class that was declared in a super class of that object class in the object class hierarchy tree defined in the federation object model (FOM).
  48. inherited parameter
    An interaction parameter that was declared in a superclass of that interaction class in the interaction class hierarchy tree defined in the federation object model (FOM).
  49. in scope
    Of or pertaining to an instance attribute of an object instance for which all of the following apply:

    a) The object instance is known to the joined federate.The instance attribute is owned by another joined federate.

    • b) The instance attribute’s corresponding class attribute is a one of the following:
    •     1) A subscribed attribute of the known class of the object instance, or
    •     2) A subscribed attribute of the known class of the object instance with regions, and the update region set of the instance attribute at the owning joined federate overlaps the subscription region set of the instance attribute’s corresponding class attribute at the known class of the instance attribute at the subscribing joined federate.

    NOTE—See 6.1 of IEEE Std 1516.1-2010.
  50. instance attribute
    A named characteristic of an object instance denoted by a pair composed of the object instance designator and the attribute designator.
  51. interaction
    An explicit action taken by a federate that may have some effect or impact on another federate within a federation execution.
  52. interaction class
    A template for a set of characteristics that is common to a group of interactions. These characteristics correspond to the parameters that individual federates may associate with interactions.
  53. interaction parameters
    The information associated with an interaction that a federate potentially affected by the interaction may receive to calculate the effects of that interaction on its current state.
  54. joined federate
    A member of a federation execution, actualized by a federate application invoking the JoinFederation Execution service as prescribed in IEEE Std 1516.1-2010. See also: federate application.
  55. known class
    a) An object instance’s registered class if the joined federate knows about the object instance as a result of having registered it, or An object instance’s discovered class if the joined federate knows about the object instance as a result of having discovered it.
  56. known object instance
    An object instance that a given joined federate has either registered or discovered and that the joined federate has not subsequently deleted (globally or locally) or been notified to remove. See also: register; discover; delete; local delete; remove.
  57. last known good logical timestamp
    The last timestamp to which a lost joined federate was successfully granted, as seen from the remaining High Level Architecture (HLA) compliant federation.
  58. local delete
    To invoke the Local Delete Object Instance service to inform the runtime infrastructure (RTI) that it is to treat the specified object instance as if the RTI had never notified the joined federate to discover the object instance (however, the object instance is not to be eliminated and may be rediscovered). See also:delete.
  59. logical time
    A federate’s current point on the High Level Architecture (HLA) time axis. Federates making use of the time management services follow restrictions on what timestamps can be sent in time stamp order(TSO) messages (relative to their logical time) to ensure that federates receiving those messages receive them in TSO.
  60. lookahead
    A nonnegative value that establishes a lower value on the timestamps that can be sent in timestamp order (TSO) messages by time-regulating joined federates. Once established, a joined federate’s lookahead value may be changed only by using the Modify Lookahead service. Each time-regulating joined federate must provide a lookahead value when becoming time-regulating.
  61. lost joined federate
    A previously joined federate that has been disconnected from the runtimeinfrastructure (RTI) as a result of a fault so that the joined federate can no longer continue in the federationexecution in a High Level Architecture (HLA) compliant manner.
  62. Management Object Model (MOM)
    A group of predefined High Level Architecture (HLA) constructs(object and interaction classes) that provide the following:

    a) Access to federation execution operating information

    b) Insight into the operations of joined federates and the runtime infrastructure (RTI)

    c) Control of the functioning of the RTI, the federation execution, and the individual joined federates
  63. Management Object Model (MOM) and Initialization Module (MIM)
    A subset of the federation object model (FOM) that contains object model template (OMT) tables that describe the High Level Architecture(HLA) MOM. The MIM also contains additional predefined HLA constructs such as object and interaction roots, data types, transportation types, and dimensions. HLA specifies a standard MIM that is incorporated into all FOM Document Data (FDD) automatically by the runtime infrastructure (RTI). The standard MIM can be replaced with a user-supplied MIM containing the standard MIM plus extensions.
  64. message
    A change of object instance attribute value(s), an interaction, or a deletion of an existing object instance, often associated with a particular point on the High Level Architecture (HLA) time axis, as denoted by the associated timestamp.
  65. null designator
    A designator reserved to indicate an empty value that is distinguishable from all other designators. A null designator is guaranteed to compare unequal to any other designator with a non empty value.
  66. object class
    A fundamental element of a conceptual representation for a federate that reflects the real world at levels of abstraction and resolution appropriate for federate interoperability. An object class is a template for a set of characteristics that is common to a group of object instances. These characteristics correspond to the class attributes that individual federates may publish and to which other federates may subscribe.
  67. object instance
    A unique instantiation of an object class that is independent of all other instances of that object class. At any point during a federation execution, the state of a High Level Architecture (HLA) object instance is defined as the collection of the values of all its instance attributes.
  68. object model
    A system specification defined primarily by class characteristics and relationships. The High Level Architecture (HLA) idea of an object model is similar in many ways, but not identical, to the common idea of an object model in object-oriented literature.
  69. object model framework
    The rules and terminology used to describe High Level Architecture (HLA) object models.
  70. order type
    A runtime infrastructure (RTI) means of ordering messages originating from multiple joined federates that are delivered to a single joined federate. Different categories of service are defined with different characteristics regarding whether and how an RTI orders messages that are to be delivered to a joined federate.
  71. out of scope
    Of or pertaining to an instance attribute of an object instance for which one or more of the following are not true:

    • a) The object instance is known to the joined federate.
    • b) The instance attribute is owned by another joined federate.
    • c) The instance attribute’s corresponding class attribute is one of the following:
    •      1) A subscribed attribute of the known class of the object instance, or
    •      2) A subscribed attribute of the known class of the object instance with regions, and the update region set of the instance attribute at the owning joined federate overlaps the subscription region set of the instance attribute’s corresponding class attribute at the known class of the instance attribute at the subscribing joined federate.NOTE—See 6.1 of IEEE Std 1516.1-2010.
  72. overlap
    a) Pertaining to region sets: given two region sets, to have a region in each set such that the two regions overlap.

    Pertaining to regions: given two regions, to have at least one dimension in common if and only if, for each dimension the regions have in common, their respective ranges in the common dimension overlap. If two regions do not have any dimensions in common, the regions do not overlap.

    c) Pertaining to ranges: given two ranges

    • (A = [alower, aupper ) and B = [blower , bupper )), to overlap if and only if either alower = blower or
    • (alower < bupper and blower < aupper ).

    NOTE—See 9.1 of IEEE Std 1516.1-2010.
  73. owned
    Pertaining to the relationship between an instance attribute and a joined federate: when the joined federate has the unique right to update the instance attribute’s value.
  74. owned instance attribute
    An instance attribute that is explicitly modeled by the owning joined federate. A joined federate that owns an instance attribute has the unique responsibility to provide values for that instance attribute to the federation, through the runtime infrastructure (RTI), as documented in the federation object model (FOM) Document Data (FDD).
  75. pair
    A grouping of two related elements (a first component and a second component), the combination of which is treated as an entity. An example of a pair would be an instance attribute grouped with its current value.
  76. parameter
    A named characteristic of an interaction.
  77. passel
    A group of attribute handle/value pairs from an Update Attribute Values service invocation that are delivered together via a Reflect Attribute Values † service invocation. All pairs within the passel have the same user-supplied tag, sent message order type, transportation type, receive message order type, timestamp(if present), and set of sent region designators (if present). A passel is a message.
  78. passive subscription
    A request to the runtime infrastructure (RTI) for the kinds of data (object classes and attributes as well as interactions) that the joined federate is currently interested in receiving. However, unlike an active subscription, this information is not used by the RTI to arrange for data to be delivered, nor is it used to tell publishing joined federates that another joined federate is subscribing to that data (by way of Start/Stop Registration, Turn On/Off Updates, or Turn On/Off Interactions service invocations). This form of subscription is provided to support certain types of logger joined federates.
  79. promoted
    Pertaining to an object instance, as known by a particular joined federate: having a discovered class that is a superclass of its registered class.

    NOTE—See 5.1.3 of IEEE Std 1516.1-2010.
  80. publish
    To announce to a federation the information a federate may provide to the federation.
  81. published
    a) Pertaining to an object class from the perspective of a given joined federate: having at least one available attribute of the object class that was an argument, along with the object class, to a Publish Object Class Attributes service invocation that was not subsequently unpublished via the Unpublish Object Class Attributes service.

    NOTE—See 5.1.2 of IEEE Std 1516.1-2010.

    b)Pertaining to an interaction class from the perspective of a given joined federate: being an argument to a Publish Interaction Class service invocation that was not subsequently followed by an Unpublish Interaction Class service invocation for that interaction class.

    NOTE—See 5.1.3 of IEEE Std 1516.1-2010.
  82. published attributes of an object class
    The class attributes that have been arguments to Publish Object Class Attributes service invocations by a given joined federate for that object class that have not subsequently been unpublished (either individually or by unpublishing the whole object class), and possibly the HLAprivilegeToDeleteObject attribute for that object class.
  83. range
    A subset of a dimension, defined by an ordered pair of values, the first being the range lower bound and the second being the range upper bound. This pair of values defines a semi-open interval [range lower bound, range upper bound) (i.e., the range lower bound is the smallest member of the interval, and the range upper bound is just greater than any member of the interval).
  84. range lower bound
    The first component of the ordered pair of values that is part of a range.

    NOTE—See 9.1.1 of IEEE Std 1516.1-2010.
  85. range upper bound
    The second component of the ordered pair of values that is part of a range.

    NOTE—See 9.1.1 of IEEE Std 1516.1-2010.
  86. received class
    The class that was an interaction’s candidate received class at the joined federate when that interaction was received at that joined federate via an invocation of the Receive Interaction † service.

    NOTE—See 5.1.3 of IEEE Std 1516.1-2010.
  87. received parameters
    The set of parameters received when the Receive Interaction † service is invoked.These parameters consist of the subset of the sent parameters of an interaction that are available parameters of the interaction’s received class.

    NOTE—See 5.1.3 of IEEE Std 1516.1-2010.
  88. receive order (RO)
    A characteristic of no ordering guarantee for messages. Messages that are received as RO messages will be received in an arbitrary order by the respective joined federate. A timestamp value will be provided with the message if one was specified when the message was sent, but that timestamp has no bearing on message receipt order.
  89. reflect
    To receive new values for one or more instance attributes via invocation of the Reflect AttributeValues † service.

    NOTE—See 6.7 of IEEE Std 1516.1-2010.
  90. reflected instance attribute
    An instance attribute that is represented but not explicitly modeled in a joined federate. The reflecting joined federate accepts new values of the reflected instance attribute as they are produced by some other federation member and provided to it by the runtime infrastructure (RTI), via the Reflect Attribute Values † service.
  91. region
    A generic term that refers to either a region specification or a region realization. If not using data distribution management (DDM), region arguments may be ignored.

    NOTE—See 9.1 of IEEE Std 1516.1-2010.
  92. region realization
    A region specification (set of ranges) that is associated with an instance attribute for update, with a sent interaction, or with a class attribute or interaction class for subscription. Region realizations are created from region specifications via the Commit Region Modifications (only when modifying a region specification from which region realizations are already derived), Register ObjectInstance With Regions, Associate Regions for Updates, Subscribe Object Class Attributes With Regions,Subscribe Interaction Class With Regions, Send Interaction With Regions, or Request Attribute Value Update With Regions services.NOTE—See 9.1.1 of IEEE Std 1516.1-2010.
  93. region specification
    A set of ranges. Region specifications are created using the Create Region service, and a runtime infrastructure (RTI) is notified of changes to a region specification using the Commit Region Modifications service.

    NOTE—See 9.1.1 of IEEE Std 1516.1-2010 .
  94. region template
    A region template is an incomplete region specification where one or more dimensions have not been assigned ranges.
  95. register
    To invoke the Register Object Instance or the Register Object Instance With Regions service to create a unique object instance designator.

    NOTE—See 6.4 of IEEE Std 1516.1-2010.
  96. registered class
    The object class that was an argument to the Register Object Instance or the Register Object Instance With Regions service invocation that resulted in the creation of the object instance designator for a given object instance.
  97. regular interaction class description
    A description of an interaction class that follows IEEE Std 1516.2-2010 and contains at a minimum the interaction class name and publish/subscribe indicator.
  98. regular object class description
    A description of an object class that follows IEEE Std 1516.2-2010 and contains at a minimum the object class name and publish/subscribe indicator.
  99. remove
    To receive an invocation of the Remove Object Instance † service for a particular object instance.

    NOTE—See 6.11 of IEEE Std 1516.1-2010.
  100. repeated description
    A description of a construct (e.g., object class, interaction class, data type, dimension)in a federation object model (FOM) module with a name and additional properties that are identical to a description that is already available in the current FOM.
  101. resolution
    The smallest resolvable value separating attribute or parameter values that can be discriminated. Resolution may vary with magnitude for certain data types.
  102. retraction
    An action performed by a federate to unschedule a previously scheduled message. Message retraction may be visible to the federate to whom the scheduled message was to be delivered. Retraction is widely used in classic event-oriented discrete event simulations to model behaviors such as preemption and interrupts.
  103. runtime infrastructure (RTI)
    The software that provides common interface services during a High Level Architecture (HLA) federation execution for synchronization and data exchange.
  104. runtime infrastructure (RTI) initialization data (RID)
    RTI vendor-specific information needed to run an RTI. If required, an RID is supplied when an RTI is initialized.
  105. scaffolding interaction class description
    A description of an interaction class in a federation object model (FOM) module or simulation object model (SOM) module that follows IEEE Std 1516.2-2010. However, it will contain only the name. The name of the scaffolding interaction class description is identical to the name of a regular interaction class description provided by another FOM/SOM module. Scaffolding interaction class descriptions act as placeholders in order to represent the class hierarchy from the other FOM/SOM module(s) from which a new regular interaction class description can be specified.
  106. scaffolding object class description
    A description of an object class in a federation object model (FOM) module or simulation object model (SOM) module that follows IEEE Std 1516.2-2010. However, it will contain only the name. The name of the scaffolding object class description is identical to the name of a regular object class description provided by another FOM/SOM module. Scaffolding object class descriptions act as placeholders in order to represent the class hierarchy from the other FOM/SOM module(s) from which a new regular object class description can be specified.
  107. sent class
    The interaction class that was an argument to the Send Interaction or Send Interaction With Regions service invocation that initiated the sending of a given interaction.

    NOTE—See 5.1.3 of IEEE Std 1516.1-2010.
  108. sent interaction
    A specific interaction that is transmitted by a joined federate via the Send Interaction or Send Interaction With Regions service and received by other joined federates in the federation execution via the Receive Interaction † service.
  109. sent parameters
    The parameters that were arguments to the Send Interaction or Send Interaction With Regions service invocation for a given interaction.

    NOTE—See 5.1.3 of IEEE Std 1516.1-2010.
  110. set
    A group of elements in which each element occurs at most once (this definition corresponds to the mathematical notion of sets). An example of a set would be a group of class attributes, each of which belongs to the same object class.
  111. simulation object model (SOM)
    A specification of the types of information that an individual federate could provide to High Level Architecture (HLA) federations as well as the information that an individual federate can receive from other federates in HLA federations. The SOM is specified using one or more SOM modules. The standard format in which SOMs are expressed facilitates determination of the suitability of federates for participation in a federation.
  112. simulation object model (SOM) module
    A subset of the SOM that contains some or all object model template (OMT) tables. SOM modules and one optional Management Object Model (MOM) andI nitialization Module (MIM) are used to specify the SOM of a federate. A SOM module contains complete or scaffolding definitions for all object classes and interaction classes that are superclasses of object classes and interaction classes in the same SOM module.
  113. specified dimensions
    The dimensions that are explicitly provided when the region specification is created or modified.
  114. specified dimensions
    The dimensions that are explicitly provided when the region specification is created or modified.
  115. stop publishing
    To take action that results in a class attribute that had been a published attribute of a class no longer being a published attribute of that class.
  116. subclass
    A class that adds additional detail to (specializes) another more generic class (superclass). A subclass, by inheriting the properties from its parent class (closest superclass), also inherits the properties of all superclasses of its parent as well.
  117. subscribe
    To announce to a federation the information a federate wants from the federation.
  118. subscribed
    a) Pertaining to an object class from the perspective of a given joined federate: having subscribed attributes of that class or subscribed attributes of that class with regions, for some region. See also: subscribed attributes of an object class; subscribed attributes of an object class with regions.

    b) Pertaining to an interaction class: being a subscribed interaction class or a subscribed interaction class with regions, for some region. See also: subscribed interaction class; subscribed interaction class with regions.
  119. subscribed attributes of an object class
    The class attributes that have been arguments to Subscribe ObjectClass Attributes service invocations by a given joined federate for a given object class that have not subsequently been unsubscribed, either individually or by unsubscribing the whole object class.

    NOTE—See 5.1.2 and 5.6 of IEEE Std 1516.1-2010.
  120. subscribed attributes of an object class with regions
    The class attributes that have been arguments to Subscribe Object Class Attributes With Regions service invocations by a given joined federate for a given object class and a given region, assuming the joined federate did not subsequently invoke the Unsubscribe Object Class Attributes With Regions service for that object class and region.

    NOTE—See 9.8 of IEEE Std 1516.1-2010.
  121. subscribed interaction class
    An interaction class that, from the perspective of a given joined federate, was an argument to a Subscribe Interaction Class or Subscribe Interaction Class With Regions service invocation that was not subsequently followed by an Unsubscribe Interaction Class or Unsubscribe Interaction Class With Regions service invocation for that interaction class.

    NOTE—See 5.1.3 and 5.8 of IEEE Std 1516.1-2010.
  122. subscribed interaction class with regions
    An interaction class and a region that, from the perspective of a given joined federate, were arguments to a Subscribe Interaction Class With Regions service invocation that was not subsequently followed by an Unsubscribe Interaction Class With Regions service invocation for that interaction class and that region.

    NOTE—See 9.10 of IEEE Std 1516.1-2010.
  123. subscription region set
    A set of regions used for subscription of a class attribute or used for subscription of an interaction class. See also: used for subscription of a class attribute; used for subscription of an interaction class.
  124. superclass
    A class that generalizes a set of properties that may be inherited by more refined (i.e., detailed)versions of the class. In High Level Architecture (HLA) applications, a class may have at most one immediate superclass (i.e., can inherit only from a single class at the next higher level of the class hierarchy).
  125. synchronization point
    A logical point in the sequence of a federation execution that all joined federates forming a synchronization set for that point attempt to reach and by which, if they are successful, they synchronize their respective processing.
  126. Time Advancing state
    The interval between a joined federate’s request to advance its logical time and the corresponding grant by the runtime infrastructure (RTI). A joined federate may advance its logical time only by requesting a time advancement from the RTI via one of the following services:

    • a) Time Advance Request
    • b) Time Advance Request Available
    • c) Next Message Request
    • d) Next Message Request Available
    • e) Flush Queue Request

    The joined federate’s logical time will not actually be advanced until the RTI responds with a Time Advance Grant † service invocation at that joined federate.
  127. time-constrained federate
    A joined federate that may receive timestamp order (TSO) messages and whose time advances are constrained by other joined federates within a federation execution.

    NOTE—See 8.1 of IEEE Std 1516.1-2010.
  128. time management
    A collection of High Level Architecture (HLA) services that support controlled message ordering and delivery to the cooperating joined federates within a federation execution in a way that is consistent with federation requirements.
  129. time-regulating federate
    A joined federate that may send timestamp order (TSO) messages and that constrains the time advances of other joined federates within a federation execution.

    NOTE—See 8.1 of IEEE Std 1516.1-2010.
  130. timestamp (of message or save)
    The value of the timestamp argument provided to the relevant service invocation.
  131. timestamp order (TSO)
    An ordering of messages provided by a runtime infrastructure (RTI) for joined federates making use of time management services and messages containing timestamps. Messages having different timestamps are said to be delivered in TSO if for any two messages, M1 and M2 (timestamped withT1 and T2, respectively), that are delivered to a single joined federate where T1 < T2, then M1 is delivered before M2. Messages having the same timestamp will be delivered in an arbitrary order (i.e., no tie-breaking mechanism is provided by an RTI).
  132. transportation type
    A runtime infrastructure (RTI) provided means of transmitting messages between joined federates. Different categories of service are defined with different characteristics such as reliability of delivery and message latency.
  133. unspecified dimensions
    The available dimensions of a class attribute, instance attribute, interaction class,or sent interaction less the specified dimensions of the region specification from which the region realization is derived.

    NOTE—See 9.1.3 of IEEE Std 1516.1-2010.
  134. update
    To invoke the Update Attribute Values service for one or more instance attributes.

    NOTE—See 6.6 of IEEE Std 1516.1-2010.
  135. update rate
    The rate at which instance attribute values are provided, either by an owning joined federate to the runtime infrastructure (RTI) or by the RTI to a subscribing joined federate.
  136. update region set
    A set of regions used for sending interactions or used for updating instance attributes. See also: used for sending; used for update.
  137. used for sending
    a) Pertaining to a region and the specified interaction class designator: being an argument in the SendInteraction With Regions service.

    b) Pertaining to the default region: when the specified interaction class designator is an argument in the Send Interaction service.

    NOTE—See 9.1 of IEEE Std 1516.1-2010.
  138. used for subscription of a class attribute
    a) Pertaining to a region, an object class, and a class attribute: when the class attribute is a subscribed attribute of the object class with that region. See also: subscribed attributes of an object class with regions.

    NOTE—See 9.1 of IEEE Std 1516.1-2010.

    b) Pertaining to the default region: when the specified class attribute is a subscribed attribute of the specified class. See also: subscribed attributes of an object class with regions.

    NOTE—See 9.1 of IEEE Std 1516.1-2010.
  139. used for subscription of an interaction class
    a) Pertaining to a region and an interaction class: when the interaction class is a subscribed interaction class with regions. See also: subscribed interaction class.

    NOTE—See 9.1 of IEEE Std 1516.1-2010.

    b)Pertaining to the default region: when the specified interaction class is a subscribed interaction class. See also: subscribed interaction class.

    NOTE—See 9.1 of IEEE Std 1516.1-2010.
  140. used for update
    a) Pertaining to a region that, along with the specified object instance and attribute designators, has been used as an argument in either the Register Object Instance With Regions service or the Associate Regions For Updates service: when the region has not subsequently been used along with the specified object instance designator as an argument in the Unassociate Regions For Updates service, nor has the joined federate subsequently lost ownership of the specified instance attribute(s).

    NOTE—See 9.1 of IEEE Std 1516.1-2010.

    b) Pertaining to the default region: when the specified instance attribute(s) is not currently used for update with any other region.

    NOTE—See 9.1 of IEEE Std 1516.1-2010.
  141. valid federate designator
    A federate designator which, during the federation execution, was returned by the Join Federation Execution service to some joined federate. The federate does not have to remain a joined federate for its federate designator to remain a valid federate designator.
  142. wall-clock time
    Time as determined by a chronometer such as a wristwatch or wall clock.
  143. ADT
    abstract datatype
  144. API
    application programmer’s interface
  145. BNF
    Backus Naur Form
  146. BOM
    base object model
  147. DDM
    data distribution management
  148. DIF
    data interchange format
  149. DM
    declaration management
  150. DTD
    document type declaration
  151. FDD
    FOM Document Data
  152. FEDEP
    Federation Development and Execution Process
  153. FOM
    federation object model
  154. GALT
    Greatest Available Logical Time
  155. HLA
    High Level Architecture
  156. JAR
    Java Archive
  157. LIS
    language-independent specification
  158. LITS
    Least Incoming Timestamp
  159. LRC
    Local Runtime Component
  160. MIM
    MOM and Initialization Module
  161. MOM
    Management Object Model
  162. M&S
    modeling and simulation
  163. NA
    not applicable
  164. OMT
    object model template
  165. OO
    object oriented
  166. OOAD
    object-oriented analysis and design
  167. POC
    point of contact
  168. RID
    RTI initialization data
  169. RO
    receive order
  170. RTI
    runtime infrastructure
  171. SOM
    simulation object model
  172. TRADT
    time representation abstract datatype
  173. TSO
    timestamp order
  174. WSDL
    Web Service Definition Language
  175. WSPRC
    Web Service Provider RTI Component
  176. XML
    extensible markup language

What would you like to do?

Home > Flashcards > Print Preview