The role of domain knowledge representation in requirements elicitation
SE'07 Proceedings of the 25th conference on IASTED International Multi-Conference: Software Engineering
Knowledge transfer in global software development: leveraging acceptance test case specifications
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2
Ahab's leg: exploring the issues of communicating semi-formal requirements to the final users
CAiSE'10 Proceedings of the 22nd international conference on Advanced information systems engineering
Generating essential user interface prototypes to validate requirements
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
Applying collaborative process design to user requirements elicitation: A case study
Computers in Industry
Detecting Web requirements conflicts and inconsistencies under a model-based perspective
Journal of Systems and Software
| Hi-index | 0.00 |
Literature tends to discuss software (and system) requirements quality control, which includes validation and verification, as a heterogeneous process using a great variety of relatively independent techniques. Also, process-oriented thinking prevails. In this paper, we attempt to promote the point that this important activity must be studied as a coherent entity. It cannot be seen as a rather mechanical process of checking documents either. Validation, especially, is more an issue of communicating requirements, as constructed by the analysts, back to the stakeholders whose goals those requirements are supposed to meet, and to all those other stakeholders, with whose goals those requirements may conflict. The main problem, therefore, is that of achieving a sufficient level of understanding of the stated requirements by a particular stakeholder, which may be hindered by, for example, lack of technical expertise. In this paper, we develop a unifying framework for requirements quality control. We reorganize the existing knowledge around the issue of communicating requirements to all the different stakeholders, instead of just focusing on some techniques and processes. We hope that this framework could clarify thinking in the area, and make future research a little more focused.