Talk:Formal specification
Latest comment: 10 years ago by Fairflow in topic Merge with formal methods?
 | This  level-5 vital article is rated Start-class on Wikipedia's content assessment scale.It is of interest to the following WikiProjects: | |||||||||||||
| ||||||||||||||
|
Merge with formal methods?
editShouldn't this article be merged with formal methods? Also, specification language covers a very similar topic. --Tillmo (talk) 22:03, 7 December 2007 (UTC)
- No. Formal Methods is a specific development technology using formal proofs that suffers because computers (and software) do not conform to Peano's 7th axiom. I do agree that this article should be replaced with "Software Design Specification." Where a Software Requirements Specification defines what problem needs to be solved with software, including constraints, a Software Design Specification describes, in detail, how that problem will be solved. Softtest123 (talk) 02:59, 15 May 2012 (UTC)
- Perhaps. Formal Methods is not a specific development technology using formal proofs (and Peano_axioms is a very odd reference to cite in this context). Do not replace with "Software Design Specification". A formal specification does not have to relate to a software design, but can also describe hardware, for example Santosh N. Varanasi, Kenneth S. Stevens, Graham Birtwistle (2010). "Concurrency Reduction of Untimed Latch Protocols - Theory and Practice". Symposium on Asynchronous Circuits and Systems. pp. 26–37. doi:10.1109/ASYNC.2010.13.
{{cite book}}:|access-date=requires|url=(help); Check date values in:|accessdate=(help)CS1 maint: multiple names: authors list (link)