System Contextual Development of Physical Environmental Representations

1
System Contextual Development of Physical
Environmental Representations

• Virginia T. Dobey, SAIC/DMSO
• Virginia.Dobey.CTR_at_dmso.mil
• [phone]
• Paul G. Foley,
• Quantum Research/DMSO
• Paul.Foley.CTR_at_dmso.mil
• [phone]

2
Outline

• Background
• Statement of Goals
• Process for Developing Physical Environment
  Representations
• Developing the System Engineering Context
• System Engineering ContextModifying the
  Representation
• Completing the Environment Concept Model
• Next Step

3
The Original Challenge

• During a June, 2002 Program Review, the DMSO
  Technical Director, Dr. S.K. Numrich, asked how
  the Environmental Data Models (EDMs) being funded
  by Army (some also funded by DMSO) were different
  from the Environment Concept Model1 (ECM)
  paradigm that she, Doug Clark, and Chris
  Chadbourne had developed for the Navys MARVEDS
  (Maritime Virtual Environment Data System)
  program.
• Since V. Dobey had helped develop the original
  MARVEDS concept and had explained how an ECM
  contained essential VVA documentation for its
  related system (co-author of the SIMTECT 2000
  paper), Dr. Numrich asked Ms. Dobey to perform a
  comparison of the two concepts.
• 1cf. Chadbourne Clark, 98F-SIW-097, 99F-SIW-093
  and Numrich, Dobey, Chadbourne Clark, SIMTECT
  2000 paper 039, among others

4
The Challenge Became Goals

• To provide system developers with the needed
  information to properly develop a representation
  of the physical environment in systems, whether
  simulation or operational
• To flesh out the Environment Concept Model
  (ECM), defining what it is and does and providing
  specific information on how to develop an ECM for
  a system

5
The Results, so far

• This challenge resulted in a series of papers
  describing
• How the various models for developing
  environmental representations (EDM / Common Data
  Model Framework, ECM, the Conceptual Reference
  Model) related to each other and to the system
  development process,
• A process for developing an environmental
  representation which is extended from both the
  FEDEP and its related VVA overlay, and
