Panel 7 - Testing Considerations for Reuse of Weapons System Components

Abstract

Open Architecture is a Navy-wide imperative Open Architecture (OA) is the confluence of business and technical practices yielding modular, interoperable systems that adhere to open standards with published interfaces. This approach significantly increases opportunities for innovation and competition, enables re-use of components, facilitates rapid technology insertion, and reduces maintenance constraints. The adoption of OA principles is expected to deliver increased warfighting capabilities in a shorter time at reduced cost. Adoption of NOA principles will led to faster cycle times for delivery of capability to the Fleet at potentially substantial reduction in cost. But there are issues that the shortened timelines also creates. The acceleration of delivery of upgrades to the Fleet also results in the need for more frequent testing - which also translates to increased cost to test and certify systems for use. As we try to reduce the cost of testing, we still need to provide assurance that our mission critical systems perform as required and are safe to operate. This work needs additional sponsorship to move forward.

Open PDF

Document Details

Document Type
Technical Report
Publication Date
May 01, 2009
Accession Number
ADA528185

Entities

People

  • Mark D. Wessman

Tags

Communities of Interest

  • Weapons Technologies

DTIC Thesaurus Topics

  • Abstracts
  • Acquisition
  • Addressing
  • Availability
  • Classification
  • Commerce
  • Competition
  • Confluence
  • Contracts
  • Demographic Cohorts
  • Information Operations
  • Instructions
  • Landing Pads
  • Maintenance
  • Monitoring
  • Standards

Readers

  • Economics
  • Enterprise Information Systems Architecture and Joint Command Capability Interoperability Support.
  • Life Cycle Cost Analysis