Inconsistency-Based Strategy for Clarifying Vague Software Requirements
It seems to be inevitable to confront vague information about customer’s needs during the software requirements stage. It may be desirable to record and clarify the vague information to avoid missing real requirements. In this paper, we provide an inconsistency-based strategy to handle vague information in the framework of Annotated Predicate Calculus. This strategy permits the stakeholder to describe the different vague information using statements with different levels of belief, where each level of belief is determined by the degree of vagueness. By checking consistency of the union of vague requirements and clear requirements, we then heighten the level of belief in uncontroversial vague requirements. We also lower the levels of belief in requirements involved in undesirable inferences and leave them to be articulated in some following stage. To support this, Annotated Predicate Calculus is used to represent the requirements specification. In particular, we present a special belief semilattice, which defines truth values appropriate for representing the strength of analyst’s belief in the truth of requirements statements.
Unable to display preview. Download preview PDF.
- 2.Spanoudakis, G., Zisman, A.: Inconsistency management in software engineering: Survey and open research issues. In: Chang, S.K. (ed.) Handbook of Software Engineering and Knowledge Engineering, pp. 329–380. World Scientific Publishing Co., Singapore (2001)Google Scholar
- 7.Easterbrook, S., Chechik, M.: A framework for multi-valued reasoning over inconsistent viewpoints. In: Harrold, M., Schafer, W., Muller, H. (eds.) Proceedings of International Conference on Software Engineering (ICSE 2001), Toronto, Canada, pp. 411–420 (2001)Google Scholar