• How to implement the first part of that process
  (the development of a complete set of
  requirements for a consistent representation of
  the physical natural environment.
• How to implement the second part of that process
  (the development of the needed system engineering
  context that converts requirements into a
  physical environmental representation that is
  actually implemented in a system
• What an EDM actually is (and what it is not)

6
Citation Information

• VVA Process Overlay for the FEDEP (03S-SIW-085)
  (with R.O. Lewis)
• Foundations for Verification and Validation in
  the Natural Environment, Special Topic Paper in
  the DoD VVA Recommended Practices Guide
• Representing the Natural Environment An
  Integrated Development Process (03S-SIW-083)
• System Environmental Representation Building
  for Success from the Very Beginning (I/ITSEC
  2003 paper 1378)
• System Contextual Development of Physical
  Environmental Representations (04S-SIW-116, this
  paper)
• Environmental Data Models Necessary but Not
  Sufficient for Interoperability (04S-SIW-114)
  (with P.L. Eirich)

7
Existing
Authoritative
Existing
Authoritative
Info on
Info on
Environmental Overlay to the FEDEP
Overall
Domain
Existing
Domain
Federate
Overall
Domain
Existing
Domain
Federate
Available
Supporting
Available
Supporting
Resources
Plans
Descriptions
Scenarios
Information
Documentation
Resources
Resources
Plans
Descriptions
Scenarios
Information
Documentation
Resources
Initial
Initial
Planning
Planning
Object Model
Define Federation
Define Federation
Define Federation
Documents
Documents
Objectives
Objectives
Objectives
Data Dictionary
1
1
1
Multiple Items
Multiple Items
Elements
Federation
Federation
Modified/New
Modified/New
Existing
Existing
Existing
Perform Conceptual
Scenario(s)
Perform Conceptual
Perform Conceptual
Scenario(s)
Federates
Federates
Conceptual
FOMs and BOMs
Analysis
Analysis
Analysis
Models
SOMs
SOMs
2
2
2
Implemented
Implemented
Federation
Federation
Infrastructure
Infrastructure
Design Federation
Federation Development and Execution Plan
Design Federation
Design Federation
Federation Development and Execution Plan
RTI Initialization
RTI Initialization
Data (modified)
Data (modified)
List of Selected (existing) Federates
List of Selected (existing) Federates
3
3
3
FOM
FOM
Federate
Federation
Federation
Objectives Verification
FED/FDD
FED/FDD
Federation
Conceptual
Conceptual
Develop Federation
Develop Federation
Develop Federation
Designs
Model
Model
Scenario
Scenario
Instances
Instances
4
4
4
Supporting
Supporting
Databases
Databases
Conceptual Model Validation
Tested
Tested
Plan, Integrate, and
Plan, Integrate, and
Plan, Integrate, and
Federation
Federation
Establish Environmental Requirements
Test Federation
Test Federation
Test Federation
Federation Agreements
5
5
5
Execution
Design Verification
Environment
Execute Federation
Execute Federation
Execute Federation
Description
and Prepare Outputs
and Prepare Outputs
and Prepare Outputs
6
Derived
6
6
Derived
Develop Environment Portion of
Federation Conceptual Model
Outputs
Outputs
Implementation Verification
Federation Test Criteria
Analyze Data and
Analyze Data and
Analyze Data and
Federation Requirements
Evaluate Results
Evaluate Results
Evaluate Results
Federation Objectives Statement
7
7
7
Design Environmental Representation
Based on IEEE P1516.3TM Draft Recommended
Practice for High Level Architecture (HLA)
Federation Development and Execution Process
(FEDEP), Institute for Electrical and Electronics
Engineers, 7 Oct 02 As adapted by Dobey Lewis,
03S-SIW-085.
Federation Validation
Reusable
Lessons
Final
Reusable
Lessons
Final
Products
Learned
Report
Products
Learned
Report
Implement Environmental Representation
Accreditation Decision
Integrate and Test Environmental Representation
Post-Execution Follow-up and Archival
8
Environment Reference Implementation Process
9
Developing Context DoD Architectural Framework
10
Specifying System Context

• OV-1 High level depiction of the capabilities
  required and their interactions
• Intended user
• Extensibility of capabilities
• Systems and Technical Views provide the
  specifications that support the
• Net-Ready Key Performance Parameters (NR-KPP)
• Interoperability Key Performance Parameters
  (I-KPP)
• Under the new DoD Acquisition Process,
  architecture views and KPPs replace the statement
  of system requirements (provide the system
  engineering context into which the environmental
  representation must fit) System developers
  build to supply these capabilities within the
  bounds of the KPPs

11
KPPs Which Impact the Environmental Representation

• Net-readiness (XML, other appropriate formats)
• Quality of service (usage, availability, and
  response time)
• Net-centric information assurance defense (access
  controls, data integrity assurance)
• Information resource visibility and access
  (search / subscribe / publish, tailoring,
  degradation, staging, transformation)
• Synchronicity of information and updates
• Availability and utilization of Global
  Information Grid (GIG) Enterprise Services
• Cross-security domain information exchange

12
Other Relevant KPPs

• Availability / reliability of the source
  information
• Capacity of the network, nodes, and system
• Cohesiveness of information
• Correlation
• Cross-platform functionality
• Data interoperability
• Delivery management (including network
  priorities)
• Directory service utilization (specifically,
  metadata quality)
• Information flow awareness
• Interface definition
• Process availability
• Standards and standards-based processing

13
Developing System Requirements (the Inferred
Environment)
Establish Environmental Requirements
Develop Environment Portion of
Federation Conceptual Model
14
Incorporating and Documenting System Context(the
Implemented Environment)
Design Environmental Representation
Implement Environmental Representation
Integrate and Test Environmental Representation
15
Completing the ECM

• Inferred Environmental Baseline A complete
  collection of environmental requirements based on
  the OV-1 as developed IAW earlier (background)
  papers. Speaks to the systems requirements
  without engineering limitations
• Implemented Environmental Baseline Inferred
  Environment Baseline adjusted to reflect system
  engineering context (primarily determined by
  system KPPs and their priorities) into which the
  representation must fit
• VVA Documentation Describes the reasons for the
  difference between the Inferred and Implemented
  Environmental Baselines, traces these differences
  to specific engineering parameters and design
  decisions

16
Next Step Application

• Development of a comprehensive process can be
  beneficial, but
• It can be viewed as a mere intellectual exercise
  until proven viable and valuable
• Application of this methodology to a real system
  will demonstrate that it can work, and will
  provide lessons learned.
• Looking for collaboration partners let DMSO
  know if youre interested