Abstract Certification is simply a process that validates conformance to an expectation or standard. Demonstrating that software was produced in a particular manner is probably the easiest type of certification to offer. (See .) Software standards exist that define how software is to be developed in order to provide increased confidence in the quality of the software, particularly in government regulated industries (medical, avionics, nuclear, manufacturing control). The problem, however, is that most of these standards define processes that must be employed during development and testing without addressing how the software will behave or interoperate with its environment. Demonstrating that the software will behave in a certain manner or interoperate in a certain way is far more difficult than demonstrating that the software was developed and tested in a particular way. The reason for this is because software is non‐physical, thus making quality difficult to assess, measure, and evaluate. This article includes information on the state of the practice today, the benefits of knowing what process a software developer/publisher uses, and the certifying of the software itself.