| Home : Testing : Formal Methods |
| Click "Subscribe" if you want to be notified of new or updated links in this category. | Subscribe |
|
|
Formal Methods Listings
|
|
Total:
20 | Displaying: 1 - 10 | Pages: 1 2 >> |
|
|
Sponsored Links
|
|
This paper describes information systems using formal, mathematical specifications written in the Z notation. These specifications are then refined into rigorously checked designs. This paper first introduces formal specification using and example, then introduces the idea of data refinement as a primary means for constructing designs which achieve a formal specification using examples. Author(s) : J.M. Spivey
Updated: 10/08/2005
|
|
|
This thesis builds upon existing research on the formal aspects of human-computer interaction by providing practical specification and development methods for interactive systems. The specification style used is based on the abstract concept of interactors, which has been used extensively at York. The development methods are integrated with a way in which design options that occur may be recorded and choices between them made so that a more constructive development process is provided between the programmer and the client. Author(s) : Christopher John Bramwell
Updated: 10/08/2005
|
|
|
This paper describes an approach to formalization of criteria of computer systems software testing. A brief review of control-flow criteria is introduced. As a formal language for describing the criteria, the Z notation is selected. Z schemas are presented for definitions of the following criteria: statement coverage, decision coverage, condition coverage, decision/condition coverage, full predicate coverage, modified condition/decision coverage, and multiple condition coverage. This characterization could help in the correct understanding of different types of testing and also the correct application of a desired testing regime. Author(s) : Sergiy A. Vilkomir and Jonathan P. Bowen
Updated: 10/08/2005
|
|
|
This slide presentation presents the following topics: potential benefits of formal methods, evaluation assurance levels, building on existing documentation, establishing links between informal, semi-formal and formal methods, what to specify and how, an example: the Java Card VM, specifying and proving in the large, dealing with systems rather than components, using appropriate tools, explaining and justifying specs and proofs, integration of formal methods in a traditional development environment, illustration: test suite generation, and assess the benefits of the formalization. Author(s) : D. Bolignano, D. Le Métayer and C. Loiseaux
Updated: 10/08/2005
|
|
|
Formal specifications have been a focus of software engineering research for many years and have been applied in a wide variety of settings. Their industrial use is still limited but has been steadily growing. After recalling the essence, role, usage, and pitfalls of formal specification, the paper reviews the main specification paradigms to date and discuss their evaluation criteria. It then provides a brief assessment of the current strengths and weaknesses of today's formal specification technology. This provides a basis for formulating a number of requirements for formal specification to become a core software engineering activity in the future. Author(s) : Axel van Lamsweerde
Updated: 10/08/2005
|
|
|
This position statement points out the advantages of using formal methods indirectly for the development of software. It is admitted that formal methods are not adequate for the daily use in large software development projects, except of a few specialized application areas. However, it is argued that formal methods are well-suited for the analysis of the notions and tools which are used in practice. Examples for indirect use of formal methods are given, including a recent case study on formal foundations for SSADM which was carried out by the author. Author(s) : Heinrich Hussmann
Updated: 10/08/2005
|
|
|
This slide presentation covers the following on formal methods: early work, early work on program transformation, software templates, the DSL experiment: 1993-94, MSL - Message Specification Language, experiment design, aftermath of the DSL experiment, embedded DSL's: experience with HAWK, implementing closed DSL's, program transformation revisited, and programatica Logic - 2001. Author(s) : Dick Kieburtz
Updated: 10/08/2005
|
|
|
For whatever reason, formal methods remain one of the more contentious techniques in industrial software engineering. Despite great increases in the number of organizations and projects applying formal methods, it is still the case that the vast majority of potential users of formal methods fail to become actual users. A paper by Hall in 1990 examined a number of 'myths' concerning formal methods, assumed by some to be valid. This paper considers a few more beliefs held by many and presents some counter examples. Author(s) : Jonathan P. Bowen and Michael G. Hinchey
Updated: 10/08/2005
|
|
|
This paper presents an approach to the specification and implementation of provably safe software. It uses well-established tools and techniques that are usually employed to ensure correctness, rather than safety, of software. The approach comprises six steps, each of which is complemented by some proof obligations. For each step, the safety-related aspects are clearly elaborated. Thus, designers of safety-critical systems are given guidance that helps to avoid potentially dangerous gaps in the specification of the system's safety properties. Author(s) : Maritta Heisel
Updated: 10/08/2005
|
|
|
This slide presentation on formal methods covers the following: the storm surge barrier and BOS, approach to software development, and experiences with the use of formal methods: seven myths of formal methods revisited. The seven myths from "Seven Myths of Formal Methods" by Anthony Hall include: 1. FM guarantee correctness, 2. FM are about program proving, 3. FM are only for safety-critical systems, 4. FM require highly trained mathematicians, 5. FM increase development costs, 6. FM are unacceptable to users, and 7. FM are not used on real software. Author(s) : Jan Tretmans, Klaas Wijbrans and Michel Chaudron
Updated: 10/08/2005
|
|
|
Formal Methods Listings
|
|
Total:
20 | Displaying: 1 - 10 | Pages: 1 2 >> |
|
|
