The Knowledge Application and Utilization Framework Applied to Defense COTS: A Research Synthesis for Outsourced Innovation

Purpose -- Militaries of developing nations face increasing budget pressures, high operations tempo, a blitzing pace of technology, and adversaries that often meet or beat government capabilities using commercial off-the-shelf (COTS) technologies. The adoption of COTS products into defense acquisitions has been offered to help meet these challenges by essentially outsourcing new product development and innovation. This research summarizes extant research to develop a framework for managing the innovative and knowledge flows. Design/Methodology/Approach – A literature review of 62 sources was conducted with the objectives of identifying antecedents (barriers and facilitators) and consequences of COTS adoption. Findings – The DoD COTS literature predominantly consists of industry case studies, and there’s a strong need for further academically rigorous study. Extant rigorous research implicates the importance of the role of knowledge management to government innovative thinking that relies heavily on commercial suppliers. Research Limitations/Implications – Extant academically rigorous studies tend to depend on measures derived from work in information systems research, relying on user satisfaction as the outcome. Our findings indicate that user satisfaction has no relationship to COTS success; technically complex governmental purchases may be too distant from users or may have socio-economic goals that supersede user satisfaction. The knowledge acquisition and utilization framework worked well to explain the innovative process in COTS. Practical Implications – Where past research in the commercial context found technological knowledge to outweigh market knowledge in terms of importance, our research found the opposite. Managers either in government or marketing to government should be aware of the importance of market knowledge for defense COTS innovation, especially for commercial companies that work as system integrators. Originality/Value – From the literature emerged a framework of COTS product usage and a scale to measure COTS product appropriateness that should help to guide COTS product adoption decisions and to help manage COTS product implementations ex post

Software Acquisition Improvement in the Aeronautical Systems Center

In the past 20 years, over 150 recommendations have been made to improve software systems development by organizations such as the Defense Science Board, National Research Council and the U.S. General Accountability Office. It has been discovered that many of these recommendation have remained unimplemented. This research had the purpose of confirming the application of these previous recommendations to improve software acquisition in the Aeronautical Systems Center. This was accomplished through interviews with 20 software practitioners in the acquisition community and the review of relevant literature. Through the analysis of the interviews and literature, this research was able to confirm that many of the recommendations have been applied in programs throughout ASC

Selection of third party software in Off-The-Shelf-based software development: an interview study with industrial practitioners

The success of software development using third party components highly depends on the ability to select a suitable component for the intended application. The evidence shows that there is limited knowledge about current industrial OTS selection practices. As a result, there is often a gap between theory and practice, and the proposed methods for supporting selection are rarely adopted in the industrial practice. This paper's goal is to investigate the actual industrial practice of component selection in order to provide an initial empirical basis that allows the reconciliation of research and industrial endeavors. The study consisted of semi-structured interviews with 23 employees from 20 different software-intensive companies that mostly develop web information system applications. It provides qualitative information that help to further understand these practices, and emphasize some aspects that have been overlooked by researchers. For instance, although the literature claims that component repositories are important for locating reusable components; these are hardly used in industrial practice. Instead, other resources that have not received considerable attention are used with this aim. Practices and potential market niches for software-intensive companies have been also identified. The results are valuable from both the research and the industrial perspectives as they provide a basis for formulating well-substantiated hypotheses and more effective improvement strategies.Peer ReviewedPostprint (author's final draft

A Systematic Mapping Study on Off-The-Shelf-based Software Acquisition

Acquiring software from external suppliers and developing less software in-house can help software-developing organizations improve operational efficiency by reducing costs, time and reusing current technologies. Software projects increasingly use Off-The-Shelf (OTS) products. From the acquirer perspective, there is a need to understand in more detail OTS-based software acquisition processes, because they are different to and less well-understood than those for the acquisition of custom software. In this paper we have undertaken a systematic mapping study on OTS-based software acquisition. The study compares and contrasts OTS-based software acquisition and non-OTS-based software acquisition, and identifies factors influencing decision making in OTS-based software acquisition. We find that the main difference is that there is a relationship between determining the software requirements and OTS selection in OTS-based software acquisition. For commercial OTS software, the major factors are functionality and quality of the software, but for open-source OTS software, cost was the most important factor

