Software development with Z. A practical approach to formal methods in software engineering

1994 ◽  
Vol 2 (3) ◽  
pp. 555-556
Author(s):  
Aristides Dasso ◽  
Ana Funes

Questions such as what are formal methods, how are formal methods implemented, how are they used in software engineering, and when should they be used, among other related questions are the main objective of this chapter. Some definitions are given to answer some of these questions; the chapter also states the aims of FM as well as giving their main characteristics. An example that shows how formal methods can be used for specifying not only software requirements but also the rest of the stages in a software development process is given. A discussion about when they should be used, explaining the reasons why they should be applied when security and reliability are important requirements of the software under development, is presented. Finally, some arguments about how they can also be used as a complement to traditional development methods are provided.


2017 ◽  
Vol 01 (01) ◽  
pp. 1630012
Author(s):  
Taehyung Wang ◽  
Astushi Kitazawa ◽  
Phillip Sheu

One of the most challenging task in software development is developing software requirements. There are two types of software requirements — user requirement (mostly described by natural language) and system requirements (also called as system specifications and described by formal or semi-formal methods). Therefore, there is a gap between these two types of requirements because of inherently unique features between natural language and formal or semi-formal methods. We describe a semantic software engineering methodology using the design principles of SemanticObjects for object-relational software development with an example. We also survey other semantic approaches and methods for software and Web application development.


Author(s):  
Aristides Dasso ◽  
Ana Funes

Questions such as what are Formal Methods, how are Formal Methods implemented, how are they used in Software Engineering and when should they be used, among other related questions, are the main objective of this article. Some definitions are given to answer some of these questions; the article also states the aims of FM as well as it gives their main characteristics. An example that shows how Formal Methods can be used for specifying not only software requirements but also the rest of the stages in a software development process is given. A discussion about when they should be used, explaining the reasons why they should be applied when security and reliability are important requirements of the software under development, is presented. Finally, some arguments about how they can also be used as a complement to traditional development methods are provided.


2021 ◽  
Vol 20 (2) ◽  
pp. 291-292
Author(s):  
Peter Csaba Ölveczky ◽  
Gwen Salaün

Sign in / Sign up

Export Citation Format

Share Document