Federate Compliance and Federation Verification Testing Under IEEE 1516

1
Federate Compliance and Federation Verification
Testing Under IEEE 1516
2
Introduction

• HLA 1516 Background
• The Federate Compliance Testing Process
• Differences in HLA 1.3 and HLA 1516
• Porting 1.3 federation to a 1516
• Federate Verification Tool

3
HLA 1516 Background
IEEE 1516 is an open and international standard
for both military and civilian use. It is based
on other open standards such as XML and Unicode.

• 1516 Framework and Rules
• 1516.1 Federate Interface Specification
• 1516.2 Object Model Template (OMT)
• -1516.3 Recommend practice for HLA Federation
  development and execution process

4
Federate Compliance Testing


QUESTIONS
Submit application request

Return if incomplete

Approve application and send user ID/password
Submit Conformance Notebook
Return SOM/CS results with deficiencies
Return SOM/CS success, IF test date
Submit environment data, Confirm IF test date
Return IF test results with deficiencies
Return IF test success
Submit certificate request and schedule AAR
Return certification letter and certification of
compliance
5
Changes from the 1.3 to 1516 standard
The object model now uses industry standard XML
format.
Opens more possibilities for example to process
the XML in standard tool.
The object models use Unicode character
representation instead of ASCII.
It can now be internationally applied since
virtually any language can be used.
The documentation of the object model is more
complete.
Makes less room for confusion in the project and
speeds up integration.
(Data Distribution Management) is easier and more
flexible.
You may freely decide which dimensions to use for
filtering at runtime.
6
Porting 1.3 federation to a 1516
Sushi HLA 1.3 Federation
Creating Computer Simulation Systems
Originally developed
by the MITRE Corporation
Dr. Frederick Kuhl
Dr. Richard Weatherly
Dr. Judith Dahmann
7
Porting 1.3 federation to a 1516
Sushi HLA 1516 Federation
DETAILS
pitch 1516 v 2.1 build 73 or higher RTI
RTI
FOM Document Data file Restaurant_1.xml
FDD
Federates
Manager
Production
Transport
Consumption
Viewer
8
FOM XML FILE
lt?xml version"1.0" encoding"UTF-8"?gt ltobjectMode
l DTDversion"1516.2"
name"Restaurant.xml" typeFOM"
version"1.0" date"2004/2/25"
purpose"This ports the sushi HLA 1.3 federation
into the new IEEE HLA 1516 standard. "
appDomain"HLA RTI Verification"
sponsor"DMSO" pocName"Mr. Demetrius
Campbell" pocOrg"GTRI"
pocPhone"404-385-1793" pocEmail"demetrius.ca
mpbell_at_gtri.gatech.edu" references"http//dss
web.gtri.gatech.edu" other"see the book
creating Computer Simulation by Kuhl, Weatherly,
and Dahmann"gt ltobjectsgt ltobjectClass
name"Serving" sharing"Publish" ltattribute
name"type" semantics"This the
differnt types of serving" dataType"NA"
updateType"NA"
updateCondition"NA" ownership"Divest"

9
FOM XML FILE
sharing"Publish"
transportation"HLAreliable"
dimensions"NA" order"TimeStamp"/gt lt/
objectClassgt ltobjectClass name"Restaurant"
sharing"Neither"
semantics"This is the root object class for the
sushi federation." gt ltattribute
name"position" semantics"This the position
for the serving in the federation." dataType"NA
" updateType"NA" updateCondition"NA"
ownership"NoTransfer" sharing"PublishSubsc
ribe" transportation"HLAreliable" dimensions
"NA" order"TimeStamp"/gt lt/objecClassgt lt/object
gt
10
FOM XML FILE
lttransportationsgt lttransportation
name"HLAreliable"   lttransportation
name"HLAbestEffort"  lt/transportationsgt  ltswitc
hes autoProvide"Disabled" conveyRegionDesignat
orSets"Disabled"
attributeScopeAdvisory"Disabled"
attributeRelevanceAdvisory"Disabled"
serviceReporting"Enabled" /gt ltdataTypesgt ltbasic
DataRepresentationsgt   ltbasicData
name"HLAinteger16BE" size"16" endian"Big"
encoding"16-bit two's complement signed
integer. " /gt   ltbasicData name"HLAinteger32BE
" size"32" endian"Big"
encoding"32-bit two's complement signed
integer." /gt lt/basicDataRepresentationsgt
11
Porting 1.3 federation to a 1516

Transport
Viewer
Production
Consumption

Sushi Federation
12
Federate Verification Tool
Purpose
Assisting federation developer in the Federation
Integration and Federate Compliance phase.
Verifying that a federate can generate the
objects and interactions it is responsible for
in the Federation.
Using the information in a federations FDD and
OMT files to determine correct service
invocations.
13
Federate Verification Tool
ARCHITECTURE
RTIs
Pitch 1.3 1516
DMSO 1.3 NGV 4-6
MAK 1516
future
14
Federate Verification Tool
Service View
15
Federate Verification Tool
Class View
16
Conclusion
IEEE 1516 is an open and international standard
for both military and civilian use.
Federate Compliance Testing is a four step
process where individual federates under go IF
testing.

Federation Verification Tool assists the
federation developer in the Federation
Integration and Federate Compliance phase.
17
QUESTIONS ?
Demetrius Campbell Georgia Tech Research
Institute Research Scientist I www.gtri.gatech.edu
demetrius.campbell_at_gtri.gatech.edu (404) 385
-1793