The cost of COTS

Hall, Jon Maddog; Naff, R.

doi:10.1109/62.942215

Cited by 14 publications

(7 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…By definition, nonrecurring costs occur one time during the lifecycle of a system, and typically they are highest at the beginning of a program. Hence, by incorporating the OTSO [Hall and Naff, 2000]. A contractor has a greater probability of being awarded a Low Rate Initial Production (LRIP) contract for a given system when cost and budget are low in the development phase of the system.…”

Section: Otso Benefitsmentioning

confidence: 99%

SysML modeling of off‐the‐shelf‐option acquisition for risk mitigation in military programs

Constantine

Solak²

2009

Systems Engineering

View full text Add to dashboard Cite

Off-the-Shelf software, hardware, and subsystem assemblies have been accepted by system engineers, project managers, designers, and, most importantly, the customer as an essential ingredient to the successful and rapid deployment of deliverable military systems. The Department of Defense (DoD) acquisition community almost always expects the prime contractor to incorporate the Off-The-Shelf-Option (OTSO) within their system design, whether it is a military tank, software defined radio, or advance tactical fighter aircraft. Clearly, system engineers and program managers have an obligation to mitigate risks when using the OTSO in DoD programs. Part of risk mitigation means having in place predefined processes, methodologies, and models that revisit and evaluate risks throughout the lifecycle of the program or project. In this paper, we develop models and expand upon current methodologies that provide guidance, risk mitigation, analysis, and strategies to system engineers and program managers when implementing the OTSO in military systems. We present OTSO acquisition models using Object Management Group System Modeling Language (OMG SysML), which we refer to as SysML throughout the paper. Specifically, we utilize Use Cases, a State Diagram, a Requirements Diagram, and an Activity Diagram within the SysML language to model acquisition, sustainment, and risk mitigation phases of an OTSO. The purposes of the models are to illustrate how the processes are tightly coupled and to put forward a concept that "glues" the processes together. Additionally, the models demonstrate the interdependencies required among the various disciplines within an organization to successfully deploy and maintain a system utilizing an OTSO.

show abstract

Section: Otso Benefitsmentioning

confidence: 99%

SysML modeling of off‐the‐shelf‐option acquisition for risk mitigation in military programs

Constantine

Solak²

2009

Systems Engineering

View full text Add to dashboard Cite

show abstract

“…Issues related to testing [Hissam and Carney, 1999;Hissam, 1998], and maintaining [Carney, Hissam, and Plakosh, 2000;Hybertson, Ta, and Thomas, 1997;Vidger and Dean, 1998] COTS intensive systems have also been presented. From a project management perspective, an estimation model for the economic life-span of systems using COTS components is described in Abts [2000], the cost of using COTS components is addressed in Erdogmus and Vandergraaf [1997], Hall and Naff [2001]. Jensen [1997], and Voas [1998aVoas [ , 1998b, and an approach considering the risks associated with the use of COTS has been proposed in Ballurio, Scalzo, and Rose [2002].…”

Section: Related Workmentioning

confidence: 99%

Defining goals in a COTS‐aware requirements engineering approach

Chung

Cooper

2003

Systems Engineering

View full text Add to dashboard Cite

The goals of developing systems better, faster, and cheaper continue to drive software engineering practitioners and researchers to investigate software engineering methodologies. In requirements engineering, the focus has traditionally been on modeling the software engineering process and products for systems that are being built from scratch. As the size and complexity of systems continues to grow the use of commercial off the shelf (COTS) components is being viewed as a solution. Effective use of COTS components, however, requires a systematic approach that provides both a set of concepts for modeling the subject matter and a set of guidelines for using such concepts. In particular, the process needs to recognize and address the people oriented problems including the identification and resolution of conflicting goals, bridging the gaps between stated requirements and "approximately fitting" components while still satisfying the customer. In this paper, we present a goal and agent oriented requirements engineering process model that explicitly addresses the use of COTS components. More specifically, we present (part of) our model for a COTS-Aware Requirements Engineering (CARE) process and illustrate it using a Digital Library System (DLS).

show abstract

“…M ANY robotic, automotive, and aerospace systems rely on serial communication buses to integrate the multitude of distributed devices necessary for system operation [1]. As more commercial-off-the-shelf (COTS) electronics find their way into these applications, so do many COTS practices and protocols [2]. Two of the most prevalent COTS serial communication protocols, Inter-Integrated Circuit (I 2 C) and Serial Peripheral Interface (SPI), are inherently vulnerable to single-point failures capable of disabling entire branches of the distributed system [3].…”

Section: Introductionmentioning

confidence: 99%

On-Orbit Implementation of Discrete Isolation Schemes for Improved Reliability of Serial Communication Buses

Holliday

Manchester

Senesky

2022

IEEE Trans. Aerosp. Electron. Syst.

View full text Add to dashboard Cite

Serial communication buses are used in electronic systems to interconnect sensors and other devices, but two of the most widely used protocols, I 2 C and SPI, are vulnerable to bus-wide failures if even one device on the bus malfunctions. For aerospace applications demanding increasingly more distributed processing and sensing capability, the compounding risk to system reliability as device count scales becomes a limiting factor in mission scope, performance, and lifetime. We propose a simple external circuit to be added to each node on a communication bus that automatically isolates the node in the event of device failure. By automatically isolating failed devices, the integrity of the bus is preserved without requiring additional signals or processing overhead from the host controller. In this article, I 2 C and SPI isolation circuits are simulated, fabricated, and experimentally verified to be effective at preserving bus integrity in the event of peripheral device failure. Generalized reusable circuit blocks were designed and integrated into three spacecraft systems for the successful NASA V-R3x mission deployed in January 2021. The addition of serial bus isolation significantly improved system reliability for the V-R3x mission by eliminating singlepoint failure modes of the I 2 C and SPI buses interconnecting sensors and radios necessary for mission success. The developed protection schemes are a valuable tool for decoupling system reliability from serial bus device count and can readily be integrated into existing aerospace systems.

show abstract

The cost of COTS

Cited by 14 publications

References 0 publications

SysML modeling of off‐the‐shelf‐option acquisition for risk mitigation in military programs

SysML modeling of off‐the‐shelf‐option acquisition for risk mitigation in military programs

Defining goals in a COTS‐aware requirements engineering approach

On-Orbit Implementation of Discrete Isolation Schemes for Improved Reliability of Serial Communication Buses

Contact Info

Product

Resources

About