A. Hall, "Seven myths of formal methods," IEEE Software, vol. 7, no. 5, pp. 11 -- 19, 1990. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
First 50 documents Next 50
Composite Propositions: Toward Support for Formal.. - Mondragon, Gates, Roach (Correct)
....industry alone was 6 billion [RT02] In spite of the current best practice, significant and costly errors remain in production software. Techniques utilizing formal specification languages and based on sound mathematics have been successful at identifying subtle errors missed by other techniques [CW96, H90]. Common formal verification tools include theorem provers [RJ00] model checkers [H97] and runtime monitors [GR01, GM02, KV99, DG01] In theorem proving, a logic formula expressing a desired property is derived from axioms that describe system behavior. In model checking, a system is described ....
....enabling the use of the aforementioned tools as well as other formal methods such as automated analysis and code synthesis. While formal methods have been demonstrated to improve the dependability of programs, practitioners have not widely adopted them. The following reasons have been cited [I88, H90]: The use of formal methods requires a high level of mathematical sophistication and training. Tools supporting the use of formal methods are not mature enough for general use and have not been well integrated with widely used software development tools. Customers and clients have ....
A. Hall, Seven Myths of Formal Methods, IEEE Software, September 1990, pp. 11-19.
Proving the Value of Formal Methods - Holzmann (1994) (1 citation) (Correct)
....in this case meant that it could no longer prove unambiguously and quantitatively exactly how much better a formal method can be. Some more details on the project follow in section 2.3. 1. 2 Opponents Formal methods are often opposed by practitioners on purely pragmatic grounds, cf. also [Ha90] and [BoHi94] The following is from an opponent of formal methods, who shall remain anonymous: A formal design method is often overkill. Only a small portion of the errors found by an expensive formal design process would ultimately show up in practice. And similarly, quoted verbatim from a ....
J. A. Hall, Seven myths of formal methods . IEEE Software, 7(5):11, 19, Sept. 1990.
FOOM: A Diagrammatic Illustration of Object-Z Specifications - Wafula, Swatman (1995) (1 citation) (Correct)
....a formal concretisation process leading to provably correct code. This process is normally referred to as refinement within the specialist literature (see, for example, Morgan [12] More recently, formal specifications have come to be acknowledged for their contribution to problem understanding [9, 10, 2, 11], their precision offering potential for enhanced communication and evaluation of understanding. In this paper we use refinement in its more common sense of clarification or increasing relevance. Our preliminary research [13, 14, 15, 2] suggested that a socio organizational approach could be used ....
A. Hall. Seven myths of formal methods. IEEE Software 75(5) (1990) 11--19.
Software Evolution as the Key to Productivity - Nierstrasz (Correct)
....adequately captured) 4] Aside from certain well understood domains, the cost of formally specifying requirements is not only exorbitant, but the cost of proving the correctness of an implementation may be unacceptably high. Furthermore, although there are some well documented counter examples [11], formal specifications and proofs typically do not scale well to large systems, and are rarely robust in the face of evolutionary changes. This suggests that formal methods most likely have their place in ensuring the robustness and correctness of individual, functional software components, but ....
Anthony Hall. Seven myths of formal methods. IEEE Software, 7(5):11--19, Sept. 1990.
Formal Object-Oriented Method Sfoom - Swatman (Correct)
....considered to be a conformance centred approach to software development. They were presented as a basis for a formal concretisation process leading to provably correct code. More recently, formal specifications have come to be acknowledged for their contribution to problem understanding [H90, S92a, SS92a, W90], their precision offering potential for enhanced communication and evaluation of understanding. Our preliminary research [FSS93, S93, SFG92, SS92a] suggested that a socio organisational approach could be used beneficially in concert with object oriented formal specification techniques within the ....
Hall, A. (1990). Seven myths of formal methods. IEEE Software, 7(5), 11--19.
On Documenting the Requirements for Computer Programs Based.. - Kreyman, Parnas (Correct)
....such methods are not routinely used in industry. Even when formal methods are often used, they are used only to a limited extent and resisted by engineers and programmers. This situation is hardly surprising, both because there are many widely held misconceptions about the use of formal techniques [2] and because many of the methods are not practical. Below we will argue that it is possible, to obtain benefits from methods based on a relational model of software requirements. The principles of documentation and the software design process most applicable for our objectives are based on the ....
Hall, A., "Seven myths of formal methods", IEEE Software, 7(5), pp. 11-20, 1990.
A Pragmatic Approach to Formalizing Object-Oriented Modeling and.. - Jia (1997) (1 citation) (Correct)
.... The capability and feasibility of the approach presented here is fully demonstrated by a prototype tool Venus[9] 2 Pragmatic Obstacles The have been laudable efforts by the formal methods community to demystifying formal methods and to convince practitioners that formal methods are practical [3]. However, as the formal methods community zealously appeals to the practitioners, it fails to fully understand and address the practical concerns of practitioners. Since a reasonably solid foundation has been established for formal methods, it s time to focus more on the pragmatics of formal ....
A. Hall. Seven myths of formal methods. IEEE Software, 7(5):11--19, Sept. 1990.
Formal Methods and Mechanical Verification applied to.. - Vos, Swierstra, Prasetya (1996) (Correct)
....these accidents with the Therac 25 the reader is referred to [LT93] Formal methods, the term with which the variety of mathematical modelling techniques that are applicable to computer system design is meant, are often advocated as a way of increasing confidence in computer based systems. Many [BS92, BH95b, BS93b, BBL93, BH95a, BS93a, Bow93, But93, CGR93, CG92, GCR94, Hal90, Kem90, Nic91, RvH93, Rus94, WW93] believe that the use of formal methods currently offers the only intellectually defensible method for handling the software crisis which increasingly affects the world of embedded systems. In this report we shall mainly concentrate on safety critical software design. Formal methods can be applied ....
A. Hall. Seven myths of formal methods. IEEE Software, pages 11--19, September 1990.
JML Reference Manual - Leavens, Poll, Clifton, Cheon, Ruby, .. (2004) (5 citations) Self-citation (Hall) (Correct)
No context found.
Anthony Hall. Seven Myths of Formal Methods. IEEE Software, 7(5):11-19 (Sept. 1990).
JML Reference Manual - Draft Revision December Self-citation (Hall) (Correct)
No context found.
Anthony Hall. Seven Myths of Formal Methods. IEEE Software, 7(5):11-19 (Sept. 1990).
Challenges and Research Directions in Agent-Oriented Software.. - Zambonelli (2004) (2 citations) (Correct)
No context found.
A. Hall, "Seven myths of formal methods," IEEE Software, vol. 7, no. 5, pp. 11 -- 19, 1990.
Accepted paper in Integrated Design and Process Technology .. - Dorian Petit Vincent (2003) (Correct)
No context found.
Hall, A. (1990). Seven myths of formal methods. IEEE Software, 7(5).
How to Formalize It? Formalization Principles for.. - Hofstede, Proper (1998) (Correct)
No context found.
J.A. Hall. Seven Myths of Formal Methods. IEEE Software, pages 11--19, September 1990.
Teaching ASMs, Teaching with ASMs: Opportunities in.. - Huggins, Mayo, Wallace (Correct)
No context found.
J.A. Hall. Seven myths of formal methods. IEEE Software, 7(5):11-19, 1990.
Benefits and Problems of Formal Methods - Gogolla (2004) (Correct)
No context found.
J. Anthony Hall. Seven Myths of Formal Methods. IEEE Software, 7(5):11{ 19, September 1990. 14
Unknown - Ning Iterative Programs (Correct)
No context found.
A. Hall. Seven Myths of Formal Methods. IEEE Software, September 1990.
The Use of Industrial-Strength Formal Methods - Bowen, Hinchey (1997) (1 citation) (Correct)
No context found.
J. A. Hall. Seven myths of formal methods. IEEE Software, 7(5):11--19, September 1990.
Towards an FCA based tool for visualising Formal Specifications - Tilley (2003) (Correct)
No context found.
A. Hall. Seven myths of formal methods. IEEE Software, pages 11--19, September 1990.
Attempto Controlled English - Not Just Another Logic.. - Fuchs, Schwertel.. (1999) (5 citations) (Correct)
No context found.
A. Hall, Seven Myths of Formal Methods, IEEE Software, 7, 5, pp. 11-19, 1990
Software Engineering II - Computer Science Tripos (2002) (Correct)
No context found.
Anthony Hall. Seven myths of formal methods. IEEE Software, 7(5):11--19, September 1990.
Formal Methods and the Certification of Critical Systems - Rushby (1993) (50 citations) (Correct)
No context found.
Anthony Hall. Seven myths of formal methods. IEEE Software, 7(5):11--19, September 1990.
Software Specification: A Comparison of Formal Methods - Gannon, Purtilo, Zelkowitz (2001) (9 citations) (Correct)
No context found.
A. Hall. "Seven myths of formal methods," IEEE Software Vol. 7, No. 5, 1990, pp. 11-19.
A Formal View of Multicomputers - Gallud, García, Quiles (Correct)
No context found.
A. Hall. Seven myths of formal methods. IEEE Computer, pages 11--20, September 1990.
Pigs from Sausages? Reengineering from Assembler to C via FermaT.. - Ward (2004) (Correct)
No context found.
A. Hall, "Seven Myths of Formal Methods," IEEE Software (Sept., 1990).
Accepted paper in Integrated Design and Process Technology .. - Dorian Petit Vincent (2003) (Correct)
No context found.
Hall, A. (1990). Seven myths of formal methods. IEEE Software, 7(5).
First 50 documents Next 50
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC