HLAE PDG Conform

1
What is Conformance?

• Specification of what it means when a piece of
  software claims to have adopted the Standard.
• vs Compatible which means the software doesnt
  disrupt the simultaneous use of Standard
  conforming software.
• vs Compliant which means the software has
  followed the direction of the Standard, according
  to its authors/vendor.
• Why?
• Adding a Conformance requirement to the Standards
  gives software producers defined criteria by
  which their compliance can be proven.

2
What is HLA Conformance?

• There are many possible conformance requirements
  that the PDG could choose to incorporate into our
  Standards.
• A) Complete Implementation of all features.
• Most work to build.
• Least differentiated.
• All vendors are selling the same thing.
• Most interoperable
• B) Implementation tailored to profiles of use.
• More diversity of RTI implementations.
• Vendors more responsive to market.
• Less interoperable

• Today HLA has (B), but everybody claims we have
  (A). We must choose!

3
Suppose we want (A)

• We write a conformance section that says
  conforming RTIs must implement every feature
  exactly according to the specs.
• Verification tests that RTIs perform in this way.
• RTIs are prohibited from having features which
  cause them to behave in a non-conforming way.
  ie.
• RID file settings to enable connectionless
  operation. (VTC/SAIC)
• Settings to disable RTI features or permit the
  user to override RTI functions (MÄK)
• Just because I cant think of a Pitch example
  doesnt mean they are immune.

4
Suppose we want (B)

• We agree on a scheme for identifying RTI subsets
  that are useful to our communities.
• We write a conformance section that states when
  RTIs are permitted to have subset
  implementations.
• We define how an RTI vendor makes claims about
  which subsets they implement.
• Verification tests that RTIs act as they claim
  they act.
• RTIs with several profiles can be tested several
  times to assure that each profile works.

5
Starting Proposal 1 of 2
6
Starting Proposal 2 of 2
7
Path Ahead

• Incorporate the Conformance section provided.
• Expect comments to the next draft on both the
  feature sets identified and the rules expressed
  in the Conformance section.

8
(No Transcript)
9
HLA Evolved PDGPosition Brief Conformance
National Security Analysis Department

• Johns Hopkins University
• Applied Physics Laboratory