Talk:Formal specification

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
???	This article has not yet received a rating on the project's importance scale.
	This article is supported by WikiProject Software.

Merge with formal methods?[edit]

Shouldn't this article be merged with formal methods? Also, specification language covers a very similar topic. --Tillmo (talk) 22:03, 7 December 2007 (UTC)[reply]

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)[reply]

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)

Fairflow (talk) 20:59, 26 January 2014 (UTC)[reply]