In her February 2020 column ("Are You Sure Your Software Will Not Kill Anyone?"), Nancy Leveson says the solution to software safety is not "building a software architecture and generating the requirements later." Reading this, we were surprised that anyone would propose such an approach, or that Leveson would find it necessary to argue against it. We were even more surprised to see that Leveson attributes the proposal to a National Academies report that we edited.1
Perhaps Leveson had a different report in mind. Our report actually substantiates the very arguments she makes in her column, identifying the same misconceptions that she notes, along with others—and provides citations for the earlier origins of these supposedly new arguments.
No entries found
Log in to Read the Full Article
Sign in using your ACM Web Account username and password to access premium content if you are an ACM member, Communications subscriber or Digital Library subscriber.
Please select one of the options below for access to premium content and features.
Create a Web Account
If you are already an ACM member, Communications subscriber, or Digital Library subscriber, please set up a web account to access premium content on this site.
Join the ACM
Become a member to take full advantage of ACM's outstanding computing information resources, networking opportunities, and other benefits.
Subscribe to Communications of the ACM Magazine
Get full access to 50+ years of CACM content and receive the print version of the magazine monthly.
Purchase the Article
Non-members can purchase this article or a copy of the magazine in which it appears.