Translation of User Needs to System Requirements

Abstract

Department of the Navy system acquisition begins with a statement of user need. Delivery of required capability depends heavily on the effective translation of user need to system requirements. Failure typically results in program cost overruns, schedule slippage, and sometimes partial or complete failure to deliver needed capability. Architectures as part of systems engineering were created to cope with the growing complexity of modern systems. The Navy develops and operates some of the most complex systems in the world. Yet, architecture development, while mandated, remains largely ancillary to the systems engineering process. As a result, much of the engineering advantage of architectures remains untapped. This study examined U.S. Navy policy, process, and current engineering and architectures standards and identified recommendations to improve the process of translating user needs to system requirements while facilitating the use of architectures.

Open PDF

Document Details

Document Type
Technical Report
Publication Date
Mar 01, 2009
Accession Number
ADA496864

Entities

People

  • Patrick R. Hoff

Organizations

  • Naval Postgraduate School

Tags

Communities of Interest

  • C4I
  • Ground and Sea Platforms
  • Sensors
  • Space
  • Weapons Technologies

DTIC Thesaurus Topics

  • Air Force
  • Command And Control
  • Command And Control Systems
  • Commerce
  • Complex Systems
  • Engineering
  • Information Systems
  • Military Science
  • National Security
  • Naval Operations
  • Naval Warfare
  • Navy
  • Organizational Structure
  • Standards
  • System Of Systems
  • Systems Engineering
  • Warfare

Fields of Study

  • Computer science
  • Engineering

Readers

  • Life Cycle Cost Analysis
  • Software Engineering.
  • Strategic Security Studies