search form

search form
Independent Verification and Validation Facility (IV&V) 
Date of Last update : 2014.03.29 Rivision Request
Photos
Location
NASA IV&V Program, 100 University Drive, Fairmont, WV 26554 USA
Homepage
http://www.nasa.gov/centers/ivv/home/index.html
Coordinating Country
United States
Hosting Organisations
Independent Verification and Validation Facility (IV&V)
Contact Person
Dr. Gregory D. Blaney
RI Category
Software Service Facilities
Keywords
software, program development, safety, space shuttle
Description
NASA’s Independent Verification and Validation (IV&V) Facility is home of NASA’s IV&V Program. Located in the heart of West Virginia?s emerging technology sector, NASA?s IV&V Program was established in 1993 as part of an Agency-wide strategy to provide the highest achievable levels of safety and cost-effectiveness for mission critical software. NASA?s IV&V Program was founded under the NASA Office of Safety and Mission Assurance (OSMA) as a direct result of recommendations made by the National Research Council (NRC) and the Report of the Presidential Commission on the Space Shuttle Challenger Accident.

Since then, NASA?s IV&V Program has experienced continual growth in personnel, projects, capabilities, and accomplishments. NASA IV&V efforts have contributed to NASA?s improved safety record since the program?s inception. Today, independent verification and validation is an Agency-level function, delegated from OSMA to Goddard Space Flight Center (GSFC) and managed by NASA IV&V The program?s primary business, software IV&V, is sponsored by OSMA as a software assurance technology. Operating under GSFC, NASA IV&V is Code 180 (Center Director?s direct report).

NASA?s IV&V Program houses approximately 270 employees and leverages the expertise of in-house partners and contractors.
Application Area
Vision
Be a world leader in systems and software engineering that enables our customers’ success.

Mission
To provide our customers assurance that their safety and mission-critical software will operate reliably and safely and to advance the systems and software engineering disciplines. In doing so, we work to standards of excellence, provide professional engineers, provide national and global leadership, focus on customer satisfaction, and adhere to and demonstrate our core set of values: safety, integrity, respect, teamwork, balance, innovation, and excellence.
Specifications

IV&V Services

NASA's IV&V Program strives to improve software safety, reliability, and quality of NASA programs and missions through effective applications of systems and software IV&V methods, practices, and techniques. Employing an ISO 9001:2008 certified process. NASA's IV&V Program applies system and software engineering best practices to evaluate the correctness and quality of critical and complex software systems throughout the System Development Life Cycle (SDLC).



When applying systems and software IV&V, NASA IV&V seeks to answer the following questions:

1. Will the system's software do what it is supposed to do?

2. Will the system's software not do what it is not supposed to do?

3. Will the system's software respond as expected under adverse conditions?



The NASA IV&V Program's analytical approaches enable efficient, cost-effective IV&V service through the usage of broad-based, eclectic expertise, adaptive software engineering best practices, and tools that are available to the IV&V analysts. The analytical paradigm utilized by NASA'd IV&V Program requires a multi-disciplinary team, and a qualitative software risk and criticality assessment capability coupled with an extensive multiphase V&V analytical process.



Software IV&V has been demonstrated to be an effective technique on large, complex software systems to increase the probability of software being delivered that meets requirements and is safe, within cost, and within schedule. When performed in parallel with the SDLC, software IV&V provides for the early detection and identification of risk elements. NASA's IV&V Program is then able to take action to mitigate these risks early in the SDLC.