See this document in CiteSeerX!

COTS Software Failures: Can Anything be Done?  (Make Corrections)  
Jeffrey Voas, Jeffery Payne



  Home/Search   Context   Related

 
View or download:
rstcorp.com/pub/papers/asset98.ps
Cached:  PS.gz  PS  PDF   Image  Update  Help

From:  rstcorp.com/papers/chrono1998 (more)
(Enter author homepages)

Rate this article: (best)
  Comment on this article  
(Enter summary)

Abstract: Software development is quickly becoming more of a process of acquiring software components and composing them than building systems from scratch. From a time-to-market perspective, this is ideal, but from a quality perspective, this is worrisome. This paper addresses steps that component integrators should follow before relying on someone else's software libraries and components. Keywords COTS, fault tolerance, testing, wrappers, fault injection 1 Introduction The adage, "if you want... (Update)

Similar documents (at the sentence level):
28.3%:   Mitigating the Potential for Damage Caused by COTS and.. - Jeffrey Voas Reliable (1998)   (Correct)

Active bibliography (related documents):   More   All
0.6:   Defensive Approaches to Testing Systems that Contain COTS and.. - Jeffrey Voas (1998)   (Correct)
0.5:   Jeffrey Voas Reliable Software Technologies Suite 250, 21515.. - Rp Com   (Correct)
0.3:   COTS Software Evaluation Techniques - Dean, al.   (Correct)

Similar documents based on text:   More   All
0.4:   Why COTS Software Increases Security Risks - Mcgraw (1999)   (Correct)
0.3:   Testing the Robustness of Windows NT Software - Ghosh, Schmid, Shah (1998)   (Correct)
0.3:   Wrapping Windows NT Software for Robustness - Ghosh, Schmid, Hill (1999)   (Correct)

BibTeX entry:   (Update)

@misc{ voas-cots,
  author = "Jeffrey Voas and Jeffery Payne",
  title = "COTS Software Failures: Can Anything be Done?",
  url = "citeseer.ist.psu.edu/7769.html" }
Citations (may not include all citations):
36   Software Reliability Measurement Prediction Application (context) - MUSA, IANNINO et al. - 1987
8   Ariane 5 flight 501 failure: Report of the inquiry board (context) - LIONS - 1996
5   Forget the Huddled Masses: Send Nerds (context) - BAKER, MCWILLIAMS et al. - 1997
5   A Crystal Ball for Software Liability - VOAS, MCGRAW et al. - 1997
3   ON UNIFORM LAWS. Uniform Commercial Code Article 2B (context) - LAW, NATIONAL et al. - 1997
3   Error Propagation Analysis for COTS Systems (context) - VOAS - 1997

Documents on the same site (http://rstcorp.com/papers/chrono-1998.html):   More
Agent Trustworthiness - Kassab, Voas (1998)   (Correct)
Automated Software Test Data Generation for Complex Programs - Michael, McGraw (1998)   (Correct)
An Automated Approach for Identifying Potential.. - Ghosh, O'Connor, McGraw (1998)   (Correct)

Online articles have much greater impact   More about CiteSeer.IST   Add search form to your site   Submit documents   Feedback  

CiteSeer.IST - Copyright Penn State and NEC