CADiZ : an architecture for Z tools and its implementation
Software—Practice & Experience
SOFL: A Formal Engineering Methodology for Industrial Applications
IEEE Transactions on Software Engineering
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Generating statechart designs from scenarios
Proceedings of the 22nd international conference on Software engineering
Software engineering (6th ed.)
Software engineering (6th ed.)
Test Driven Development: By Example
Test Driven Development: By Example
Investigating the readability of state-based formal requirements specification languages
Proceedings of the 24th International Conference on Software Engineering
Synthesis of Behavioral Models from Scenarios
IEEE Transactions on Software Engineering
A Modular Framework for the Integration of Heterogeneous Notations and Tools
IFM '99 Proceedings of the 1st International Conference on Integrated Formal Methods
Use Case Maps for the Capture and Validation of Distributed Systems Requirements
RE '99 Proceedings of the 4th IEEE International Symposium on Requirements Engineering
Using Use Cases in Executable Z
ICFEM '00 Proceedings of the 3rd IEEE International Conference on Formal Engineering Methods
The mystery of formal methods disuse
Communications of the ACM - Interactive immersion in 3D graphics
Fit for Developing Software: Framework for Integrated Tests (Robert C. Martin)
Fit for Developing Software: Framework for Integrated Tests (Robert C. Martin)
Generating Annotated Behavior Models from End-User Scenarios
IEEE Transactions on Software Engineering
ZB'05 Proceedings of the 4th international conference on Formal Specification and Development in Z and B
| Hi-index | 0.00 |
A formal specification, written in a mathematical notation, is beyond the comprehension of the average software customer. As a result, the customer cannot provide useful feedback regarding its correctness and completeness. To address this problem, we suggest the formalism expert to work with the customer to create precise scenarios. With only a few simple Z concepts, a precise scenario describes an operation by its effects on the system state. The customer would find a concrete precise scenario easier to understand than its corresponding abstract schema. The Z expert derives schemas based on the precise scenarios. Precise scenarios afford user involvement that improves the odds of a formal specification fully capturing the user requirements.