The Z notation: a reference manual
The Z notation: a reference manual
PD and joint application design: a transatlantic comparison
Communications of the ACM - Special issue Participatory Design
Joint application development (2nd ed.)
Joint application development (2nd ed.)
Use case maps for object-oriented systems
Use case maps for object-oriented systems
The Object-Z specification language
The Object-Z specification language
Requirements engineering: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Formal specification: a roadmap
Proceedings of the Conference on The Future of Software Engineering
Does OO Sync with How We Think?
IEEE Software
What is a Good Formal Specification?
Proceedings of the Fifth Annual Z User Meeting on Z User Workshop
Encoding Object-Z in Isabelle/HOL
ZB '02 Proceedings of the 2nd International Conference of B and Z Users on Formal Specification and Development in Z and B
Using GSSs to Support Error Detection in Software Specifications
HICSS '98 Proceedings of the Thirty-First Annual Hawaii International Conference on System Sciences - Volume 1
Making Behaviour a Concrete Architectural Concept
HICSS '99 Proceedings of the Thirty-second Annual Hawaii International Conference on System Sciences-Volume 8 - Volume 8
Mathematical Approaches to Software Quality
Mathematical Approaches to Software Quality
Criteria used in selecting effective requirements elicitation procedures
Proceedings of the 2007 annual research conference of the South African institute of computer scientists and information technologists on IT research in developing countries
Principles of good software specification and their implications for specification languages
AFIPS '81 Proceedings of the May 4-7, 1981, national computer conference
A four-way framework for validating a specification
SAICSIT '10 Proceedings of the 2010 Annual Research Conference of the South African Institute of Computer Scientists and Information Technologists
Hi-index | 0.01 |
It is a common practice in software development and other engineering domains to design more than one solution for a complex problem and consider only the most appropriate one. Similar practice is observed when procuring a new software product. The literature recommends this practice and intensively reveals a number of practical cases, yet is largely silent on how to make such a selection. In requirements engineering, an important issue is to provide a basis for judging and selecting one specification above others. This paper proposes through a case study, an approach to evaluate and compare two Object-Z specifications of the same set of requirements and hence, provides a means to select the most appropriate one. The approach recommends identifying properties expected from a satisfactory specification, uses existing validation techniques to evaluate proposed specifications and defines guidelines for comparison to facilitate the choice.