2020Calhoun: The Naval Postgraduate School Institutional Archive (Naval Postgraduate School)Requires access

Integrating DevOps into Navy Combat Systems Development

Andrew Miller

Open publisher page 0 citations

Abstract

This thesis seeks to answer three questions concerning the Navy's adoption of DevOps and its practices. Those questions are: What is DevOps in a naval context? What stands in the way of that adoption? What are some ways that the Navy can overcome those obstacles? By drawing upon both an extensive review of literature on the topic, as well as interviews with subject-matter experts, this work provides a comprehensive understanding of the breadth and complexity of the change needed in order for the Navy to adopt a culture of DevOps as well as its attendant practices. Pursuant to the same end, this thesis proposes process architectures for continuous integration, continuous testing, and continuous certification, as well as the reorganization of the Navy's combat systems development hierarchy necessary for the transition to DevOps.

About this research paper

What this paper is about

This thesis seeks to answer three questions concerning the Navy's adoption of DevOps and its practices. Those questions are: What is DevOps in a naval context? What stands in the way of that adoption? What are some ways that the Navy can overcome those obstacles? By drawing upon both an extensive review of literature on the topic, as well as interviews with subject-matter experts, this work provides a comprehensive understanding of the breadth and complexity of the change needed in order for the Navy to adopt a culture of DevOps as well as its attendant practices. Pursuant to the same end, this thesis proposes process architectures for continuous integration, continuous testing, and continuous certification, as well as the reorganization of the Navy's combat systems development hierarchy necessary for the transition to DevOps.

Why it matters

A significance statement is not available in the OpenAlex record.

Key contribution

A contribution statement is not available in the OpenAlex record.

Method / approach

Method details are not available in the OpenAlex metadata.

Main findings

Findings are not separately available in the OpenAlex metadata.

Limitations

Limitations are not available in the OpenAlex metadata.

Applications

Application details are not available in the OpenAlex metadata.

Available abstract

This thesis seeks to answer three questions concerning the Navy's adoption of DevOps and its practices. Those questions are: What is DevOps in a naval context? What stands in the way of that adoption? What are some ways that the Navy can overcome those obstacles? By drawing upon both an extensive review of literature on the topic, as well as interviews with subject-matter experts, this work provides a comprehensive understanding of the breadth and complexity of the change needed in order for the Navy to adopt a culture of DevOps as well as its attendant practices. Pursuant to the same end, this thesis proposes process architectures for continuous integration, continuous testing, and continuous certification, as well as the reorganization of the Navy's combat systems development hierarchy necessary for the transition to DevOps.

Key concepts: DevOps, Navy, Computer science, Computer security, Engineering, Aeronautics, Political science, Software engineering

Related papers

Back to paper searchBrowse research topicsOriginal source
Integrating DevOps into Navy Combat Systems Development — Research Paper | ScholarLens