OneSAF Baseline Assessment Outbrief

1

OneSAF A Product Line Approach to Simulation
Development
2001 European Simulation Interoperability
Workshop (EuroSIW) 25 June 2001
Robert L. Wittman Jr. MITRE CORPORATION 3504 Lake
Lynda Drive Orlando, FL 32817 321-235-7601 rwittm
an_at_mitre.org
Cynthia T. Harrison U.S. Army STRICOM 12350
Research Parkway Orlando, FL 32826 407-384-3845 C
indy_Harrison_at_stricom.army.mil
2
Agenda

• Introduction of OneSAF
• Teamwork Based Development Strategy
• Continuous Army Community Involvement
• Electronic Information Environment
• Operational Context
• Operational Concept Document
• Technical Foundation
• Product Line Architecture Framework
• Reuse Direction and Guidance
• International Community Collaboration
• Summary

3
What is One Semi-Automated Forces (OneSAF)?
A composable, next generation CGF that can
represent a full range of operations, systems,
and control process (TTP) from entity up to
brigade level, with variable level of fidelity
that supports all Army MS domains (ACR, RDA,
TEMO) applications.
Software only
Automated Composable Extensible Interoperable
Platform Independent
Fielded to National Guard Armories Reserve
Training Centers All Active Duty Brigades and
Battalions
Replaces legacy entity based Simulations BBS -
ModSAF - JANUS - CCTT SAF
4
OneSAF Teamwork Based Acquisition Strategy

• Continuous (Side by Side) Army Domain/User
  Involvement
• Advanced Concepts and Requirements Domain (ACR)
• Research, Development, and Acquisition Domain
  (RDA)
• Training, Exercise and Military Operations Domain
  (TEMO)
• Training and Doctrine OneSAF Program Office (TPO)
• Simulation Training and Instrumentation Command
  (STRICOM)
• OneSAF Integrated Development Environment
• Contractors Government Side-by-Side in single
  location
• Web Based Electronic Information Environment to
  ensure easy and timely access to OneSAF
  information

5
OneSAF Electronic Information Environment
Technical Reqs Doc
Operational Reqs Doc
Product Line Arch FW
Product Line Reqs Spec
Operational Concept Doc
Product Line Arch Spec
Reuse Direction
FDB
Reuse Repository
Draft
6
OneSAF Operational Context

• End State Scenarios seven from the ACR domain,
  two from the RDA domain, and six from the TEMO
  domain
• Provides the Military Operations that OneSAF must
  Represent
• Four representative Operational Architectures
• Provides Simulation Configuration Context
• A set of OneSAF use cases a representative set
  from each domain
• Provides Representative Uses of OneSAF within
  each Domain
• A OneSAF exercise lifecycle overview
• The set of OneSAF user categories

7
OneSAF User Categories

• Training Audience
• Observer/Controller
• Low Overhead Driver User
• Analyst

• Model Composer

• Software Developer
• Database Developer
• Scenario Developer

• Model Validator

• Configuration Manager
• Data Manager

• Technical Controller
• System Administrator

8
OneSAF Lifecycle Phases
2. Database Development
1. Event Planning
3. Software Development
4. Model Composition
10. Archival
5. Scenario Generation
9. Post-Execution AAR
6. Simulation Configuration
8. Simulation Execution
7. System Test and Verification
9
OneSAF Product Line Identification Process
Technical Requirements Document
System Categories
ORD
User Categories
Life Cycle Phases
User Workstation Environments
End State Scenarios
TRD (Product/Component Modules)
Use Cases
Product Line Architecture Framework
10
OneSAF Technical Foundation

• Systematic top down approach to software and
  simulation development
• Supports product line development within the same
  software architecture based on commonality and
  variability across the complete set of
  requirements
• Allows software quality assessment to start at
  the architecture level
• Based on system partitioning, interface
  definition, and community rules and standards
• Allows for incremental and evolutionary
  development

11
Product Line Approach

• Expanded Product Line approach to address
  commonalities and variabilities across Army user
  domains.
• Promotes End User composition of system
  configurations within Product Line to meet
  specific Modeling Simulation need (use case
  driven), not just developer composition.
• Early acquisition focus on development of Product
  Line Architecture Framework (PLAF).
• Evolved as Operational Requirements were
  defined/refined by cross domain team.
• Identified draft Products, Components and
  Services within Product Line.
• PLAF to evolve into highly detailed, rigorously
  maintained Product Line Architecture
  Specification (PLAS).

12
Product Line Processes
Product Line Development
Product Line Requirements Engineering
Product/ Component Design
Architecture Development
Implementation
objects
entities
data
Product Line Architecture
time mgmt
behaviors
services
Product Line Repository
Training/Analytical Requirements
System Composition and Configuration
. . .
Use Case 1 System
. . .
. . .
Use Case 2
Use Case 3
Use Case N
Use Case 1
13
OneSAF Product Line Architecture Framework
14
Product Line StructureComposition Example
System Configurations (Composed of Products)
Components (Tasked Out for Development)
Products (Composed of Components)
15
Data Management

• Data frameworks/models are key part of Product
  Line Architecture (e.g., scenario data, equipment
  performance data, automated behavior definitions,
  scenario output data supporting analysis and
  after action review, etc.)
• Utilize standardized Data Interchange
  Specifications/Formats as primary interface
  between components
• Promotes autonomy of components, both in
  development and in execution.
• Promotes independence of internal data model from
  logical data model.

16
OneSAF Product Based Info Flow
Phase
User
Product
OneSAF Info Exchange XML File(s)
17
OneSAF Product Based Info Flow
Phase
User
Product
OneSAF Info Exchange XML File(s)
- Military Scenario Information
- Synthetic Environment Information
- Model Composition Information
- Simulation Generation Information
18
Reuse Assessment and Direction

• OneSAF Reuse Assessment performed by
  collaborative team with members from all OneSAF
  domains, combat developer, and materiel
  developer
• Identification of numerous reuse
  decisions/opportunities for large, key areas of
  OneSAF development including Scenario
  Development, Behavior modeling, Core Physical
  Models, Equipment modeling, Environment, AAR
  tools, and KA/KE processes and products.
• Reuse products allow for early development and
  user feedback.
• Current versions of reuse products provided as
  part of OneSAF Reuse Repository web site
  traceable to requirements and available for all
  OneSAF development organizations.

19
OneSAF International Community Collaboration

• OneSAF Active International Participation since
  1997
• United Kingdom Defence Evaluation and Research
  Agency (DERA)
• Collaborative Research into Next Generation
  Simulation Technology
• Supporting the establishment of a Modeling and
  Simulation Working Group within the American,
  British, and Canadian, and Australian (ABCA)
  Armies Standardization Program
• Early Technical Transition through the OneSAF
  Testbed Baseline

20
Summary

• Teamwork Based Development Strategy
• Continuous Army Community Involvement
• Electronic Information Environment
• Operational Context
• Operational Concept Document
• Technical Foundation
• Product Line Architecture Framework
• Reuse Direction and Guidance
• International Community Collaboration

21
Questions???

• Thank You