Integrating Formal Methods into the Development Process

Authors:
Richard A. Kemmerer
Affiliations:
-
Venue:
IEEE Software
Year:
1990

Citing 3
Cited 10

Abstract data types and software validation

Communications of the ACM
Formal specification as a design tool

POPL '80 Proceedings of the 7th ACM SIGPLAN-SIGACT symposium on Principles of programming languages
Processor-per-Domain Guard Architecture

SP '83 Proceedings of the 1983 IEEE Symposium on Security and Privacy

Informal and Formal Requirements Specification Languages: Bridging the Gap

IEEE Transactions on Software Engineering
Strategies for incorporating formal specifications in software development

Communications of the ACM
Experiences Using Lightweight Formal Methods for Requirements Modeling

IEEE Transactions on Software Engineering
A practical approach to security assessment

NSPW '97 Proceedings of the 1997 workshop on New security paradigms
A formal approach to scenario integration

Annals of Software Engineering
A formal approach to object-oriented software engineering

Theoretical Computer Science - Rewriting logic and its applications
Preconditions for understanding

IWSSD '91 Proceedings of the 6th international workshop on Software specification and design
Evaluating the recovery-oriented approach through the systematic development of real complex applications

Software—Practice & Experience
Formal analysis of an electronic voting system: An experience report

Journal of Systems and Software
Large-scale formal verification in practice: a process perspective

Proceedings of the 34th International Conference on Software Engineering

Quantified Score

Hi-index	0.02

Visualization

Abstract

It is shown that integrating formal specification and verification with development is faster and more cost-effective than doing the steps separately or in parallel. This case study demonstrates their application in a security context and documents their use in several phases of development, starting from the requirements of a terminal serving a security officer, on through formal requirements and design expressed as state transitions, to detailed design specifications and proofs that these agree with higher-level specifications, stopping just before code-level verification (due to complications typical of such projects). The effects of verification on this particular project are addressed.