The Crow and the Pitcher

1
(No Transcript)
2
Agenda

• The Story Thus Far Verification, Validation
  Accreditation (VVA) and the Importance of Its
  Documentation
• Encountering a Problem The Current
  Documentation Process
• Discovering the Pitcher VVA Documentation Tool
  (VDT) VVA Documentation Standardization
• Raising the Water Line Benefits of the VDT
• Necessity Is the Mother of Invention The Way
  Ahead

3
(No Transcript)
4
VVA Its Documentation

• VVA Process
• Evaluation of MS fidelity for the intended use
• Concept well amalgamated in the DON MS community
• VVA Documentation
• Artifacts used to assess MS fidelity
• Assessment artifacts for MS use
• Archival record of existing MS

Implementation still needs standardization
Inter-relationship of the MS, VVA, and VVA
Documentation Processes
5
VVA 101
Requirements Development Management
MS Need
Technical Solution
Product Integration
Support
MS Process
Intended Use
Design, Develop, Test
Functionality, Fidelity, Credibility
Integrate, Test, Deliver
Operations, Maintenance, Disposal
Accreditation VV Planning
VVA Process
Conceptual Model Validation
Design Verification
Implementation Verification
Results Validation
Data VV
VV Plan
VV Report
Accreditation Report
Accredit. Decision Letter
VVA Documentation
Accreditation Plan
Historical Database Entry
Evaluation
VVA Documentation Process
Original Intended Use
Re-Use (First-order Assessment)
As-Is
Modular
6
Applications for VVA Documentation

• Composable interoperable MS interplay of
  several individual, or modular, MS.
• Assessment Strategy for MS Modules
• 1st Order (High) Correct module for intended
  use?
• 2nd Order (Middle) Code line-by-line dovetails
  w/the new application?
• 3rd Order (Low) Specific steps required to make
  the module fit the greater composition?

7
(No Transcript)
8
The Current VVA Documentation Process
DON MS VVAImplementationHandbook Vol. I
SECNAVINST 5200.40A (draft)
MS Documentation
VVA Output Artifacts
Author
9
Standardized VVA Evaluation

• Goal Stop Reinventing the Wheel
• Streamline the process
• Develop standardized, automated tools to
  support VVA -Feinberg-Foundations 02
  Conference
• Pre-Req Standardized Mechanism and
  Infrastructure for the Evaluation of MS
  Credibility
• Solution Standardize VVA Documentation

Bottom Line Documentation should not require
thesis-level research to get the format right.
10
(No Transcript)
11
How?

• Standardization Infrastructure
• RAND Policies, standards, process, VVA, and
  use-specific databases
• Policy SECNAVINST 5200.40
• Standardized Implementation ???
• Process DON MS VVA Implementation Handbook,
  Volume 1
• VVA VVA Implementation
• Database NMSIS and MS Repository

12
Four Core Documents From Intended Use to MS
Fidelity
Purpose From MS Development to MS Fidelity
Accreditation Plan
13
Four Core Documents From Intended Use to MS
Fidelity
Purpose From MS Development to MS Fidelity
Accreditation Plan
VV Plan
14
Four Core Documents From Intended Use to MS
Fidelity
Purpose From MS Development to MS Fidelity
Accreditation Plan
VV Plan
VV Report
15
Four Core Documents From Intended Use to MS
Fidelity
Purpose From MS Development to MS Fidelity
Accreditation Plan
VV Plan
VV Report
Accreditation Report
16
(No Transcript)
17
Assured Security

• DON Conformity to DOD network security standards
• Users Transparency of information among team
  members while preserving security for proprietary
  information

18
Benefits to the User

• Document consistently and holistically
• VVA-specific framework to organize and record
  VVA information in a consistent and organized
  manner.
• Do more in less time
• The VDT is founded on DON VVA policy and
  implementation guidance.
• References are available throughout the tool.
• Cut-and-paste existing information

Bottom Line Lets not reinvent the wheel.
Reduce document-delivery time by not starting
with a blank slate.
19
Data-Aware Application

• DON
• Consistent information across all documents
• Data capture to the NMSIS
• User
• Elimination of Redundant Data Entry

As a data-aware application, common information
regarding the MS (Description, CONOPs, Use
History, etc) are propagated across all four
documents, reducing the resources expended on
repetitive reporting of duplicate information.
Further, this MS metadata will be captured in
the MS Repository.
20
Online Collaboration

• DON Reduced resources expended on collaboration
  of geographically dispersed members.
• User Collaborative editing and streamlined
  process

21
Taking the Guesswork Out of VVA

• Publish to Word
• Print to your local printer quickly efficiently
• Polish your published documents to fit your
  organizations preferences
• Benefits
• DON Standardized artifacts for all DON MS
• User Conformity to DON VVA precepts while
  preserving the flexibility required to tailor
  VVA according to need

22
VDT Users/Customers

• N81 Assessments Costs/Capability models
• NMSO Navy MS Office
• NRL Navy Research Laboratory
• NDAT NAVSEA Dahlgren VVA Team
• COTF Commander Operational Test Evaluation
  Force
• NRL PEOIWS2E
• JHU APL Johns Hopkins University Applied Physics
  Laboratory
• SPAWAR Space Warfare Systems Center

23
(No Transcript)
24
NMSIS Standardizing MS Reuse

• Navy MS Information Service (NMSIS)
• Repository for information re Navy MS,
  including those MS that have gone through VVA
• Current Problems
• NMSIS difficult to enter MS information
• Insufficient data for searches
• People are using COTS to find DONMS

25
VVML

• VVML VVA-specific eXtensible Markup Language
• XML Allows for data to be distributed between
  applications disregarding the platform on which
  it resides
• Auto-entry of VVA information in NMSIS
• Easier/productive searches
• Information and searches conducted in the correct
  forum

• NMSIS difficult to enter MS information
• Insufficient data for searches
• People are using COTS to find DONMS

26
VDT Development

• Control mechanisms
• IPT
• CMMI Process
• Requirements Derivation Control
• Collection of new requirements candidates
• Vetting/solidification of new requirements
• Tracking/SRS
• Configuration Management

27
Future Development

• V.2.2- Requirements Traceability Table
• Linking the relationships between requirements,
  acceptability criteria, VV tasks, and
  VV-results analysis.
• Future Plans
• DON Standardization
• Move to DOD level

More to come... Pending your comments!!! Provide
your feedback and suggestions anytime vvadoc_at_navy
.mil
28
Conclusions

• VVA assesses MS for credibility according the
  intended use
• VVA documentation must be standardized for
  current and reuse assessments
• The VDT automates the VVA planning and
  documentation processes
• VDT links to the NMSIS will expand the usefulness
  of archived MS information

29
Questions?

• NMSO VVA
• http//navmsmo.hq.navy.mil
• Click VVA on the left navigation bar.
• The VDT can be accessed from this site
• Points of Contact
• NMSO VVA vva_at_navmsmo.hq.navy.mil
• VDT vvadoc_at_navy.mil
• VDT Developer David H. Broylesdavid.h.broyles_at_na
  vy.mil [phone]