Quantitative analysis of an application of formal methods

  • Juan Bicarregui
  • Jeremy Dick
  • Eoin Woods
Session 1: B
Part of the Lecture Notes in Computer Science book series (LNCS, volume 1051)


This paper reports on the experience gained in the MaFMeth project, which undertook a formal development with tool support for several parts of the life cycle from requirements capture through to C code generation. We explore the hypotheses that formal methods enable the early detection of faults in design by examining the development process in the light of the stages at which faults were introduced and discovered.


Formal Method Unit Test Development Life Cycle Rutherford Appleton Laboratory Capability Maturity Model 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. 1.
    J.C. Bicarregui, J. Dick and E. Woods, Supporting the length of formal development: from diagrams to VDM to B to C Proceedings, 7th International Conference on: Putting into practice method and tools for information system design, Nantes (France), October '95, IUT de Nantes, H. Habrias (Editor) 1995.Google Scholar
  2. 2.
    J.C. Bicarregui and B. Ritchie. Invariants, frames and postconditions: a comparison of the VDM and B notations. In Proceedings of Formal Methods Europe '93, Lecture Notes in Computer Science, Springer-Verlag, 1993.Google Scholar
  3. 3.
    Jeremy Dick and Jerome Loubersac. A Visual Approach to VDM: Entity-Structure Diagrams. Technical Report DE/DRPA/91001, Bull, 68, Route de Versailles, 78430 Louveciennes (France), January 1991.Google Scholar
  4. 4.
    Jeremy Dick and Alain Faivre. Automating the generation and sequencing of test cases from model-based specifications. In J.C.P. Woodcock and P.G. Larsen, editors, FME'93: Industrial-Strength Formal Methods, pages 268–284, Formal Methods Europe, Springer-Verlag, April 1993. Lecture Notes in Computer Science 670.Google Scholar
  5. 5.
    J.Dick, Fault grids: another way of presenting fault counts, Software Reliability and Metrics Club Newsletter, Issue 16, July 1995, p 2–4. (published by the Centre for Software Reliability, University of Newcastle upon Tyne).Google Scholar
  6. 6.
    Des Maisey and Jeremy Dick, Measuring the quality of the development life cycle process, Submitted to SQM96, Software Quality Measurement.Google Scholar
  7. 7.
    U.K. Department of Trade and Industry, TickIT: Guide to Software Quality Management, System Construction and Certification using ISO9001/EN29001/BS5750 Part 1, February 1992, TickIT Project Office, 68 Newman Street, London, W1A 4SE, UK.Google Scholar
  8. 8.
    M.C. Paulk, W. Curtis, M.B. Chrissis, C.V. Weber, Capability Maturity Model for Software, Version 1.1, Carnegie Mellon University Software Engineering Institute Technical Report, CME/SEI-93-TR-24, February 1993.Google Scholar
  9. 9.
    E. Woods, The Development of a Software Subsystem Using VDM and B, University of Manchester, Board for Continuing Education, Department of Computer Science, MSc Thesis, 1995.Google Scholar
  10. 10.
    J. Dick and E. Woods, Lessons Learned Applying Formal Methods to System Software Development, submitted (July 1995) to IEEE Software.Google Scholar
  11. 11.
    Yourdon Inc., The Yourdon Systems Method: Model Driven Systems Development, Prentice Hall, Englewood Cliffs, NJ, USA, 1993, ISBN 0-13-285818-5Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 1996

Authors and Affiliations

  • Juan Bicarregui
    • 1
  • Jeremy Dick
    • 2
  • Eoin Woods
    • 3
  1. 1.Rutherford Appleton LaboratoryUK
  2. 2.B-CoreUK
  3. 3.SybaseUK

Personalised recommendations