Viewing software from an engineering perspective, in a hierarchical manner, enables it be be classified according to function, origin, degree of automation, and degree of customization. In general, software is too customized, causing far-reaching maintenance and reliability problems. Add to that sloppy, undisciplined coding practices and you have the makings of poor quality, 'hazardous' software. These hazards can be located by examining user complaints, development conditions, and how software requirements are specified. An analogy between first aid practices and fixing software problems is given to help others understand software safety and security. (Publisher abstract)