A Hierarchical Core Reference Ontology for New Technology Insertion Design in Long Life Cycle, Complex Mission Critical Systems

Organizations, including government, commercial and others, face numerous challenges in maintaining and upgrading long life-cycle, complex, mission critical systems. Maintaining and upgrading these systems requires the insertion and integration of new technology to avoid obsolescence of hardware software, and human skills, to improve performance, to maintain and improve security, and to extend useful life. This is particularly true of information technology (IT) intensive systems. The lack of a coherent body of knowledge to organize new technology insertion theory and practice is a significant contributor to this difficulty. This research organized the existing design, technology road mapping, obsolescence, and sustainability literature into an ontology of theory and application as the foundation for a technology design and technology insertion design hierarchical core reference ontology and laid the foundation for body of knowledge that better integrates the new technology insertion problem into the technology design architecture

Standards and Specifications for Ground Processing of Space Vehicles: From an Aviation-Based Shuttle Project to Global Application

Proprietary or unique designs and operations are expected early in any industry's development, and often provide a competitive early market advantage. However, there comes a time when a product or industry requires standardization for the whole industry to advance...or survive. For the space industry, that time has come. Here, we will focus on standardization of ground processing for space vehicles and their ground systems. With the retirement of the Space Shuttle, and emergence of a new global space race, affordability and sustainability are more important now than ever. The growing commercialization of the space industry and current global economic environment are driving greater need for efficiencies to save time and money. More RLV's (Reusable Launch Vehicles) are being developed for the gains of reusability not achievable with traditional ELV's (Expendable Launch Vehicles). More crew/passenger vehicles are also being developed. All of this calls for more attention needed for ground processing-repeatedly before launch and after landing/recovery. RLV's should provide more efficiencies than ELV's, as long as MRO (Maintenance, Repair, and Overhaul) is well-planned-even for the unplanned problems. NASA's Space Shuttle is a primary example of an RLV which was supposed to thrive on reusability savings with efficient ground operations, but lessons learned show that costs were (and still are) much greater than expected. International standards and specifications can provide the commonality needed to simplify design and manufacturing as well as to improve safety, quality, maintenance, and operability. There are standards organizations engaged in the space industry, but ground processing is one of the areas least addressed. Challenges are encountered due to various factors often not considered during development. Multiple vehicle elements, sites, customers, and contractors pose various functional and integration difficulties. Resulting technical publication structures and methods are incongruent. Some processing products are still done on paper, some electronic, and many being converted in between. Business systems then are not fully compatible, and paper as well as electronic conversions are time-consuming and costly. NASA and its Shuttle contractors setup rules and systems to handle what has produced over 130 RLV launches, but they have had many challenges. Attempts have been made to apply aviation industry specifications to make the Shuttle more efficient with its ground processing. One efficiency project example was to make a Shuttle Maintenance Manual (SMM) based on the commercial ATA (Air Transport Association of America) Spec 100 for technical publications. This industry standard, along with others, has been a foundation for efficient global MRO of commercial airlines for years. A modified version was also made for some military aircraft. The SMM project found many similarities in Spec 100 which apply to the Shuttle, and room for expansion for space systems/structures not in aircraft. The SMM project team met with the ATA and representatives from NASA's X-33 and X-34 programs to discuss collaboration on a national space standard based on Spec 100. A pilot project was enabled for a subset of Shuttle systems. Full implementation was not yet achieved, X-33 and X-34 were cancelled, and the Shuttles were then designated for retirement. Nonetheless, we can learn from this project how to expand this concept to all space vehicle products. Since then, ATA has joined with ASD (AeroSpace and Defence Industries Association of Europe) and AIA (Aerospace Industries Association) to form a much-enhanced and expanded international specification: Sl000D, International Specification for Technical Publications. It includes air, land, and sea vehicles, missiles, support equipment, ordnance, and communications. It is used by a growing number of countries for commercial and government products. Its modular design is supported by a Common Source Dabase (CSDB), and COTS (commercial off-the-shelf) software is available for production of IETP's (Interactive Electronic Technical Publications). A few space industry products in Europe have begun to apply Sl000D already. Also, there are other related standards/specifications which have global implications. We have an opportunity to adapt Sl000D and possibly other standards for use with space vehicles and ground systems. Sl000D has plenty of flexibility to apply to any product needed. To successfully grow the viability of the space industry, all members, commercial and government, will need to engage cooperatively in developing and applying standards to move toward interoperability. If we leverage and combine the best existing space standards and specifications, develop new ones to address known gaps, and adapt the best applicable features from other industries, we can establish an infrastructure to not only accelerate current development, but also build longevity for a more cohesive international space community

