(redirected from N-version programming)
Also found in: Wikipedia.
NVPName-Value Pair
NVPNew Venture Partners (various locations)
NVPNausea and Vomiting of Pregnancy
NVPNetwork Voice Protocol
NVPNational Volunteer Program (various organizations)
NVPName Value Pair
NVPNational Vice President
NVPNon-Violence Project (various locations)
NVPNominal Velocity of Propagation
NVPNew Venture Performance (various organizations)
NVPN-Version Programming (multiple functionally equivalent program versions)
NVPN-Vinyl Pyrrolidone (synthetic liquid)
NVPNational Variety Performance (agricultural testing conference)
NVPNuance Voice Platform (software)
NVPNew Ventures Program (various organizations)
NVPNew Voters Project (non-partisan student group)
NVPNevada Power Company
NVPNon-Violent Peace
NVPNorth Valley Playhouse (Phoenix, AZ)
NVPNationwide Volume Program (Sprint PCS)
NVPNetwork Video Products (Abbotsford, Victoria, Australia)
NVPNew Vision Productions (various locations)
NVPNick Video Pick
NVPNeurological Visual Profiling
NVPNet Value Percentage
NVPNear-Vertical Propagation
NVPNetwork Video Processor
NVPNot Very Pretty
NVPNetwork Verification Point
NVPNominal Vapor Pressure
NVPNo Volt Protection
NVPNominal Venous Pressure
NVPNinja vs Penguin (blog)
NVPNinja versus Pirate
References in periodicals archive ?
Furthermore, the various panaceas proposed in this area--structured programming, high-level languages, formal methods, n-version programming, code walk-throughs, and others--have not succeeded.
N-version programming is the notion of having different programs written independently from the same specification, and then executing them in parallel, with conflicts resolved by majority voting.
Another methodology for increased reliability is N-version programming [2].
N-version programming uses a single team and then N teams during design and coding.
N remains variable in calculating team-week costs for N-Fold inspection and for N-version programming.
N-version programming and dual development may offer increased reliability which cannot be captured by our model, since we are interested only in the detection of URD faults.
The number of faults found by the N-version programming is taken by summing the average number of faults found by a single team inspection, the average number of faults found by a single team requirement specification, and the average number of faults found by N teams during design.
The N-version programming method is effective in providing reliable designs and implementations, but its success hinges on the quality of the formal specification and a reliable interpretation of the URD.