Lessons Learned in Applying Architecture to the Acquisition of Air Force Command and Control Systems

Abstract

At the Air Force Materiel Command Electronic Systems Center, we are using architecture in multiple programs to support the acquisition of Air Force Command and Control systems. This use ranges from informally augmenting traditional requirements documents to actually delivering architecture products to the contractor as a formal representation of requirements. We also use architecture to ensure that programs better understand their operational and system context within the enterprise. The architecture activities described in this paper span the time frame from 1997 to the present. During that time, we've had varying degrees of success. On the one hand, we have found the architecture to foster significant communication between the user, the acquirer, and the developer mostly by having operational subject matter experts work directly with the acquirer and contractor in developing parts of the operational architecture views. In general, we have found that the use of a disciplined approach to architecture helps all stakeholders better understand the operational, system, and technical context in which they must operate. Conversely, we've found that additional attention is needed relative to working with contractors to incorporate the use of architectures into their system/software development processes and in applying architecture to support Enterprise Integration.

Open PDF

Document Details

Document Type
Technical Report
Publication Date
Jun 01, 2005
Accession Number
ADA464240

Entities

People

  • Murray E. Daniels
  • Ruth E. Sespaniak

Organizations

  • MITRE Corporation

Tags

Communities of Interest

  • C4I
  • Engineered Resilient Systems
  • Materials and Manufacturing Processes

DTIC Thesaurus Topics

  • Acquisition
  • Air Force
  • Business Process Reengineering
  • Command And Control
  • Command And Control Systems
  • Computing System Architectures
  • Configuration Management
  • Contractors
  • Contracts
  • Control Systems
  • Engineering
  • Governments
  • Information Systems
  • Lessons Learned
  • Reliability
  • Software Development
  • Systems Engineering

Fields of Study

  • Computer science
  • Engineering

Readers

  • Joint Military Operations and Doctrine.
  • Software Engineering.

Technology Areas

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