Statecharts: A visual formalism for complex systems
Science of Computer Programming
Safeware: system safety and computers
Safeware: system safety and computers
Fault-tolerant computer system design
Fault-tolerant computer system design
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)
Using Z: specification, refinement, and proof
Using Z: specification, refinement, and proof
Using Abstraction and Model Checking to Detect Safety Violations in Requirements Specifications
IEEE Transactions on Software Engineering
Software engineering (2nd ed.): principles and practice
Software engineering (2nd ed.): principles and practice
Specifying embedded systems with statecharts and Z: an agenda for cyclic software components
Science of Computer Programming - Specical issue on fundamental approaches to software engineering
Software engineering (6th ed.)
Software engineering (6th ed.)
Real-Time Systems and Software
Real-Time Systems and Software
Requirements Engineering: Processes and Techniques
Requirements Engineering: Processes and Techniques
Modeling Reactive Systems with Statecharts: The Statemate Approach
Modeling Reactive Systems with Statecharts: The Statemate Approach
Formal Development of Reactive Systems - Case Study Production Cell
A Steam-Boiler Control Specification with Statecharts and Z
Formal Methods for Industrial Applications, Specifying and Programming the Steam Boiler Control (the book grow out of a Dagstuhl Seminar, June 1995).
PRDC '01 Proceedings of the 2001 Pacific Rim International Symposium on Dependable Computing
Integrative analysis of state-based requirements for completeness and consistency
Integrative analysis of state-based requirements for completeness and consistency
From informal specification to formalization: an automated visualization approach
From informal specification to formalization: an automated visualization approach
Generating model-based test cases from natural language requirements for space application software
Software Quality Control
Hi-index | 0.00 |
Software development starts by specifying the requirements. A Software Requirements Specification (SRS) describes what the software must do. Naturally, the SRS takes the core role as the descriptive documentation at every phase of the development cycle. To avoid problems in the latter development phases and reduce life-cycle costs, it is crucial to ensure that the specification is correct. This paper describes how to model, test and evaluate (i.e., check, examine, and probe) a natural language (NL) SRS using two formalisms (Z and Statecharts). These formalisms are used to determine strategies for avoiding design defects that stem from the requirements that could ultimately lead to system failures. A case study was performed to validate the integrity of a Guidance Control SRS in terms of completeness, consistency, and fault-tolerance. Based on these experiences, the NL-specification→Z→Statechart transformations can be completed in a systematic and repeatable manner that yield valuable insight into the overall integrity of software specifications.