Generalization of an integrated cost model and extensions to COTS, PLE and TTM

There have been existing software reuse cost models related to estimating costs of software reuse, for example, COCOMO II, COCOTS, and so on. Chmiel\u27s model [Chmiel 2000] is a generalization of these cost models. This model is different from others in that the decisions are composed of four levels and treats reuse projects from a point of view of long term run. Each level corresponds one engineering cycle. Each level is a decision making process based on calculation of NPV, ROI, and other economic indices. Reuse investment decisions are made on different levels from the corporate to the programming.;Chmiel\u27s model doesn\u27t cover Commercial-Off-The-Shelf (COTS), Product Line Engineering (PLE) and benefits due to shortened Time-To-Market (TTM) and can only deal with internal traffic since the model assumes all of the reusable components are built from scratch in house. For example, Extra efforts caused by the use of COTS, assessment, tailoring, glue code and COTS volatility, are not covered in this model. And this model doesn\u27t treat the benefits of TTM, for example, business performance.;By extending Chmiel\u27s model, the new model is applied to CBSE (Component-Based Software Engineering), COTS reuse systems and PLE. In addition, attempts of quantifying benefits of shortened TTM are made within this study and a TTM submodel is developed to cover this issue.;This study also addresses the issue to analyze and optimize corporate Return On Investment (ROI). The rational is that optimizing (maximizing) the corporate ROI under the condition that all other ROI\u27s are positive. By designing an algorithm and applying it to the data, this study discovers the method how to make the maximized value of corporate ROI.;And this model is supported through a tool based on the model rationale. Users to this tool are corporate management and development engineers. The supporting tool has user-friendly interface and allows users to input values of related parameters. A detailed report is produced, which is composed of details about costs and benefits, final Net Present Value (NPV) and ROI of each cycle

Theater Battle Management Core System Systems Engineering Case Study

The Theater Battle Management Core System (TBMCS) is an integrated air command and control (C2) system that performs standardized, secure, automated air battle planning and execution management for Air Force, multi-service, and allied commanders in theaters of operation worldwide. TBMCS provides the means to plan, direct, and control all theater air operations and to coordinate with land, maritime, and special operations elements. It is deployed at C2 nodes at national, force and wing/unit-level elements. TBMCS operates in support of planners and decision makers at, and below, the level of Joint Force Air Component Commander. The system is modular and scalable for air, land, or sea transport and the deployed configurations can be tailored to meet a particular contingency

Metrics and Models for Cost and Quality of Component-Based Software

Quality and risk concerns currently limit the application of commercial off-the-shelf (COTS) software components to non-critical applications. Software metrics can quantify factors contributing to the overall quality of a component-based system, and models for tradeoffs between cost and various aspects of quality can guide quality and risk management by identifying and eliminating sources of risk. This paper discusses metrics and models that can be used to alleviate quality concerns for COTS-based systems, enabling the use of COTS components in a broader range of applications