Experiences Using Lightweight Formal Methods for Requirements Modeling
IEEE Transactions on Software Engineering
Low-cost pathways towards formal methods use
FMSP '98 Proceedings of the second workshop on Formal methods in software practice
Applying the SCR requirements method to a weapons control panel: an experience report
FMSP '98 Proceedings of the second workshop on Formal methods in software practice
Proving Invariants of I/O Automata with TAME
Automated Software Engineering
Restructuring Requirements Specifications For Managing Inconsistency And Change: A Case Study
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
Validating Requirements for Fault Tolerant Systems using Model Checking
ICRE '98 Proceedings of the 3rd International Conference on Requirements Engineering: Putting Requirements Engineering to Practice
From Complex Specifications to a Working Prototype. A Protocol Engineering Case Study
FME '01 Proceedings of the International Symposium of Formal Methods Europe on Formal Methods for Increasing Software Productivity
V & V through Inconsistency Tracking and Analysis
IWSSD '98 Proceedings of the 9th international workshop on Software specification and design
Wireless protocol testing and validation supported by formal methods: a hands-on report
Journal of Systems and Software - Special issue: Software engineering education and training
Constraint animation using an object-oriented declarative language
ACM-SE 38 Proceedings of the 38th annual on Southeast regional conference
Hi-index | 0.02 |
This paper describes our work exploring the suitability of formal specification methods for independent verification and validation (IV&V) of software specifications for large, safety critical systems. An IV&V contractor often has to perform rapid analysis on incomplete specifications, with no control over how those specifications are represented. Lightweight formal methods show significant promise in this context, as they offer a way of uncovering major errors, without the burden of full proofs of correctness. We describe an experiment in the application of the method SCR to testing for consistency properties of a partial model of the requirements for Fault Detection Isolation and Recovery on the space station. We conclude that the insights gained from formalizing a specification is valuable, and it is the process of formalization, rather than the end product that is important. It was only necessary to build enough of the formal model to test the properties in which we were interested. Maintenance of fidelity between multiple representations of the same requirements (as they evolve) is still a problem, and deserves further study.