4 citations found. Retrieving documents...
Leveson, N. G., guest editorial "Formal Methods in Software Engineering," IEEE Transactions on Software Engineering, Vol. 16, No. 9, Sept. 1990, pp. 929-931.

 Home/Search   Document Not in Database   Summary   Related Articles   Check  

This paper is cited in the following contexts:
Practical Computer Security Analysis - Kienzle (1998)   (Correct)

....identical position [NASA95] Leveson reinforces this position, saying there is a need to determine how and where formal methods are most effective the more rigorous and costly procedures might well be reserved for those software qualities that need to be ensured with very high confidence. [Lev90] And, as noted above, Parnas s work on the A 7 provides an excellent example of the utility of risk specific application of rigor. Depending on the risks, an application of MOAT can result in varying degrees of formality along all five of these axes. The MOAT approach provides a framework in ....

Leveson, N. G., guest editorial "Formal Methods in Software Engineering," IEEE Transactions on Software Engineering, Vol. 16, No. 9, Sept. 1990, pp. 929-931.


The Application of Formal Methods to the Reverse Engineering of.. - Gannod (1994)   (Correct)

....caused by software failure have been well documented and with the change in laws concerning liability [6] the need to reduce the number of problems due to software increases. Formal methods in software development provide many benefits in the forward engineering aspect of software development [7, 8, 9, 10, 11]. One of the advantages of using formal methods in software development is that the formal notations are precise, verifiable, and facilitate automated processing [12] Reverse Engineering is the process of constructing high level representations from lower level instantiations of an existing ....

N. G. Leveson, "Formal Methods in Software Engineering," IEEE Transactions on Software Engineering, vol. 16, pp. 929--930, September 1990.


Design Recovery Through Formal Specification - Lim, Harrison, Bailes, Berglas (1998)   (1 citation)  (Correct)

....is a simple and reliable approach to apply formal methods to design recovery that will ensure correctness in the specification and therefore the recovered design. 1. Introduction Formal methods in software development provide many benefits in the forward engineering aspect of software development [16, 17, 27, 31, 43]. Although formal methods have being used in reverse engineering, the application of the formal methods is mainly on the formalisation of the recovered design in order to facilitate further analysis [6, 8, 14, 15, 28, 38, 41, 44] There is little attempt on applying formal methods to specify the ....

Leveson, N.G. (1990). Formal Methods in Software Engineering. IEEE Transaction on Software Engineering, 16(9), Sept., pp. 929-930.


Facilitating the Maintenance of Safety-Critical Systems - Gannod, Cheng (1994)   (Correct)

....or due to software failure have been well documented and with the change in laws concerning liability [2] the need to reduce the number of problems caused by software increases. Formal methods in software development provide many benefits in the forward engineering aspect of software development [3, 4, 5, 6, 7]. One of the advantages of using formal methods in software development is that the formal notations are precise, verifiable, and facilitate automated processing [8] Reverse Engineering is the process of constructing high level representations from lower level instantiations of an existing ....

N. G. Leveson, "Formal Methods in Software Engineering," IEEE Transactions on Software Engineering, vol. 16, pp. 929--930, September 1990.

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