Limited software warranties

Because there are different types of software (e.g., language, application, target environment, etc.), different software certification methodologies are needed. Software process improvement schemes have not taken this approach and have therefore suffered in widespread adoption as a result. Their "one approach fits all" perspective is one reason why we are now seeing more customized process improvement schemes being created (e.g., CMM-SSE and the Common Criteria are recent "newcomers" that address developing software with security requirements) and even the call to certify software professionals. This paper presents a framework for customizing certification methodologies ac-cording to: (1) the specific needs of the organization requesting assurances about the software's integrity, and (2) the pecularities of that type of software. Each methodology must mirror the nuances of the type of software it was designed for. For example, certifying that a desktop plug-in will behave appropriately requires a different set of assessment technologies than the set of technologies needed to certify that an aircraft control system will behave appropriately. The goal of creating a certification frame-work is to provide a more systematic way to create and compare software certification methodologies which today does not exist. And from there, we will be able to offer limited software warranties