Simone Youngblood

1
DoD MS VVARecommended Practices Guide
Fall 99 SIW VVA Forum 16 Sep 99
Simone Youngblood DMSO VVA Technical Director
2
DoD RPG History

• DoD I
• Established common terminology and defined high
  level roles and responsibilities
• DoD RPG
• Defined underlying philosophy, principles,
  methodologies recommended for use in DoD VVA
  efforts
• First distributed in 1996
• Well-received (welcomed)
• adopted by numerous programs (e.g., JADS, JWARS,
  JSIMS)
• accepted by Services -- used as foundation for
  Service VVA policies

3
Reader Feedback

• GREAT! BUT . . .
• Too long
• Not enough detail
• One size fits all
• Doesnt address needs of entire audience
• Recommendations
• Provide more technical detail
• which techniques to use when
• cost estimation
• metrics
• Address a broader audience
• Make it easier to find what is needed

4
Objective

• Update and Enhance VVA Recommended Practices
  Guide (RPG)
• Account for diversity of audience
• Tailored messages, guidance for each
• Account for diversity of situations
• Context specific guidance
• Focus on practical vs theoretical
• Handbook vs Textbook

Address user feedback and issues associated with
use of prior RPG
5
Basic Approach

• Reader-based -- address diverse audiences
• Not one size fits all
• Allow reader to see self in document
• Reader profiling used to determine paths
• Non-linear
• Role/function (user, manager, developer, VV
  agent, accreditor)
• simulation (legacy, new stand-alone, federation)
• Multiple levels of detail
• Multi-media
• HTML Web-based / CD document
• Separate role-oriented pamphlets
• Technical papers, references
• Advantages
• Increased comprehension readers read what they
  need to
• Facilitates usage multiple paths, multiple
  levels of detail
• Allows growth and development easy addition of
  information

6
Basic Document -- Different Audiences
Funds the development, (or modification) and
preparation of MS for his specific
application. Has the most to lose if MS results
arent believable.
Typically works for the USER. Manages the MS
development effort. Ensures that the USERs MS
requirements are accurately captured and
implemented in the software.
MS PROGRAM MANAGER
USER
Typically works for the USER. Ensures that VV
and other evaluation efforts support
accreditation of MS for specific
applications. Needs guidance on how to
determine how much VVA is enough
Needs guidance on how VVA impacts MS credibility
Needs guidance on importance of VV to the
application
Needs guidance on how to plan, execute VV and
how to serve as bridge between USER and DEVELOPER
Needs guidance on how to coordinate with VV
activities
ACCREDITATION AGENT
MS DEVELOPER
Typically works for MS PROGRAM MANAGER Builds
the software. Performs/assists with VV
activities.
VV AGENT
Typically works for the USER. Plans, conducts,
oversees and documents VV activities
appropriately.
7
Basic Document -- Different Simulation Types
VV AGENT
Guidance is provided for each role and model
category as appropriate
MS PM
ACCREDITATION AGENT
MS DEVELOPER
USER
Stand-Alone MS Federates
Federations
Legacy
New
As-Is
Legacy, Major Modifications
Minor Mods
Addressing Diverse Situations
8
Principal Authors
MS PROGRAM MANAGER Terry Prosser,
Industry JWARS, C4ISR Dave Hoffman, Govt
MS DEVELOPER Mike Metz, Ed Harvey
Industry STOW, JWARS, JSIMS, JCOS
VV AGENT Bob Lewis, Industry NMD, DIS
9
Additional Authors
Technical AuthorsDale Pace, Averill Law, Jack
Morrison, Bob Lewis, Paul Meussig, Priscilla
Glasow, Scott Harmon, David Gross, Dave Hoffman,
Susan Solick, Walt Stanley, Candace Conwell, Bob
Senko, Dennis Laack, . . . .
Synthesis TeamSusan SolickWalt StanleyJack
Morrison
10
RPG -- Breadth and Depth
Each Role/Simulation Type
VVA Activities
VVA Activities
Lessons Learned
Lessons Learned
Special Topics
Special Topics
Introduction
Roles
Roles
Profile
Profile
Elaborations
Elaborations
Elaborations
Contents
Profiles
Elaborations
Elaborations
Policies
Glossary
Elaborations
References
FAQs
Index
Technical Papers
Technical Papers
Technical Papers
Technical Papers
Technical Papers
Technical Papers
Technical Papers
Technical Papers
Technical Papers
Technical Papers
SEARCH
______________
11
RPG -- As Reader Sees It
MS Life Cycle
Introduction
Overview
Leveraging
Key Concepts
VVA Activities
Conceptual Models
Benefits
Tools
Definitions
Techniques
Roles/Functions
Configuration Management
MS Life Cycle
Credibility Fidelity
Rqmts Engr
Cost Implications
Role VVA Responsibilities Relationships
Special Topics
VV and TE
Data
Build Profile
Risk
Stand-Alone Legacy, As-Is or Minor Mod
Behavior Validation
Lessons Learned
Glossary
Stand-Alone New or Legacy, Major Mod
References
Federation
FAQs
Sample Problems
12
RPG Structure -- Baseline Information

• Main Level for Each Role / Simulation Type
• Introduction/Overview
• Common to all
• VVA Responsibilities Challenges of the Role
• My impact on VVA -- VVAs impact on me
• My responsibilities to VVA
• Challenges I face relative to VVA
• VVA Functions of the Role for the Simulation
  Type
• Simulation Type development process involved
  and related VVA process overview
• How I fulfill the responsibilities in the face of
  the challenges
• Credibility and Fidelity
• Relationships With Other Roles
• What information I share with others
• Identifying and Saving Essential Information
• VVA Cost Implications and Resourcing
• Lessons Learned (interspersed throughout)
• Sample Problems

2000 effort
13
RPG Structure -- Technical Detail

• Elaborations
• Credibility and Fidelity
• Conceptual Model
• Data
• Validation Tools and Techniques
• Verification Tools and Techniques
• Behavioral Validation
• Cost and Risk
• SMEs
• Requirements Engineering
• VVA and TE

14
Product Vision

• On-Line access under the DMSO Home Page
• Viewers can browse any part of the RPG
• OR
• Viewers can answer questions that will compose a
  tailored RPG automatically
• Based on Role and Simulation Type
• Viewers can print out any or all
• Nested layers of information available
• Main level provides basic guidance
• Mouse-overs for definitions, comments
• Pop-up Windows for more detail
• Hypertext links for technical elaborations

15
Current Status
Nearing Completion
Synthesis Group July 31
Publishing Group September 30
First Draft December 30
-- Requires significant coordination
configuration management effort --
16
Thought For The Future

• 2000
• Two builds at 6-month intervals
• Role-Oriented pamphlets
• 2001 -- Steady state
• quarterly reviews
• quarterly updates
• Allow addition of current lessons learned
• Allow addition of new information

17
HELP!

• Seeking assistance with
• Lessons Learned
• application based
• domain oriented
• Sample problems
• domain oriented