1. Choosing a Formal Method Mike Weissert COSC 481

2. Outline Introduction Reasons For Choosing Formality Application Characteristics Criteria For A Successful Application Needs/Constraints Of The Organization Characteristics Of A Formal Method Conclusion Sources

3. Introduction The choice in using FMs requires the same decision making skills used to make any other decision. Requirements: Clear Objectives Knowledge of Constraints In selecting a method, you will choose one in which the tools, experience, and support most closely meets these requirements.

4. Reasons for Choosing Formality Improve the Quality of the Entire Development Process When your goal is for a general improvement of your company’s development process

5. Reasons for Choosing Formality Improve Integrity, Reliability, and Other Characteristics of a System System development can be enhanced parallel with software development Use when goal is to enhance the system architecture as well as the software

6. Reasons for Choosing Formality Reduce Specification Errors Using FMs, the system specification (in particular the functional specification) can be expressed in a way that greatly reduces errors.

7. Reasons for Choosing Formality Improvements In the Requirements Definition Requirements are normally expressed in non-formal language Using formal expressions, omissions and inconsistencies are found more easily then with other techniques

8. Reasons for Choosing Formality Improved Documentation and Understanding Present legacy software is undocumented or has very inadequate documentation. Using FMs in your documentation makes for easier understanding of software and better confidence in its reliability

9. Reasons for Choosing Formality Provide a firm foundation for: Maintenance Enhancement

10. Reasons for Choosing Formality Gain Knowledge About the Properties of a Design Architecture Provides an understanding of the design of the software in terms of: Properties Limitations

11. Reasons for Choosing Formality Acquire a More Rational Basis for Choosing Test Data New techniques developed where test data is being derived from functional specifications of the software components. These techniques become more systematic if FMs are used in the functional specification.

12. Reasons for Choosing Formality To Become as Certain As Possible that the Design and Implementation are Error Free Important in safety-critical fields Using FMs, one can see “proofs of correctness” during the development cycle

13. Reasons for Choosing Formality Customer/Standards Requirement? Contracts might mandate the use of FMs in the development cycle

14. Application Characteristics There Are 3 Intrinsic Characteristics of an Application: “Phenomenological Model” Computational Model Physical and Societal Environment

15. Application Characteristics: Phenomenological Model The mathematics used by the scientific theory of the application to explain its phenomena Examples The Phenomenological model of: Ballistics & Civil Engineering is Classic Mechanics Telephony is Traffic and Switching Theory

16. Application Characteristics: Computational Model Related to the Phenomenological model, this model relates to the structure of the computations which reflect and model a specific system within the application. Different structures include: Sequential Distributed Distributed and concurrent Dependent on real time events

17. Application Characteristics: Physical and Societal Environment Several considerations: Safety system? Embedded system? Cost-critical? High volume cost critical? Large human interaction?

18. Criteria For A Successful Application Customers and users find applications acceptable for different reasons. Rating the following features will help in developing an application: Correct Functioning High Performance Ease of Use

19. Needs/Constraints Of The Organization Different FMs have different levels of support based upon: Available Literature Courses Documented Experience Tools

20. Needs/Constraints Of The Organization Important for an organization to have a reasonably well-developed software engineering discipline already in place. Before engaging in FMs, your organization should have: Good level of engineering experience In-house working standards

21. Needs/Constraints Of The Organization When adopting FMs its good if the staff have either: Used FMs previously Understand some of the principles of FMs When adopting FMs for the 1 st time good to adopt a training program in which you will have to consider: Available training budget Time scales

22. Characteristics of a FM If you need to ensure the correctness of your end software product, it may be wise to adopt a method whose tools enables proof of correctness.

23. Characteristics of a FM: Level of Abstraction Different languages display varying levels of abstraction at which they support discourse: Can be categorized by: Language Requirements Functional Specification Design Ability to be Executed “Should choose a method and language whose capability best supports the part of the development process where formalization is going to be most beneficial”

24. Characteristics of a FM: Computational Model The languages of different methods allow for different kinds of computation. Wise to match the language to the computational model of the application. Several Model Classifications: Sequential Parallel Dynamic Real-time Indifferent

25. Characteristics of a FM: Supported by Tools Many tools available Differ in: Capabilities Maturity Degree of commercial support Ease of use

26. Conclusion When choosing a formal method, there are several steps that should be followed to make an intelligent and beneficial selection for your organization. By following the steps outlined in this presentation, your experience with FMs should go more smoothly.

27. Sources Formal Methods Europe http://www.fmeurope.org/fme/choosing. htm http://www.fmeurope.org/fme/choosing. htm Michael G. Hinchey, Jonathan P. Bowen: Applications of Formal Methods. Prentice Hall International (UK), 1995.