Software safety: why, what, and how
ACM Computing Surveys (CSUR)
Statecharts: A visual formalism for complex systems
Science of Computer Programming
Communications of the ACM
A general-purpose algorithm for analyzing concurrent programs
Communications of the ACM
STATEMATE: A Working Environment for the Development of Complex Reactive Systems
IEEE Transactions on Software Engineering
On the development of reactive systems
Logics and models of concurrent systems
Software Requirements Analysis for Real-Time Process-Control Systems
IEEE Transactions on Software Engineering
Communicating Real-Time State Machines
IEEE Transactions on Software Engineering - Special issue: specification and analysis of real-time systems
Targeting safety-related errors during software requirements analysis
SIGSOFT '93 Proceedings of the 1st ACM SIGSOFT symposium on Foundations of software engineering
Experience with Formal Methods in Critical Systems
IEEE Software
Requirements Specification for Process-Control Systems
IEEE Transactions on Software Engineering
Formal Methods Reality Check: Industrial Usage
IEEE Transactions on Software Engineering
Completeness and Consistency in Hierarchical State-Based Requirements
IEEE Transactions on Software Engineering - Special issue: best papers of the 17th International Conference on Software Engineering (ICSE-17)
Automated consistency checking of requirements specifications
ACM Transactions on Software Engineering and Methodology (TOSEM)
Communicating sequential processes
Communications of the ACM
The Core Method for Real-Time Requirements
IEEE Software
Specification and analysis of the requirements for embedded software with an external interaction model
Specifying Software Requirements for Complex Systems: New Techniques and Their Application
IEEE Transactions on Software Engineering
| Hi-index | 0.00 |
In embedded systems the interfaces between software and its embedding environment are a major source of costly errors. For example, Lutz reported that 20% - 35% of the safety related errors discovered during integration and system testing of two spacecraft were related to the interfaces between the software and the embedding hardware. Also, the software's operating environment is likely to change over time further complicating the issues related to system level inter-component communication. In this paper we discussed a formal approach to the specification and analysis of inter-component communication using a revised version of the RSML (Requirements State Machine Language) specification language. The formalism allows rigorous specification of the physical aspects of the inter-component communication and enables encapsulation of communication related properties in well defined interface specifications. This allows us to both analyze a system design and detect incompatibilities between connected components and use the interface specifications as simple safety kernels to enforce safety and simple liveness constraints.