Experiences using statecharts for a system requirements specification

Authors:
N. G. Leveson;M. Heimdahl;H. Hildreth;J. Reese;R. Ortega
Affiliations:
University of California, Irvine, CA;University of California, Irvine, CA;University of California, Irvine, CA;University of California, Irvine, CA;University of California, Irvine, CA
Venue:
IWSSD '91 Proceedings of the 6th international workshop on Software specification and design
Year:
1991

Citing 5
Cited 2

Software safety: why, what, and how

ACM Computing Surveys (CSUR)
Safety Analysis Using Petri Nets

IEEE Transactions on Software Engineering
Statecharts: A visual formalism for complex systems

Science of Computer Programming
Software Requirements Analysis for Real-Time Process-Control Systems

IEEE Transactions on Software Engineering
Specification and analysis of the requirements for embedded software with an external interaction model

Specification and analysis of the requirements for embedded software with an external interaction model

Reduction and slicing of hierarchical state machines

ESEC '97/FSE-5 Proceedings of the 6th European SOFTWARE ENGINEERING conference held jointly with the 5th ACM SIGSOFT international symposium on Foundations of software engineering
ROAD/EE: A Prototyping Environment for Object-Oriented Specifications

TOOLS '97 Proceedings of the Tools-23: Technology of Object-Oriented Languages and Systems

Quantified Score

Hi-index	0.00

Visualization

Abstract

This paper describes some lessons learned and issues raised while building a system requirements specification for a real aircraft collision avoidance system using statecharts. Some enhancements to statecharts were necessary to model the complete system and a few notational changes were made to improve reviewability.