Abstract

Should software be sold “as is”, totally guaranteed, or something else? This paper suggests that “informed consent”, used extensively in medical ethics, is an appropriate way to envision the buyer/developer relationship when software is sold. We review why the technical difficulties preclude delivering perfect software, but allow statistical predictions about reliability. Then we borrow principles refined by medical ethics and apply them to computer professionals.