Using SREM to Specify Command and Control Software Requirements

Abstract

This report briefly describes command and control systems and the documentation standards currently used to specify their embedded computer software requirements. The Software Requirements Engineering Methodology (SREM9 appears to satisfy these documentation standards. However, the original SREM design did not specifically address command and control needs, thereby leaving uncertain the exact extent of the SREM's capabilities to specify problems unique to this domain. To resolve this issue, the SREM is used to specify the software requirements for a small, but representative, command and control problem. The results show that, in general, SREM is capable of specifying command and control software requirements, but that certain problems exist. Some of the problems are easily resolved using the self-extension mechanisms of SREM, but other problems are sufficiently serious to warrant further investigations involving full-scale command and control systems.

Open PDF

Document Details

Document Type
Technical Report
Publication Date
Dec 01, 1982
Accession Number
ADA124429

Entities

People

  • William E. Rzepka

Organizations

  • Rome Laboratory

Tags

Communities of Interest

  • C4I
  • Space
  • Weapons Technologies

DTIC Thesaurus Topics

  • Acquisition
  • Command And Control
  • Command And Control Systems
  • Computer Programming
  • Computer Programs
  • Computers
  • Control Systems
  • Databases
  • Engineering
  • Human-Machine Interfaces
  • Language
  • Simulations
  • Simulators
  • Software Design
  • Software Development
  • Standards
  • User Interface

Fields of Study

  • Computer science

Readers

  • Joint Military Operations and Doctrine.
  • Software Engineering.
  • Systems Analysis and Design

Technology Areas

  • Fully Networked C3
  • Fully Networked C3 - Command and Control