The Rapid Integration and Test Environment: A Process for Achieving Software Test Acceptance
Abstract
The Rapid Integration and Test Environment (RITE) initiative, implemented by the Program Executive Office, Command, Control, Communications, Computers and Intelligence, Command and Control Program Office (PMW-150), was born of necessity. Existing processes for requirements definition and management, as well as those for software development, did not consistently deliver high-quality Navy command and control (C2) systems on time and within budget. Navy C2 software programs experienced an increase in software defects that were not discovered until the completion of development activities and, because of the pressure to deploy software on schedule, product releases were distributed with defects. These defects were then repaired post delivery at significant cost. This situation was untenable and required new procedures and processes to solve the programmatic and technical challenges while operating with reduced budgets. This paper introduces a new life cycle model for Navy C2 software that places increased emphasis on early and frequent software testing, as well as on necessary software engineering practices at the source code level. RITE is a more structured approach to software development, taking full advantage of technology advances and open source models to automate processes and shorten development cycles''thus increasing the maintainability of the software baselines. The initiative also clarifies software delivery requirements, adding additional engineering rigor to deliverables and reducing opportunity for misunderstanding between customers and developers. Its goal is to reduce overall cost, streamline delivery of quality C2 software, and, ultimately, resource focus toward the early stages of the life cycle, where the return on investment is maximized. RITE provides comprehensive oversight of software development from initial product design to customer acceptance.
Description
Proceedings Paper (for Acquisition Research Program)
Rights
This publication is a work of the U.S. Government as defined in Title 17, United States Code, Section 101. Copyright protection is not available for this work in the United States.NPS Report Number
NPS-AM-10-044Related items
Showing items related by title, author, creator and subject.
-
Dependable Software through a Holistic Framework of Tool Interoperability and Artifact Dependency
Luqi; Puett, J. (Monterey, California. Naval Postgraduate School, 2002-07); NPS-SW-02-006Objectives. The goal of this research is to develop a holistic framework for engineering dependable computing and communications software. The framework establishes collaborative mechanisms by which existing software ... -
Total Ownership Cost—System Software Impacts
Naegle, Brad R. (Monterey, California. Naval Postgraduate School, 2017-04); NPS-CE-17-042Department of Defense (DoD) software-intensive systems and the software content in other systems will continue to grow and may dominate total ownership costs (TOC) in the future. These costs are exacerbated by the fact ... -
Total ownership cost - system software impacts
Naegle, Brad R. (Monterey, California. Naval Postgraduate School, 2017-04-19); NPS-CE-17-042Department of Defense (DoD) software-intensive systems and the software content in other systems will continue to grow and may dominate total ownership costs (TOC) in the future. These costs are exacerbated by the fact ...