Search results
1 – 10 of over 1000Joe Garcia, Russell Shannon, Aaron Jacobson, William Mosca, Michael Burger and Roberto Maldonado
This paper aims to describe an effort to provide for a robust and secure software development paradigm intended to support DevSecOps in a naval aviation enterprise (NAE) software…
Abstract
Purpose
This paper aims to describe an effort to provide for a robust and secure software development paradigm intended to support DevSecOps in a naval aviation enterprise (NAE) software support activity (SSA), with said paradigm supporting strong traceability and provability concerning the SSA’s output product, known as an operational flight program (OFP). Through a secure development environment (SDE), each critical software development function performed on said OFP during its development has a corresponding record represented on a blockchain.
Design/methodology/approach
An SDE is implemented as a virtual machine or container incorporating software development tools that are modified to support blockchain transactions. Each critical software development function, e.g. editing, compiling, linking, generates a blockchain transaction message with associated information embedded in the output of a said function that, together, can be used to prove integrity and support traceability. An attestation process is used to provide proof that the toolchain containing SDE is not subject to unauthorized modification at the time said critical function is performed.
Findings
Blockchain methods are shown to be a viable approach for supporting exhaustive traceability and strong provability of development system integrity for mission-critical software produced by an NAE SSA for NAE embedded systems software.
Practical implications
A blockchain-based authentication approach that could be implemented at the OFP point-of-load would provide for fine-grain authentication of all OFP software components, with each component or module having its own proof-of-integrity (including the integrity of the used development tools) over its entire development history.
Originality/value
Many SSAs have established control procedures for development such as check-out/check-in. This does not prove the SSA output software is secure. For one thing, a build system does not necessarily enforce procedures in a way that is determinable from the output. Furthermore, the SSA toolchain itself could be attacked. The approach described in this paper enforces security policy and embeds information into the output of every development function that can be cross-referenced to blockchain transaction records for provability and traceability that only trusted tools, free from unauthorized modifications, are used in software development. A key original concept of this approach is that it treats assigned developer time as a transferable digital currency.
Details
Keywords
- Software development
- Blockchain
- Cybersecurity
- Operational flight program
- Secure development environment
- Secure virtual machine
- Zero trust
- Embedded systems
- Mission-critical systems
- OFP
- DevOps
- DevSecOps
- Software support activity
- SSA
- SDE
- Permissioned blockchain
- Cryptocurrency
- Time-limited authorization for developer action
- TADA
- Code signing
- Trusted software guard
- SGX
- Trusted eXecution technology
- TXT
- Trusted platform module
- Self-hosting
- Controlled access blockchain
- CABlock
- Role-based access control
- RBAC
Joshua R. Muckensturm and Dave C. Longhorn
This paper introduces a new heuristic algorithm that aims to solve the military route vulnerability problem, which involves assessing the vulnerability of military cargo flowing…
Abstract
Purpose
This paper introduces a new heuristic algorithm that aims to solve the military route vulnerability problem, which involves assessing the vulnerability of military cargo flowing over roads and railways subject to enemy interdiction.
Design/methodology/approach
Graph theory, a heuristic and a binary integer program are used in this paper.
Findings
This work allows transportation analysts at the United States Transportation Command to identify a relatively small number of roads or railways that, if interdicted by an enemy, could disrupt the flow of military cargo within any theater of operation.
Research limitations/implications
This research does not capture aspects of time, such as the reality that cargo requirements and enemy threats may fluctuate each day of the contingency.
Practical implications
This work provides military logistics planners and decision-makers with a vulnerability assessment of theater distribution routes, including insights into which specific roads and railways may require protection to ensure the successful delivery of cargo from ports of debarkation to final destinations.
Originality/value
This work merges network connectivity and flow characteristics with enemy threat assessments to identify militarily-useful roads and railways most vulnerable to enemy interdictions. A geographic combatant command recently used this specific research approach to support their request for rapid rail repair capability.
Details
Keywords
The purpose of this paper is to develop an original model and a solution procedure for solving jointly three main strategic fleet management problems (fleet composition…
Abstract
Purpose
The purpose of this paper is to develop an original model and a solution procedure for solving jointly three main strategic fleet management problems (fleet composition, replacement and make-or-buy), taking into account interdependencies between them.
Design/methodology/approach
The three main strategic fleet management problems were analyzed in detail to identify interdependencies between them, mathematically modeled in terms of integer nonlinear programing (INLP) and solved using evolutionary based method of a solver compatible with a spreadsheet.
Findings
There are no optimization methods combining the analyzed problems, but it is possible to mathematically model them jointly and solve together using a solver compatible with a spreadsheet obtaining a solution/fleet management strategy answering the questions: Keep currently exploited vehicles in a fleet or remove them? If keep, how often to replace them? If remove then when? How many perspective/new vehicles, of what types, brand new or used ones and when should be put into a fleet? The relatively large scale instance of problem (50 vehicles) was solved based on a real-life data. The obtained results occurred to be better/cheaper by 10% than the two reference solutions – random and do-nothing ones.
Originality/value
The methodology of developing optimal fleet management strategy by solving jointly three main strategic fleet management problems is proposed allowing for the reduction of the fleet exploitation costs by adjusting fleet size, types of exploited vehicles and their exploitation periods.
Details
Keywords
Tommie L. Ellis, Robert A. Nicholson, Antoinette Y. Briggs, Scott A. Hunter, James E. Harbison, Paul S. Saladna, Michael W. Garris, Robert K. Ohnemus, John E. O’Connor and Steven B. Reynolds
Rising operational costs and software sustainment concerns have driven the Air Force to move to newer technology to ensure that the Air Force Standard Base Supply System (SBSS…
Abstract
Purpose
Rising operational costs and software sustainment concerns have driven the Air Force to move to newer technology to ensure that the Air Force Standard Base Supply System (SBSS) can continue to provide affordable and sustainable mission support in the years to come. This paper aims to summarize the successful software modernization effort the Air Force undertook to achieve that objective.
Design/methodology/approach
The paper describes the preliminary system updates that were required to isolate the SBSS software from all internal and external system and user interfaces in preparation for the subsequent successful code roll effort. Once the legacy SBSS component was fully isolated, the SBSS software modernization objective was achieved via a “code roll” conversion of the SBSS software from legacy COBOL to Java code, and movement of the integrated logistics system-supply application from a proprietary information technology (IT) platform to an open IT operating environment.
Findings
The SBSS system modernization yielded immediate and significant IT operational cost reductions and provided an important foundation for achieving Air Force logistics system consolidation and cloud computing objectives going forward.
Originality/value
The SBSS modernization experience should be useful in assisting similar data system software modernization efforts.
Details
Keywords
Marisol S. Romero-Mancilla, Kenneth E. Hernandez-Ruiz and Diana L. Huerta-Muñoz
The purpose of this paper is to introduce a three-echelon multimodal transportation problem applied to a humanitarian logistic case study that occurred in Mexico.
Abstract
Purpose
The purpose of this paper is to introduce a three-echelon multimodal transportation problem applied to a humanitarian logistic case study that occurred in Mexico.
Design/methodology/approach
This study develops a methodology combining a transshipment problem and an adaptation of the multidepot heterogeneous fleet vehicle routing problem to construct a mathematical model that incorporates the use of land-based vehicles and drones. The model was applied to the case study of the Earthquake on September 19, 2017, in Mexico, using the Gurobi optimization solver.
Findings
The results ratified the relevance of the study, showing an inverse relationship between transportation costs and delivery time; on the flip side, the model performed in a shorter CPU time with medium and small instances than with large instances.
Research limitations/implications
While the size of the instances limits the use of the model for big-scale problems, this approach manages to provide a good representation of a transportation network during a natural disaster using drones in the last-mile deliveries.
Originality/value
The present study contributes to a model that combines a vehicle routing problem with transshipment, multiple depots and a heterogeneous fleet including land-based vehicles and drones. There are multiple models present in the literature for these types of problems that incorporate the use of these transportation modes; however, to the best of the authors’ knowledge, there are still no proposals similar to this study.
Details
Keywords
Ryan Trudelle, Edward D. White, Dan Ritschel, Clay Koschnick and Brandon Lucas
The introduction of “should cost” in 2011 required all Major Defense Acquisition Programs (MDAP) to create efficiencies and improvements to reduce a program’s “will-cost”…
Abstract
Purpose
The introduction of “should cost” in 2011 required all Major Defense Acquisition Programs (MDAP) to create efficiencies and improvements to reduce a program’s “will-cost” estimate. Realistic “will-cost” estimates are a necessary condition for the “should cost” analysis to be effectively implemented. Owing to the inherent difficulties in establishing a program’s will-cost estimate, this paper aims to propose a new model to infuse realism into this estimate.
Design/methodology/approach
Using historical data from 73 Departments of Defense programs as recorded in the selected acquisition reports (SARs), the analysis uses mixed stepwise regression to predict a program’s cost from Milestone B (MS B) to initial operational capability (IOC).
Findings
The presented model explains 83 per cent of the variation in the program acquisition cost. Significant predictor variables include: projected duration (months from MS B to IOC); the amount of research development test and evaluation (RDT&E) funding spent at the start of MS B; whether the program is considered a fixed-wing aircraft; whether a program is considered an electronic system program; whether a program is considered ACAT I at MS B; and the program size relative to the total program’s projected acquisition costs at MS B.
Originality/value
The model supports the “will-cost and should-cost” requirement levied in 2011 by providing an objective and defensible cost for what a program should actually cost based on what has been achieved in the past. A quality will-cost estimate provides a starting point for program managers to examine processes and find efficiencies that lead to reduced program costs.
Details
Keywords
Christopher R. Reutzel, Carrie A. Belsito and Jamie D. Collins
The purpose of this paper is to add to the small but growing body of research examining the influence of founder gender on new venture access to venture development programs.
Abstract
Purpose
The purpose of this paper is to add to the small but growing body of research examining the influence of founder gender on new venture access to venture development programs.
Design/methodology/approach
Hypotheses were tested utilizing a sample of 482 nascent technology ventures which applied for admittance into a venture development organization headquartered in the southern region of the United States from March 2004 through February 2016.
Findings
Findings suggest that female-founded applicant ventures experience a higher likelihood of acceptance into venture development programs than male-founded applicant ventures. Results further suggest that social attention to gender equality reduces this effect for female-founded applicant ventures. Findings extend the understanding of the gendered nature of high-technology venturing and venture development organizations.
Research limitations/implications
The findings of this study may not generalize to new ventures operating in other contexts (e.g., non-U.S., low-tech, and other venture development programs). Additionally, this study's design and data limitations do not allow for the establishment of causality or address founder motivations to apply for acceptance into venture development programs.
Originality/value
This study adds to empirical findings regarding the influence of founder gender on new venture acceptance into venture development programs by developing and testing competing hypotheses. This study also extends extant research by examining the moderating effect of social attention to gender equality on the hypothesized relationships between founder gender and acceptance into venture development programs.
Details