ebook img

Army Software Architecture Workshop:Reporting on Army - FTP PDF

74 Pages·2008·1.44 MB·English
by  
Save to my drive
Quick download
Download
Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.

Preview Army Software Architecture Workshop:Reporting on Army - FTP

Army Software Architecture Workshop: Reporting on Army Experiences John Bergey Stephen Blanchette, Jr. Michael Gagliardi Mark Klein Reed Little Timothy Morrow Linda Northrop William Wood February 2008 SPECIAL REPORT CMU/SEI-2008-SR-003 Acquisition Support Program Product Line Systems Program Distribution limited by the U.S. Army This report was prepared for the SEI Administrative Agent ESC/XPK 5 Eglin Street Hanscom AFB, MA 01731-2100 The ideas and findings in this report should not be construed as an official DoD position. It is published in the interest of scientific and technical information exchange. This work is sponsored by the U.S. Department of Defense. The Software Engineering Institute is a federally funded research and development center sponsored by the U.S. Department of Defense. Copyright 2008 Carnegie Mellon University. NO WARRANTY THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT. Use of any trademarks in this report is not intended in any way to infringe on the rights of the trademark holder. Internal use. Permission to reproduce this document and to prepare derivative works from this document for internal use is granted, provided the copyright and “No Warranty” statements are included with all reproductions and derivative works. External use. This document may be reproduced in its entirety, without modification, and freely distributed in written or electronic form without requesting formal permission. Permission is required for any other external and/or commercial use. Requests for permission should be directed to the Software Engineering Institute at [email protected]. This work was created in the performance of Federal Government Contract Number FA8721-05-C-0003 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The Government of the United States has a royalty-free government-purpose license to use, duplicate, or disclose the work, in whole or in part and in any manner, and to have or permit others to do so, for government purposes pursuant to the copyright license under the clause at 252.227-7013. For information about SEI reports, please visit the publications section of our website (http://www.sei.cmu.edu/publications). Table of Contents Acknowledgments vii Executive Summary ix Abstract xiii 1 Introduction 1 1.1 About This Workshop 1 1.2 Workshop Participants 2 1.3 About the ASSIP 3 1.4 About This Report 3 2 SEI Software Architecture Technology Developments: A Digest of SEI Presentations 5 2.1 Introductory Presentation – Linda Northrop, SEI 5 2.2 Software Architecture Technology (SAT) Presentation – Mark Klein, SEI 9 2.3 Software Architecture Evaluation in DoD System Acquisitions – John Bergey and Mike gagliardi, SEI 13 2.3.1 Acquisition Planning Workshop 13 2.3.2 Examples of Applying SAT Products and Services in a System Acquisition 14 2.3.3 Improved Means for Incorporating Architecture Evaluation in a System Acquisition 15 2.3.4 Collaboration Opportunities for Piloting New Capabilities 16 3 Army Software Architecture Evaluation Experiences: A Digest of Army Presentations 19 3.1 Warfighter information Network–Tactical (WIN-T) – David Mason, C-E LCMC SEC 19 3.1.1 Summary of Evaluation Findings 20 3.1.2 Value and Impact to the Program 21 3.1.3 Issues and Recommendations 22 3.2 One semi-automated forces simulation (ONESAF) – Rob Wittman, MITRE 22 3.2.1 Summary of Evaluation Findings 23 3.2.2 Value and Impact to the Program 24 3.2.3 Issues and Recommendations 25 3.3 Army Battle Command System (ABCS) – John Landmesser, PM Battle Command 25 3.3.1 Summary of Evaluation Findings 26 3.3.2 Value and Impact of the Evaluation to the Program 27 3.3.3 Issues and Recommendations 27 3.4 Command Post of the Future (CPoF) – John Landmesser, PM Battle Command 27 3.4.1 Summary of Evaluation Findings 28 3.4.2 Value and Impact to the Program 29 3.4.3 Issues and Recommendations 29 3.5 Joint Tactical Common Operational Picture Workstation (JTCW) – John Landmesser, PM Battle Command 29 3.5.1 Summary of Evaluation Findings 31 3.5.2 Value and Impact of the Evaluation to the Program 31 3.5.3 Issues and Recommendations 31 SOFTWARE ENGINEERING INSTITUTE | i 3.6 Manned/Unmanned Common Architecture Program (MCAP) – Jack Van Kirk, PEO Aviation 32 3.6.1 Summary of Evaluation Findings 32 3.6.2 Value and Impact of the Evaluation to the Program 33 3.6.3 Issues and Recommendations 33 3.7 Common Avionics Architecture System (CAAS) – Jack Van Kirk, PEO Aviation 34 3.7.1 Summary of Evaluation Findings 35 3.7.2 Value and Impact of the Evaluation to the Program 35 3.7.3 Issues and Recommendations 35 3.8 Integrated Air and Missile Defense (IAMD) – Patrick Dowdy, Georgia Tech Research Institute (GTRI) 36 3.8.1 Summary of Evaluation Findings 37 3.8.2 Value and Impact to the Program 38 3.8.3 Issues and Recommendations 39 3.9 Aerial Common Sensor (ACS) – Brenda Klafter, L3 Communications ILEX Systems 39 3.9.1 Summary of Evaluation Findings 40 3.9.2 Value and Impact of the Evaluation to the Program 41 3.9.3 Issues and Recommendations 41 3.10 Distributed Common Ground Station – Army (DCGS-A) – David Leciston, PM DCGS-A 42 3.10.1 Summary of Evaluation Findings 43 3.10.2 Value and Impact of the Evaluation to the Program 44 3.10.3 Issues and Recommendations 44 4 General Discussion 47 4.1 Recurrent Themes 47 4.2 Other Discussion Points 48 5 Recommendations 51 6 Conclusions 53 Bibliography 55 ii | CMU/SEI-2008-SR-003 List of Figures Figure 1: Original Timeline for Army’s Planned Software Architecture Initiative Activities 9 Figure 2: Conceptual Flow of the ATAM 10 Figure 3: Other Methods and Techniques Developed by the SAT Initiative 12 Figure 4: Overview of the Acquisition Planning Workshop Activities 14 Figure 5: Application of SAT Products and Services in the System Acquisition Life Cycle 15 Figure 6: Conceptual Approach for Conducting an ATAM Evaluation as Part of Source Selection 16 Figure 7: WIN-T Context Diagram (OV-1) 20 Figure 8: OneSAF Concept 23 Figure 9: ABCS Migration Vision 26 Figure 10: CPoF High-Level System Architecture 28 Figure 11: Army JTCW High-Level System Architecture 30 Figure 12: MCAP NCORE Open Systems Architecture Instantiation 32 Figure 13: CAAS Architecture 34 Figure 14: Army IAMD Increment 2 Architecture 36 Figure 15: ACS Operational View (OV-1) 40 Figure 16: DCGS-A Heavy Brigade Combat Team High-Level Operational View (OV-1) 43 SOFTWARE ENGINEERING INSTITUTE | iii iv | CMU/SEI-2008-SR-003 List of Tables Table 1: ASSIP-Sponsored Architecture Training 6 Table 2: ASSIP-Sponsored ATAM Evaluations and QAWs 8 Table 3: Summary of ACS Risk Themes 41 SOFTWARE ENGINEERING INSTITUTE | v vi | CMU/SEI-2008-SR-003 Acknowledgments The Acquisition Support Program (ASP) and Product Line Systems (PLS) Program of the Carne- ® gie Mellon Software Engineering Institute (SEI) have jointly developed this special report. The authors would like to thank Ceci Albert of the ASP and Larry Jones of the PLS Program for their careful review and comments for improving this report. ® Carnegie Mellon is registered in the U.S. Patent and Trademark Office by Carnegie Mellon University. SOFTWARE ENGINEERING INSTITUTE | vii viii | CMU/SEI-2008-SR-003

Description:
Common Avionics Architecture System (CAAS) – Jack Van Kirk, PEO Figure 16 : DCGS-A Heavy Brigade Combat Team High-Level Operational View (OV-1).
See more

The list of books you might like

Most books are stored in the elastic cloud where traffic is expensive. For this reason, we have a limit on daily download.