Talk:Formal specification
To-do list for Formal specification: edit · history · watch · refresh · Updated 2011-06-22
 | 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?
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)
- 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)
Content Disclaimer
Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.
- The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
- There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
- It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
- Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
- Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.