This, if anything, is a sorely mistaken portrayal of formal methods and analyses. There may be any number of reasons not to discuss formal methods in the course, but they not being applicable for evolving software isn't one. I hope that the authors' better-informed colleagues at UC Berkeley will correct them soon enough.
Friday, February 10, 2012
An unfair indictment
The first chapter of the textbook, Engineering Long-Lasting Software: An Agile Approach Using SaaS and Cloud Computing (Alpha Edition), for the Software Engineering for Software as a Service free-class offered by Armando Fox and David Patterson in Spring 2012, has this to say about formal methods:
This, if anything, is a sorely mistaken portrayal of formal methods and analyses. There may be any number of reasons not to discuss formal methods in the course, but they not being applicable for evolving software isn't one. I hope that the authors' better-informed colleagues at UC Berkeley will correct them soon enough.
This, if anything, is a sorely mistaken portrayal of formal methods and analyses. There may be any number of reasons not to discuss formal methods in the course, but they not being applicable for evolving software isn't one. I hope that the authors' better-informed colleagues at UC Berkeley will correct them soon enough.
Subscribe to:
Posts (Atom)