Safety Analysis Using Petri Nets
IEEE Transactions on Software Engineering
A field study of the software design process for large systems
Communications of the ACM
Software Requirements Analysis for Real-Time Process-Control Systems
IEEE Transactions on Software Engineering
Requirements Specification for Process-Control Systems
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)
ICSE '97 Proceedings of the 19th international conference on Software engineering
Completeness in formal specification language design for process-control systems
FMSP '00 Proceedings of the third workshop on Formal methods in software practice
Generating obstacle conditions for requirements completeness
Proceedings of the 34th International Conference on Software Engineering
| Hi-index | 0.00 |
The complexity of most embedded software limits our ability to assure safety after the fact, e.g., by testing or formal verification of code. Instead, to achieve high confidence in safety requires considering it from the start of system development and designing the software to reduce the potential for hazardous behavior. An approach to building safety into embedded software will be described that integrates system hazard analysis, user task analysis, traceability, and informal specifications combined with executable and analyzable models. The approach has been shown to be feasible and practical by applying it to complex systems experimentally and by its use on real projects.