OneSAF Perspectives for Enabling BOMs

1
OneSAF Perspectives for Enabling BOMs

• Stephen M. Goss
• SimVentions
• 3330 Bourbon St., Ste 129
• Fredericksburg, VA 22408
• 540-372-7727
• sgoss_at_simventions.com

2
Purpose

• Introduction of OneSAF
• Discuss how OneSAF concepts relate to Base Object
  Model development
• Discuss how Base Object Models will potential
  help the growth of OneSAF and its concepts

3

• Disclaimer I am NOT an expert on
• OneSAF just an individual who is
• learning the latest technologies!

4
OneSAF Overview

• OneSAF a composable Computer Generated Force
  product line
• Supports
• Research, Development and Acquisition (RDA)
• Advanced Concepts and Requirements (ACR)
• Training, Exercise and Military Operations (TEMO)

5
OneSAF Overview

• Each instance of OneSAF is called a System
  Composition (e.g., Leader and Staff Training
  Test and Evaluation Support)
• Satisfies specific user needs
• Consists of one or more of 12 OneSAF Products
• Driven by OneSAF Use Cases (OUC)

6
OneSAF Use Cases

• Each Use Case describes
• Intended use
• Functionality required
• Activities to be performed during whole lifecycle
• Contains examples

7
OneSAF Products

• Provide end-user visible functionality
• Logical aggregations and integrations of one or
  more Components
• Four types
• Battlespace (e.g., Simulation Core and C4I
  Adapter)
• Tool (Event Planner and Simulation Controller
  Product
• Software Development (Maintenance Environment
  Product)
• Data (Repository Manager Product)

8
OneSAF Components

• Collection of capabilities
• Discrete Modules (executables) for software
  development, reuse or integration
• Either software or data
• Configuration managed items
• Similar or related groups of components called a
  package

9
Component Types

• Four types
• Model (Composite Models)
• Tool
• Infrastructure
• Repository
• Model represent functionality in synthetic
  battlespace (e.g., weapon models, behavioral
  models or environment models)
• Tool user interfaces (e.g., plan view displays,
  control and data analysis tools)

10
Component Types (cont)

• Infrastructure components in the computer
  science domain to form higher components and
  functioning software products.
• Repository data elements used in support of
  models, tools or infrastructure.

11
Unit Models component of a military,
paramilitary, quasi-military or government
Entity Models Command (Physical representation
of command nodes) or simple Entity (system that
can express observable behavior)
Behavior Models Provide command and control
capabilities for Units and Entities.
Physical Models mathematical representation of
combat systems and their physical interactions.
Environment Models provide static and dynamic
runtime representations including terrain,
atmosphere, ocean, and space.
12
Learning from OneSAF

• Full life-cycle usage of components
• Fully integrated environments
• Use of meta-data, integration experience,
  conceptual model information, graphics, behavior
• Interoperability able to work with larger
  systems, other simulations or simulators
• Reliability and Availability
• Maintainability
• Extensibility and Scalability
• Portability
• Security

13

• What are some of the types of BOMs that OneSAF
  might benefit from?
• Encapsulated BOMs carry behavior and other
  relevant meta-data
• Design-time BOMs XML context for platform
  independence
• Runtime BOMs Compiled (DLL, .SO)
• Trigger BOMs