Talk:Software safety

Article source

Much (all?) of this article appears to have been copied from http://www.monmouth.army.mil/cecom/safety/sys_service/software_handbook.htm. This source might be public domain if it is a work of the US government (as opposed to simply being published/hosted on a government websitee.Sagsaw 21:11, 7 January 2007 (UTC)

The manual on second page states it was funded and developed - and lists the United States Navy, Army and Air Force. most names listed are DoD Civilian employees. Those not DoD Civilian employees probably worked on this as contractors to the DoD. Wfoj2 (talk)

False Statement about history of safety importance.

"In the past, industry in general considered increased productivity as the most important aspect of Software Engineering. Little consideration was given concerning the reliability or safety of the software product."

This is not true and has never been true. Embedded software systems have always had to take into account system and MCU resource failures. That's is why there are FMEAs both systems and software, ram checks, rom checks, illegal opcode checks, dual core microprocessers, etc. which have been around for 2 decades. I would guess that the author of this statement had a PC application background. However, that doesn't make his/her viewpoint true in general. —Preceding unsigned comment added by 206.19.210.7 (talk) 13:19, 17 July 2008 (UTC)

Broken link

I'm sorry to notify that the link to "http://www.monmouth.army.mil/cecom/safety/sys_service/" is broken