A framework for evaluating specification methods for reactive systems-experience report

Numerous formal specification methods for reactive systems have been proposed in the literature. Because the significant differences between the methods are hard to determine, choosing the best method for a particular application can be difficult. We have applied several different methods, including...

Full description

Saved in:
Bibliographic Details
Published in:IEEE transactions on software engineering 1996-06, Vol.22 (6), p.378-389
Main Authors: Ardis, M.A., Chaves, J.A., Jagadeesan, L.J., Mataga, P., Puchol, C., Staskauskas, M.G., Von Olnhausen, J.
Format: Article
Language:English
Subjects:
Algorithms
Application software
Applied sciences
Communication channels
Comparative studies
Computer programming
Computer science
control theory
systems
Control system analysis
Control theory. Systems
Design
Design methodology
Exact sciences and technology
Formal specifications
Laboratories
Language
Logical, boolean and switching functions
Methods
Office automation, teleprocessing
Programming
Programming languages
Protocols
Software
Software design
Software development
Specification languages
Specifications
Switching systems
System testing
Systems design
Telephone switching equipment
Telephony
Theoretical computing
Citations: Items that this one cites
Items that cite this one
Online Access:Get full text
Tags: Add Tag
No Tags, Be the first to tag this record!
Description
Summary:Numerous formal specification methods for reactive systems have been proposed in the literature. Because the significant differences between the methods are hard to determine, choosing the best method for a particular application can be difficult. We have applied several different methods, including Modechart, VFSM, ESTEREL, Basic LOTOS, Z, SDL, and C, to an application problem encountered in the design of software for AT&T's 5ESS telephone switching system. We have developed a set of criteria for evaluating and comparing the different specification methods. We argue that the evaluation of a method must take into account not only academic concerns, but also the maturity of the method, its compatibility with the existing software development process and system execution environment, and its suitability for the chosen application domain.
ISSN:0098-5589
1939-3520
DOI:10.1109/32.508312