bom template specification images siso-std-003.1-draft-v0.13
TRANSCRIPT
BOM Palette - x
Choose what fits conceptual model
A
B
C
XCompositions identified as BOM Assemblies A,B,C and X
Spec – Figure 1-1
structured, encoded data that describe characteristics of information-bearing entities to aid in the identification, discovery, assessment, and management of the described entities
BOM Elements
required simulated capabilities defined in the context of an interface description.
represents the information necessary for execution and exchange.
described in terms of structural and/or object-based classes defining capabilities of a simulation application.
use of the HLA OMT provides a familiar construct for the simulation software designer, but does not restrict the use of a BOM to HLA specific implementations.
Model Identification (Metadata)
Notes
Lexicon (definitions)
Object Model Definition
HLA Object Classes
HLA Object Class Attributes
HLA Object Classes
HLA Interaction Classes
HLA Interaction Class Parameters
HLA Interaction Classes
HLA Data Types
Conceptual Model Definition
Pattern of Interplay
State Machine
Entity Type
Event Type
Model Mapping
Entity Type Mapping
Event Type Mapping
static descriptions of items resident in the real world described in terms of conceptual entities and conceptual events.
information on how such items relate or interact with each other in the real world in terms of patterns of interplay and state machines.
BOM template allows BOMs to be captured in a reusable way
maps the relationship between the elements in the Conceptual Model space and the interface description elements described in the HLA Object Model Space
BOM Elements• a component-based standard describing reusable piece
parts of a simulation or simulation space.
• BOMs can be used to document one or more of the following piece part elements:
– Conceptual Model Definition• Patterns of interplay• State machines• Entities• Events
– Object Model Definition (“Interface”)• Object classes / attributes• Interaction classes / parameters
– Mapping between Conceptual Model and Object Model
• Used as a building block in the development and extension of a simulation and/or a federation of simulations.
• Provides developers and users a modular approach – for defining and adding new capabilities to a federate or federation, – for quickly composing object models such as HLA FOMs and SOMs through BOM
Assemblies.
Model Identification (Metadata)
Notes
Lexicon (definitions)
Object Model Definition
HLA Object Classes
HLA Object Class Attributes
HLA Object Classes
HLA Interaction Classes
HLA Interaction Class Parameters
HLA Interaction Classes
HLA Data Types
Conceptual Model Definition
Pattern of Interplay
State Machine
Entity Type
Event Type
Model Mapping
Entity Type Mapping
Event Type Mapping
Model Identification (Metadata)
Notes
Lexicon (definitions)
Object Model Definition
HLA Object Classes
HLA Object Class Attributes
HLA Object Classes
HLA Interaction Classes
HLA Interaction Class Parameters
HLA Interaction Classes
HLA Data Types
Object Model Definition
HLA Object Classes
HLA Object Class Attributes
HLA Object Classes
HLA Interaction Classes
HLA Interaction Class Parameters
HLA Interaction Classes
HLA Data Types
Conceptual Model Definition
Pattern of Interplay
State Machine
Entity Type
Event Type
Conceptual Model Definition
Pattern of Interplay
State Machine
Entity Type
Event Type
Model Mapping
Entity Type Mapping
Event Type Mapping
Model Mapping
Entity Type Mapping
Event Type Mapping
Pattern of Interplay
+Name
Event<<Event Type>>
Pattern Action
+Name+Sequence
1..*
BOM<<BOM Type>>
Receiver<<Entity Type>> 1..*
Sender<<Entity Type>>
State Machine
+Name
State
+Name
Conceptual Entity<<Entity Type>>
Exit Condition
Next State<<State>>
Exit Action<<Pattern Action>>
Event Type
+Name
Target Characteristic<<Entity Characteristic>>
+Name
Source Characteristic<<Entity Characteristic>>
+Name
Content Characteristic<<Entity Characteristic>>
+Name
Target Condition
0..10..*0..*1
event type
sourcecharacteristic
targetcharacteristic
contentcharacteristic
action type
<<entity type>> sender
<<entity type>> receiverevent type
sourcecharacteristic
contentcharacteristic
triggercondition
<<event type>> event or
message
trigger
pattern action,variation, orexception
conceptual entity
entity type
characteristic
message
event type
sourcecharacteristic
targetcharacteristic
contentcharacteristic
event type
sourcecharacteristic
contentcharacteristic
triggercondition
trigger
pattern action,variation, or
exception
action type
<<entity type>> sender
<<entity type>> receiver
<<event type>> event
entity type
characteristic
event type
sourcecharacteristic
targetcharacteristic
contentcharacteristic
event type
sourcecharacteristic
contentcharacteristic
triggercondition
trigger
pattern action,variation, or
exception
action type
<<entity type>> sender
<<entity type>> receiver
<<event type>> event
An action can be associated to an event
An action can be potentially supported completely by another pattern of interplay
{OR}
1
*
1
*
Pattern
Action
Sender
Receiver
BOM
Event
Exception
Variation
0..1
*
1
*
0..1
*
old
State Machine
States
1
*
Exit Condition
1
*
NextState
1 *
ExitAction
«entity type»Conceptual Entity Entity Type
Entity Characteristics
1
*
old
Entity Type
Characteristics
1
*
{OR}
1
*
1
*
Pattern
Action
«entity type»Sender
«entity type»Receiver
BOM
«event type»Event
Exception
Variation
0..1
*
1
*
0..1
*
Pattern Description
Event Type DescriptionEntity Type Description
State Machine
BOM Element Relationship (Conceptual Model View)old
HomeConstruction
ElectronicsEngineering
Plumbing and Electrical Supplies, Lumber, Hardware
Integrated Circuits,Capacitors, Resistors
SoftwareDevelopment
VBX, ActiveX, VCL, and
JavaBean Controls
HomeConstruction
ElectronicsEngineering
Plumbing and Electrical Supplies, Lumber, Hardware
Integrated Circuits,Capacitors, Resistors
SoftwareDevelopment
VBX, ActiveX, VCL, and
JavaBean Controls
Figure 6-1 - Examples of Component Reuse
BOMs
MetadataRich
HLAObjectModels(FOMs)
Federate View
Communication View
Classa
Classb
Classx
Classa
Classc
Classx
Classb
Classc
Classx
Classa
Classb
Classd
BOM Assembly (Composite)
MoreOMT
Implementation View (within each Federate)
BOM a - State MachineBOM b - State MachineBOM c – State MachineBOM d - State Machine BOM x - State Machine
BOM Component Imp BOM Component Imp BOM Component Imp
ReuseLibrary
*Required
Optional
*
LEGEND
Potentially more thanone occurrence
SOM
Conceptual / Interface View
Federate Code / Libraries
Conceptual / Interface View
FOM (OMT 1.3 - or - 1516 - or - 1516 Evolve)
RTI
BOM 1 - Pattern BOM 2 - Pattern BOM 3 - Pattern BOM n - Pattern
Federation View
BOMs
MetadataRich
HLAObjectModels(FOMs)
Federate View
Entitya
Entityb
Entityx
Entitya
Entityc
Entityx
Entityb
Entityc
Entityx
Entitya
Entityb
Entityd
BOM Assembly (Composite)
MoreHLA OMTelements
Implementation View (within each Federate)
BOM a - State MachineBOM b - State MachineBOM c – State MachineBOM d - State Machine BOM x - State Machine
BOM Component Imp BOM Component Imp BOM Component Imp
ReuseLibrary
*Required
Optional
*
LEGEND
Potentially more thanone occurrence
SOM
Conceptual Model View
Federate Code / Libraries
Conceptual Model View
FOM (OMT 1.3 - or - 1516 - or - 1516 Evolve)
BOM 1 - Pattern BOM 2 - Pattern BOM 3 - Pattern BOM n - Pattern
Federation View
BOMs
MetadataRich
HLAObjectModels(FOMs)
Federate View
Entitya
Entityb
Entityx
Entitya
Entityc
Entityx
Entityb
Entityc
Entityx
Entitya
Entityb
Entityd
BOM Assembly (Composite)
BOM a - State MachineBOM b - State MachineBOM c – State MachineBOM d - State Machine BOM x - State Machine
ReuseLibrary
*
Required
Optional
*
LEGEND
Potentially more thanone occurrence
Conceptual Model View
Conceptual Model View
BOM 1 - Pattern BOM 2 - Pattern BOM 3 - Pattern BOM n - Pattern
Federation View
Object Model View (class structures within multiple BOMs or a single SOM)
Object Class y
• Attribute 4• Attirbute 5• Attribute 6
Object Class y
• Attribute 1• Attirbute 2• Attribute 3
Object Class z
• Attribute 7• Attirbute 8• Attribute 9
Interaction Class r
• Attribute 1• Attirbute 2• Attribute 3
Interaction Class s
• Attribute 4• Attirbute 5• Attribute 6
Object Model View (class structures within multiple BOMs or a single SOM)
Object Class y
• Attribute 4• Attirbute 5• Attribute 6
Object Class y
• Attribute 1• Attirbute 2• Attribute 3
Object Class z
• Attribute 7• Attirbute 8• Attribute 9
Interaction Class Q
• Attribute 1• Attirbute 2• Attribute 3
Interaction Class R
• Attribute 4• Attirbute 5• Attribute 6
Implementation View (within each Federate)BOM Component Imp BOM Component Imp BOM Component Imp Federate Code / Libraries
BOMs
MetadataRich
HLAObjectModels(FOMs)
Federate View
Entitya
Entityb
Entityx
Entitya
Entityc
Entityx
Entityb
Entityc
Entityx
Entitya
Entityb
Entityd
BOM Assembly (Composite)
BOM a - State MachineBOM b - State MachineBOM c – State MachineBOM d - State Machine BOM x - State Machine
ReuseLibrary
*
Required
Optional
*
LEGEND
Potentially more thanone occurrence
Conceptual Model View
Conceptual Model View
BOM 1 - Pattern BOM 2 - Pattern BOM 3 - Pattern BOM n - Pattern
Federation View
Object Model View (class structures defined within multiple BOMs or a single SOM)
Object Class y
• Attribute 4• Attirbute 5• Attribute 6
Object Class y
• Attribute 1• Attirbute 2• Attribute 3
Object Class z
• Attribute 7• Attirbute 8• Attribute 9
Interaction Class Q
• Attribute 1• Attirbute 2• Attribute 3
Interaction Class R
• Attribute 4• Attirbute 5• Attribute 6
Implementation View (within each Federate)BOM Component Imp BOM Component Imp BOM Component Imp Federate Code / Libraries
Object Model View (class structures defined within multiple BOMs or a single SOM)
Object Class y
• Attribute 4• Attirbute 5• Attribute 6
Object Class y
• Attribute 1• Attirbute 2• Attribute 3
Object Class z
• Attribute 7• Attirbute 8• Attribute 9
Interaction Class Q
• Attribute 1• Attirbute 2• Attribute 3
Interaction Class R
• Attribute 4• Attirbute 5• Attribute 6
BOMs
MetadataRich
HLAObjectModels(FOMs)
Federate View
Entitya
Entityb
Entityx
Entitya
Entityc
Entityx
Entityb
Entityc
Entityx
Entitya
Entityb
Entityd
State Machine a State Machine b State Machine c State Machine d State Machine x
ReuseLibrary
*
Required
Optional
*
LEGEND
Potentially more thanone occurrence
Conceptual Model View
Conceptual Model View
Pattern of Interplay 1 Pattern of Interplay 2 Pattern of Interplay 3 Pattern of Interplay 4
Federation View
Object Model View (class structures supported with each Federate to represent conceptual elements)
Object Class y
• Attribute 4• Attirbute 5• Attribute 6
Object Class y
• Attribute 1• Attirbute 2• Attribute 3
Object Class z
• Attribute 7• Attirbute 8• Attribute 9
Interaction Class Q
• Attribute 1• Attirbute 2• Attribute 3
Interaction Class R
• Attribute 4• Attirbute 5• Attribute 6
Implementation View (capability within each Federate)
BOM Component Imp BOM Component Imp BOM Component Imp Federate Code / Libraries
Object Model View (class structures describing context for information exchange among Federation)
Object Class y
• Attribute 4• Attirbute 5• Attribute 6
Object Class y
• Attribute 1• Attirbute 2• Attribute 3
Object Class z
• Attribute 7• Attirbute 8• Attribute 9
Interaction Class Q
• Attribute 1• Attirbute 2• Attribute 3
Interaction Class R
• Attribute 4• Attirbute 5• Attribute 6
Entity a1 Entity a2 Entity b1 Entity b2 Entity c1 Entity c2 Entity d Entity x1 Entityx2
Event G Event HEvent E Event FEvent C Event DEvent A Event B
Implementation View (within each Federate)BOM Component Imp BOM Component Imp BOM Component Imp Federate Code / Libraries
Object Model View (class structures within a single SOM or multiple BOMs)
BOMs
MetadataRich
HLAObjectModels(FOMs)
Federate View
Entitya
Entityb
Entityx
Entitya
Entityc
Entityx
Entityb
Entityc
Entityx
Entitya
Entityb
Entityd
BOM Assembly (Composite)
MoreHLA OMTelements
Implementation View (within each Federate)
BOM a - State MachineBOM b - State MachineBOM c – State MachineBOM d - State Machine BOM x - State Machine
BOM Component Imp BOM Component Imp BOM Component Imp
ReuseLibrary
*
Required
Optional
*
LEGEND
Potentially more thanone occurrence
SOM
Conceptual Model View
Federate Code / Libraries
Conceptual Model View
FOM (OMT 1.3 - or - 1516 - or - 1516 Evolve)
BOM 1 - Pattern BOM 2 - Pattern BOM 3 - Pattern BOM n - Pattern
Federation View
Object Model ViewBOM a – Object Class / AttributeBOM a – Object Class / AttributeBOM a – Object Class / AttributeBOM a – Object Class / Attribute
Fe
dera
te(S
OM
)
BOMs(Coupling)
BOMAssembly
CompositeInterface
Composition
Sim / System A
Representation Fe
dera
tion
(FO
M)Federate B
Federate X
Federate A
Ag
gre
gat
ion
Model#1
Model#2
Model#3
Model#n
- or -
- or -
These BOMs represent the relationship of activities among conceptual entities (FOM level),
BOM 1
BOM 3
BOM n
BOM 2
Figure 6-4 – Application of BOMs for Providing Various Federation Level Support
Fe
dera
te(S
OM
)
BOMs(Coupling)
BOMAssembly
BOM 1
BOM 3
BOM n
CompositeInterface
Composition
Sim / System A
Representation Fe
dera
tion
(FO
M)Federate B
Federate X
Federate A
Ag
gre
gat
ion
Model#1
Model#2
Model#3
Model#n
- or -
- or -
These BOMs represent the relationship of activities among conceptual entities (FOM level),
Weapons
Effect
Radio
Comm
s
Theater W
arfare
Representa
tion
BOM 2
Repair
Resupply
Detect /
Jam
Federate - Conceptual /
interface view
BOM 1
Sim / System
FunctionalExposure
State MachineEntity Types
HLA Object Classes
BCI = BOM Component Implementation
CODE
BCI
BCI
BCI
BCI
Federate – Implementation
View
BOM 2State Machines,
Entities,Events
----Object Classes,
Attributes,Interaction Classes,
Parameters
BOM nState Machines,
Entities,Events
----Object Classes,
Attributes,Interaction Classes,
Parameters
FunctionalCapability
Run-timeExecution
Figure 6-5 - Application of BOMs for Providing Federate Level Support
BOM 1
BOM Element Relationship (Conceptual Model View)
Pattern
ActionEvent
n
1
BOM1
Sender Receiver
n n
An action can be associated to an event
State Machine
States
n
ExitCondition
PatternAction
n
NextState
State MachinePattern DescriptionAn action can be potentially supported completely by another pattern of interplay
Entity
Characteristics
Entity Type Description
n
Event Type Description
Event
Source
Target
Trigger
Message Content
Entityn
Characteristics
n
Role
Corrective Actions / Iterative Development
65431
Perform Conceptual
Analysis
2
Analyze Data and Evaluate Results
7
Define Federation Objectives
Design Federation
Develop Federation
Plan,Integrate, and Test
Federation
Execute Federation
and Prepare Outputs
Figure 7-1 – FEDEP Seven-Step Process
BOM Element ->Model
Identification Conceptual
ModelModel
MappingObject Model
Definition
Individual BOM(Conceptual Model Def)behavior representation(pattern, state machine, events)
Required Required Optional Optional
Individual BOM(Object Model Definition) object repesentation (object classes, interaction classes)
Required Optional Optional Required
BOM Assembly(representing composite of other BOMs)
RequiredRequired
(Pattern of Interplay)
Optional Optional
SOM
FOM
BOMs
BOM Assembly
n
Aggregate Model
Xformation
Figure 8‑1 - BOM Elements for Representing a Pattern of Interplay
Model Identification(Key meta-data)
Type
Name
Version
Mod Date
Description
Use Limit
Use History*
Keyword*Sec Class POC*
Rel Rstctn* References
Purpose Other
App Dom Glyph
ConceptualModel
Required
Optional
*Supportsmultiple occurrences
Figure 8‑3 –BOM – Model Identification Table
Model Identification(Key metadata)
Type
Name
Version
Mod Date
Description
Use Limit
Use History*
Keyword*Sec Class POC*
Rel Rstctn* References
Purpose Other
App Dom Glyph
Required
Optional
*Supportsmultiple occurrences
Figure 8‑3 –BOM – Model Identification Table
Figure 8‑4 - BOM Template – Pattern Description
Pattern of Interplay
Actions (Activities)
Name
Variations*
Exceptions*
Event
BOM
Sequence *
Name
Source*
Target*
Pattern
ActionEvent
Trigger Message
n
1 BOM(Another Pattern)
1
Source Target
n n
An action can be associated to an event An action can be potentially
supported completely by another pattern of interplay
Figure 8‑5 - BOM Template – Pattern Step Relationship
Triggers
• The conceptual entity identified as the sender of the action within the pattern of interplay publishes information as an event for other conceptual entities to react to, but does not know the target conceptual entities.
• In the HLA, the event is generated using either an object class attribute update or a sent interaction.
• A response (reaction) may occur by one or more subscribing conceptual entities that have interest in such observable events.
• In the HLA, the occurrence of the undirected event is of interest to a federate, which may react or respond to such an action.
Publish Event Subscribe Event
Undirected Events
Source Björn Löfstrand – Pitch ABFigure 8‑7 – Event - Trigger
Figure 8-10
Messages
• The conceptual entity identified as the sender of the action within the pattern of interplay directs (sends) a message event to the conceptual entity(s) identified as the receiver.
• In the HLA, the message occurs between federates using either an object class attribute update or a sent interaction.
• The conceptual entity(s) identified as the receiver reacts to the information contained in the directed message.
• In the HLA, the federate responsible for modeling the receiving conceptual entity(s) may respond to the specific sent interaction or object attribute update.
Send Event Receive Event and react to its contents
Directed events
Source Björn Löfstrand – Pitch AB
Figure 8‑6 – Event - Message
Figure 8-11
Define Federation Objectives
1.1 - Identify User/Sponsor Needs 1.2 - Develop Objectives
Overall Plans
Existing Domain
Descriptions
Info On Available
Resources
Federation Objectives Statement
(1.2)
Initial Planning
Documents (1.2)
Perform Conceptual Analysis 2.1 – Develop Scenario 2.2 – Develop Conceptual Model 2.3 – Develop Federation Req
Existing Conceptual
Models
Federation Objectives Statement
(1.2)
Existing Scenarios
Authoritative Domain Information
Federation Conceptual Model (2.2)
Federation Scenario(s) (2.1)
Federation Requirements (2.3)
Federation Test Criteria
Figure 8-2 - FEDEP Steps 1 & 2
Define Federation Objectives
1.1 - Identify User/Sponsor Needs 1.2 - Develop Objectives
Overall Plans
Existing Domain
Descriptions
Info On Available
Resources
Federation Objectives Statement
(1.2)
Initial Planning
Documents (1.2)
Figure 9‑1 - FEDEP Step 1
Perform Conceptual Analysis 2.1 – Develop Scenario 2.2 – Develop Conceptual Model 2.3 – Develop Federation Req
Existing Conceptual
Models
Federation Objectives Statement
(1.2)
Existing Scenarios
Authoritative Domain Information
Federation Conceptual Model (2.2)
Federation Scenario(s) (2.1)
Federation Requirements (2.3)
Federation Test Criteria
Figure 9‑2 - FEDEP Step 2
Design Federation 3.1 – Select Federates 3.2 – Prepare Federation Design 3.3 – Prepare Plan
Federation Scenario(s)
(2.1)
Initial Planning Documents (1.2)
Existing Conceptual
Models Federation Objectives
Statement (1.2)
Federation Requirements
(2.3)
Federation Conceptual Model (2.2)
Federate / Federation Design (3.2)
Federation Development & Execution Plan (3.3)
Selected Federates (3.1)
Figure 9‑5 - FEDEP Step 3 Figure 9‑6 - FEDEP Step 4
Develop Federation
4.1 – Develop FOM (Mega -BOM)4.2 – Establish Federation
Agreements4.3 – Implement Federate Designs4.4 – Implement Federation
Infrastructure
FederationScenario(s)
(2.1)
FederationDevelopment &Execution Plan
(3.3)
Federate &Federation
Designs (3.2)
(4.2)
FederationRequirements (2.3)
FederationConceptualModel (2.2)
Multiple Items:•
(4.1)• FED/FDD (4.1)• Scenario Instances
(4.2)• Modified/New
Federates (4.3)• Federation
Infrastructure (4.4)• RTI Init Data (4.4)• Supporting
Databases (4.3)
Develop Federation
4.1 – Develop FOM (Mega -BOM)4.2 – Establish Federation
Agreements4.3 – Implement Federate Designs4.4 – Implement Federation
Infrastructure
(2.1)
FederationAgreements
Multiple Items:• FOM / BOM Assembly
(4.1)••
•
•
••
Design Federation 3.1 – Select Federates 3.2 – Prepare Federation Design 3.3 – Prepare Plan
Federation Scenario(s)
(2.1)
Initial Planning Documents (1.2)
Existing Conceptual
Models Federation Objectives
Statement (1.2)
Federation Requirements
(2.3)
Federation Conceptual Model (2.2)
Federate / Federation Design (3.2)
Federation Development & Execution Plan (3.3)
Selected Federates (3.1)
Figure 9‑5 - FEDEP Step 3 Figure 9‑6 - FEDEP Step 4
Develop Federation
4.1 – Develop FOM (Mega-BOM)4.2 – Establish Federation
Agreements4.3 – Implement Federate Designs4.4 – Implement Federation
Infrastructure
FederationScenario(s)
(2.1)
FederationDevelopment &Execution Plan
(3.3)
Federate &Federation
Designs (3.2)
FederationAgreements
FederationRequirements (2.3)
FederationConceptualModel (2.2)
Multiple Items:• FOM / BOM Assembly
(4.1)• FED/FDD (4.1)• Scenario Instances
(4.2)• Modified/New
Federates (4.3)• Federation
Infrastructure (4.4)• RTI Init Data (4.4)• Supporting
Databases (4.3)
Develop Federation
4.1 – Develop FOM (Mega-BOM)4.2 – Establish Federation
Agreements4.3 – Implement Federate Designs4.4 – Implement Federation
Infrastructure
FederationScenario(s)
(2.1)
FederationDevelopment &Execution Plan
(3.3)
Federate &Federation
Designs (3.2)
FederationAgreements
FederationRequirements (2.3)
FederationConceptualModel (2.2)
Multiple Items:• FOM / BOM Assembly
(4.1)• FED/FDD (4.1)• Scenario Instances
(4.2)• Modified/New
Federates (4.3)• Federation
Infrastructure (4.4)• RTI Init Data (4.4)• Supporting
Databases (4.3)
Plan, Integrate, &Test Federation
5.1 – Plan Execution5.2 – Integrate Federation5.3 – Test Federation
FederationDevelopment &
Execution Plan (3.3)Selected
Federates (3.1)
FederationAgreements (4.2)
TestedFederation (5.3)
ExecutionEnvironment
Description (5.1)
Multiple Items:• FOM / Mega-BOM
(4.1)• FED/FDD (4.1)• Scenario Instances
(4.2)• Modified/New
Federates (4.3)• Federation
Infrastructure (4.4)• RTI Init Data (4.4)• Supporting
Databases (4.3)
Plan, Integrate, &Test Federation
5.1 – Plan Execution5.2 – Integrate Federation5.3 – Test Federation
FederationDevelopment &
Execution Plan (3.3)Selected
Federates (3.1)
FederationAgreements (4.2)
TestedFederation (5.3)
ExecutionEnvironment
Description (5.1)
Multiple Items:• FOM / Mega-BOM
(4.1)• FED/FDD (4.1)• Scenario Instances
(4.2)• Modified/New
Federates (4.3)• Federation
Infrastructure (4.4)• RTI Init Data (4.4)• Supporting
Databases (4.3)
Figure 9‑10 - FEDEP Step 5
Figure 9‑4 - Conceptual Model Driven Development
65431
Perform Conceptual
Analysis
2
Analyze Data and Evaluate Results
7
Define Federation Objectives
Design Federation
Develop Federation
Plan,Integrate, and Test
Federation
Execute Federation
and Prepare Outputs
Corrective Actions / Iterative Development
F E D E PF E D E PModelModel • Identifies
purpose• Used to
locate BOM candidate
• Used to helpvalidate semantic composabilty
• Verify results
•Verify results
MegaMega--BOMBOM
65431
Perform Conceptual
Analysis
2
Analyze Data and Evaluate Results
7
Define Federation Objectives
Design Federation
Develop Federation
Plan,Integrate, and Test
Federation
Execute Federation
and Prepare Outputs
Corrective Actions / Iterative Development
F E D E PF E D E PConceptualConceptualModelModel • Identifies
• Used to locate BOM candidate
• Used to help
composabilty•
•
BOMBOMAssemblyAssembly
Find candidate BOMs • Use purpose, keywords, and conceptual
model as searching criteria• Match metadata with available BOMs in
repository
Find candidate BOMs • Use purpose, keywords, and conceptual
model as searching criteria• Match metadata with available BOMs in
repository
FEDEPSteps2 – 4
BOM candidatefound
BOM candidatefound
Create BOM piece parts• Define patterns of interplay, state machines, entities, &
events such as triggers & messages (Conceptual Model)• Define class structures (Object Model Definition)• Define model mappings• Use BOM DIF (based on an extension of HLA OMT)
Create BOM piece parts• Define patterns of interplay, state machines, entities, &
events such as triggers & messages (Conceptual Model)• Define class structures (Object Model Definition)• Define model mappings• Use BOM DIF (based on an extension of HLA OMT)
Integrate BOM within federate • Use BOM Object Model Definition piece parts• Ensure federate supports conceptual behavior of BOM• Develop or use existing BOM Component Implementation
(BCI) – if needed
Integrate BOM within federate • Use BOM Object Model Definition piece parts• Ensure federate supports conceptual behavior of BOM• Develop or use existing BOM Component Implementation
(BCI) – if needed
BOM not found
BOM found
Identify purpose / objective / intent
• Focus on capturing conceptual model• Identify “pattern of simulation interplay”• E.g. Model capabilities of a JCAD Sensor
Identify purpose / objective / intent
• Focus on capturing conceptual model• Identify “pattern of simulation interplay”• E.g. Model capabilities of a JCAD Sensor
Search library
results
Insert BOM into libraryInsert BOM into library
Insert BOMs / BOM Assembly into libraryInsert BOMs / BOM Assembly into library
Create BOM Assembly • Composition of BOMs that support functional
inputs / anticipated outputs• Used to represent system interface (much like
SOM) or a federation (much like FOM)
Create BOM Assembly • Composition of BOMs that support functional
inputs / anticipated outputs• Used to represent system interface (much like
SOM) or a federation (much like FOM)
Insert FOM / SOM into libraryInsert FOM / SOM into library
BOM DevelopmentLibrary
BOM DevelopmentLibrary
Federation IntegrationFederation Integration
results
Fetch model
Generate FOM / SOM from BOM Assembly
Generate FOM / SOM from BOM Assembly
FOM/SOM/BOMReuse Library
FOM/SOM/BOMReuse Library
Con
cep
tual A
nalysis
Desig
nD
evelo
pm
en
t
Conceptual Model Object Model
FEDEPSteps 2 – 4
Find candidate BOM • Use Conceptual Model metadata input for
searching• Match metadata with available BOMs in
repository
BOM CandidateFound
Create BOM• Identify functional inputs / anticipated outputs• Identify potential Events such as Triggers and Messages• Use BOM DIF (based on an extension of HLA OMT) • Note: represents “interface” not an “implementation”
Integrate BOM within federate • XML Parsable BOM Interface • BOM Component Implementation (BCI) – if needed
BOM not found
BOM found
BOM Assembly
Identify purpose / objective / intent
• Focus on capturing Conceptual Model• Identify “pattern of simulation interplay”• E.g. Model capabilities of a JCAD Sensor
Conceptual Model
BOM ReuseLibrary
Search library
results
Insert BOM into library
Insert BOM Assembly into library
Create BOM Assembly • Composition of BOMs based on their
interface• Used to represent system interface (much
like SOM) or a federation (much like FOM)
Generate FOM / SOM from BOM Assembly
Object Model
old
Find candidate BOM • Use Conceptual Model metadata input for
searching• Match metadata with available BOMs in
OMRC (future capability)
Find candidate BOM • Use Conceptual Model metadata input for
searching• Match metadata with available BOMs in
OMRC (future capability)
BOM CandidateFound
BOM CandidateFound
Create BOM Interface• Identify functional inputs / anticipated outputs• Identify potential Events such as Triggers and Messages• Use BOM DIF (based on an extension of HLA OMT) • Note: represents “interface” not an “implementation”
Create BOM Interface• Identify functional inputs / anticipated outputs• Identify potential Events such as Triggers and Messages• Use BOM DIF (based on an extension of HLA OMT) • Note: represents “interface” not an “implementation”
Integrate BOM within federate • XML Parsable BOM Interface • BOM Component Implementation (BCI) – if needed
Integrate BOM within federate • XML Parsable BOM Interface • BOM Component Implementation (BCI) – if needed
BOM not found
BOM found
FEDEPFEDEPStep 3Step 3
FEDEPFEDEPStep 4Step 4
BOM BOM AssemblyAssembly
Identify purpose / objective / intent
• Focus on capturing Conceptual Model• Identify “pattern of simulation interplay”• E.g. Model capabilities of a JCAD Sensor
Identify purpose / objective / intent
• Focus on capturing Conceptual Model• Identify “pattern of simulation interplay”• E.g. Model capabilities of a JCAD Sensor
FEDEPStep 2
FEDEPStep 1 ConceptualConceptual
ModelModel
BOM ReuseLibrary
BOM ReuseLibrary
Search library
results
Insert BOM into libraryInsert BOM into library
Insert BOM Assembly into libraryInsert BOM Assembly into library
Create BOM Assembly • Composition of BOMs based on their
interface• Used to represent system interface (much
like SOM) or a federation (much like FOM)
Create BOM Assembly • Composition of BOMs based on their
interface• Used to represent system interface (much
like SOM) or a federation (much like FOM)
Generate FOM / SOM from BOM AssemblyGenerate FOM / SOM from BOM Assembly
old
Find candidate BOM • Use Conceptual Model metadata input for
searching• Match metadata with available BOMs in
OMRC (future capability)
BOM CandidateFound
Create BOM• Identify functional inputs / anticipated outputs• Identify potential Events such as Triggers and Messages• Use BOM DIF (based on an extension of HLA OMT) • Note: represents “interface” not an “implementation”
Integrate BOM within federate • XML Parsable BOM Interface • BOM Component Implementation (BCI) – if needed
BOM not found
BOM found
BOM BOM AssemblyAssembly
Identify purpose / objective / intent
• Focus on capturing Conceptual Model• Identify “pattern of simulation interplay”• E.g. Model capabilities of a JCAD Sensor
FEDEPStep 2 – Step 5
FEDEPStep 1 ConceptualConceptual
ModelModel
BOM ReuseLibrary
Search library
results
Insert BOM into library
Insert BOM Assembly into library
Create BOM Assembly • Composition of BOMs based on their
interface• Used to represent system interface (much
like SOM) or a federation (much like FOM)
Generate FOM / SOM from BOM Assembly
old
1998 20022000 2003
ReferenceFOM
StudyGroup
BOMMethodology
Strawman
SRML
Rapidly composableand scalable
M&S
2001
BOMStudyGroup
1996
RPRFOM
20101999
HLA1516
FOM“piece parts”
(FEDEP, OMT) BOMBOMPDG PDG
2004
BOM History
SISO-STD-003.1-2003BOM Spec Vol 1Interface BOM
BOM Spec
GuidanceDoc
2006 …
• Tools• Components
• Libraries
HLA1516 Evolve
DIS HLA
1990
FEDEP1516
C M S E
Protocol Oriented
WSDL
Schemas
XSLTDTD
SOAP
Object-Based Oriented Component/Service Oriented
Figure 9‑7 - Base Object Model in FEDEP
Develop Federation
4.1 – Develop FOM (Mega-BOM)4.2 – Establish Federation
Agreements4.3 – Implement Federate Designs4.4 – Implement Federation
Infrastructure
DesignFederation
3.1 – Select Federates3.2 – Prepare Federation Design3.3 – Prepare Plan
ConceptualConceptualModelModel
Develop Federation
4.1 – Develop FOM4.2 – Establish Federation
Agreements4.3 – Implement Federate Designs4.4 – Implement Federation
Infrastructure
DesignFederation
3.1 – Select Federates3.2 – Prepare Federation Design3.3 – Prepare Plan
ConceptualConceptualModelModel
BOM Assembly
Pattern
Action
n
BOM(Another Pattern)
1
Figure 9‑9 – BOM Assembly – Pattern Action to BOM Relationship
BOMs
MetadataRich
HLAObjectModels(FOMs)
ReuseLibraries
Composition A
BOM 2
BOM 4
BOM 17
ReuseLibrary
BOM 1
BOM 2
BOM 3
Composition B
BOM 1
BOM 3
BOM 11BOM 4
BOM N
BOM 23 . . . BOM 19
Figure 10‑1- Leveraging a BOM Resource Reuse Library
User Requirements
A
B
CX
BOM Palette - x
Choose what fits conceptual model?
Simulation Components
Simulation Systems• federation
interactivities(i.e., foms)
• federate capabilities
Compositions identified as BOM Assemblies A,B,C and X
Figure 6-2 - Creating BOM Compositions
BOM Element Validity Matrix
BOM Element ->Model Identification
ModelDefinition
BehaviorDescription –Pattern
BehaviorDescription –State Machine
BehaviorDescription - Events
IndividualBOM (representing pattern, state machine, and/or object/interaction class)
Required Required Optional Optional Optional
BOM Assembly(representing composite of other BOMs)
Required Optional Required Optional Optional
Application of BOM Elements
BOM ElementFederation Level
SupportFederate Level
Support
Model Identification
Required Use Required Use
Behavior Description / Pattern
Intended Use(Required for
BOM Assembly)Optional Use
Behavior Description / Events
Intended Use Optional Use
Behavior Description / State Machine
Optional Use Intended Use
Model Definition(object class/ interaction class / attributes / parameters / datatypes)
Intended Use(Not Require for BOM Assembly)
Intended Use
RPR BOMsRPR FOM 2.0
Repair
Resupply
Entity Creation
Entity Reconst’n
Entity Removal
Action Request
Post Comment
Post Event
Behavior Rep
Object Rep EntityObjects
EnvObjects
MinefieldObjects
SignalObjects
Weapons Effect
Collision
Entity St Update
Minefield
Synthetic Env
SIMAN
Logistics
RadioComms
Includes Model Mapping
BOMsBOMsBase Object ModelsBase Object Models
Locate ComposeCreate
FederationFederationImplementations
Interfaces
Activity Relationship
Conceptual Entities
Behavioral StatesEvents
System Composability
Plug & Play Systems
Model Composability
Reusable Piece Parts
What BOMs Provide? – Model Composability
65431
Perform Conceptual
Analysis
2
Analyze Data and Evaluate Results
7
Define Federation Objectives
Design Federation
Develop Federation
Plan,Integrate, and Test
Federation
Execute Federation & Prepare Outputs
FEDEP
BOMs are designed for enabling composability, providing extensibility, facilitating interoperability, improving manageability, and encouraging understandibility.
BOM Illustration #2
Derived from RPR FOM
State Machines
Pattern of Interplay
pattern actions
Weapons Effect
states
Federation Activities Federate Capability
What is Composability?
Bar
rier
s
“The ability to rapidly select and assemble components to construct meaningful simulation systems to satisfy specific user requirements. Composability includes the framework, body of knowledge, tools, techniques, and standards necessary to enable effective integration, interoperability, and reuse.” - (DoD M&S Master Plan)
Composition A
BOM 2
BOM 4
BOM 17
ReuseLibrary
BOM 1
BOM 2
BOM 3
Composition B
BOM 1
BOM 3
BOM 11BOM 4
BOM N
BOM 23 . . . BOM 19
Composition A
BOM 2
BOM 4
BOM 17
ReuseLibrary
BOM 1
BOM 2
BOM 3
Composition B
BOM 1
BOM 3
BOM 11BOM 4
BOM N
BOM 23 . . . BOM 19
M&S COMPONENTS - Reusable building blocks which have a known set of inputs and provide expected output behavior, but the implementation details may be hidden. Such components are useful for constructing simulations and/or providing functionality for simulation systems.” – COI M&S Metadata Focus Group