Modern structured analysis
Object oriented design with applications
Object oriented design with applications
A practical guide to real-time systems development
A practical guide to real-time systems development
Z: An Introduction to Formal Methods
Z: An Introduction to Formal Methods
Requirements-based product line engineering
Proceedings of the 8th European software engineering conference held jointly with 9th ACM SIGSOFT international symposium on Foundations of software engineering
Building security requirements with CLASP
SESS '05 Proceedings of the 2005 workshop on Software engineering for secure systems—building trustworthy applications
An application of uncertain reasoning to requirements engineering
UAI'99 Proceedings of the Fifteenth conference on Uncertainty in artificial intelligence
Journal of Systems and Software
Hi-index | 0.00 |
Systems Analysis, or as it is increasingly known as today, Requirements Engineering, is a time consuming, expensive but critical phase in software (and system) development. The "perfect" Requirements Specification should exhibit a number of qualities including correctness, completeness and consistency. Within a Requirements Specification individual requirements at the microscopic level should be justified, clear, unambiguous and verifiable. However, in many cases Systems Analysts or Requirements Engineers describe requirements which fall short of these demands. In addition, outside reviewers faced with presenting an independent qualitative assessment of a Requirements Specification have few guidelines to assist them. In this paper we present a simple technique, borrowed from objective setting in Management Psychology, to assist the construction and evaluation of individual requirements.