Automatic verification of finite-state concurrent systems using temporal logic specifications
ACM Transactions on Programming Languages and Systems (TOPLAS)
Precise Documentation of Well-Structured Programs
IEEE Transactions on Software Engineering
Functional documents for computer systems
Science of Computer Programming
A logic-model semantics for SCR software requirements
ISSTA '96 Proceedings of the 1996 ACM SIGSOFT international symposium on Software testing and analysis
Automated consistency checking of requirements specifications
ACM Transactions on Software Engineering and Methodology (TOSEM)
Formal methods: state of the art and future directions
ACM Computing Surveys (CSUR) - Special ACM 50th-anniversary issue: strategic directions in computing research
IEEE Transactions on Software Engineering - Special issue on formal methods in software practice
Using Test Oracles Generated from Program Documentation
IEEE Transactions on Software Engineering
Symbolic Model Checking
IEEE Software
Integration in PVS: Tables, Types, and Model Checking
TACAS '97 Proceedings of the Third International Workshop on Tools and Algorithms for Construction and Analysis of Systems
HUG '93 Proceedings of the 6th International Workshop on Higher Order Logic Theorem Proving and its Applications
Static determination of dynamic properties of generalized type unions
Proceedings of an ACM conference on Language design for reliable software
Automatic analysis of consistency between requirements and designs
Automatic analysis of consistency between requirements and designs
Automatic Analysis of Consistency between Requirements and Designs
IEEE Transactions on Software Engineering
Model exploration with temporal logic query checking
Proceedings of the 10th ACM SIGSOFT symposium on Foundations of software engineering
Model exploration with temporal logic query checking
ACM SIGSOFT Software Engineering Notes
| Hi-index | 0.00 |
This paper gives an overview of SC(R)3 - a toolset designed to increase the usability of formal methods for software development. Formal requirements are specified in SC(R)3 in an easy to use and review format, and then used in checking requirements for correctness and in verifying consistency between annotated code and requirements.In this paper we discuss motivations behind this work, describe several tools which are part of SC(R)3 and illustrate their operation on an example of a Cruise Control system.