U.S. Department of EnergyOffice of Scientific and Technical Information
Quantitative methods for developing C2 system requirement
Abstract
The US Army established the Army Tactical Command and Control System (ATCCS) Experimentation Site (AES) to provide a place where material and combat developers could experiment with command and control systems. The AES conducts fundamental and applied research involving command and control issues using a number of research methods, ranging from large force-level experiments, to controlled laboratory experiments, to studies and analyses. The work summarized in this paper was done by Pacific Northwest Laboratory under task order from the Army Tactical Command and Control System Experimentation Site. The purpose of the task was to develop the functional requirements for army engineer automation and support software, including MCS-ENG. A client, such as an army engineer, has certain needs and requirements of his or her software; these needs must be presented in ways that are readily understandable to the software developer. A requirements analysis then, such as the one described in this paper, is simply the means of communication between those who would use a piece of software and those who would develop it. The analysis from which this paper was derived attempted to bridge the ``communications gap`` between army combat engineers and software engineers. It sought to derive and state themore »
- Authors:
- Publication Date:
- Research Org.:
- Pacific Northwest Lab., Richland, WA (United States)
- Sponsoring Org.:
- Department of Defense, Washington, DC (United States)
- OSTI Identifier:
- 10171315
- Report Number(s):
- PNL-SA-20720; CONF-9206239-1
ON: DE92019127
- DOE Contract Number:
- AC06-76RL01830
- Resource Type:
- Conference
- Resource Relation:
- Conference: 60. Military Operations Research Society symposium,Monterey, CA (United States),23-25 Jun 1992; Other Information: PBD: Jun 1992
- Country of Publication:
- United States
- Language:
- English
- Subject:
- 45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEFENSE; 99 GENERAL AND MISCELLANEOUS//MATHEMATICS, COMPUTING, AND INFORMATION SCIENCE; COMPUTERIZED CONTROL SYSTEMS; ORGANIZATIONAL MODELS; US DOD; ENGINEERING; FEASIBILITY STUDIES; AUTOMATION; COMMUNICATIONS; C CODES; 450000; 990200; MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEFENSE; MATHEMATICS AND COMPUTERS
Citation Formats
Tyler, K K. Quantitative methods for developing C2 system requirement. United States: N. p., 1992.
Web.
Tyler, K K. Quantitative methods for developing C2 system requirement. United States.
Tyler, K K. 1992.
"Quantitative methods for developing C2 system requirement". United States. https://www.osti.gov/servlets/purl/10171315.
@article{osti_10171315,
title = {Quantitative methods for developing C2 system requirement},
author = {Tyler, K K},
abstractNote = {The US Army established the Army Tactical Command and Control System (ATCCS) Experimentation Site (AES) to provide a place where material and combat developers could experiment with command and control systems. The AES conducts fundamental and applied research involving command and control issues using a number of research methods, ranging from large force-level experiments, to controlled laboratory experiments, to studies and analyses. The work summarized in this paper was done by Pacific Northwest Laboratory under task order from the Army Tactical Command and Control System Experimentation Site. The purpose of the task was to develop the functional requirements for army engineer automation and support software, including MCS-ENG. A client, such as an army engineer, has certain needs and requirements of his or her software; these needs must be presented in ways that are readily understandable to the software developer. A requirements analysis then, such as the one described in this paper, is simply the means of communication between those who would use a piece of software and those who would develop it. The analysis from which this paper was derived attempted to bridge the ``communications gap`` between army combat engineers and software engineers. It sought to derive and state the software needs of army engineers in ways that are meaningful to software engineers. In doing this, it followed a natural sequence of investigation: (1) what does an army engineer do, (2) with which tasks can software help, (3) how much will it cost, and (4) where is the highest payoff? This paper demonstrates how each of these questions was addressed during an analysis of the functional requirements of engineer support software. Systems engineering methods are used in a task analysis and a quantitative scoring method was developed to score responses regarding the feasibility of task automation. The paper discusses the methods used to perform utility and cost-benefits estimates.},
doi = {},
url = {https://www.osti.gov/biblio/10171315},
journal = {},
number = ,
volume = ,
place = {United States},
year = {Mon Jun 01 00:00:00 EDT 1992},
month = {Mon Jun 01 00:00:00 EDT 1992}
}