An Ambiguity Minimization Technique during Requirements Elicitation Phase

The ability to achieve valid requirements and subsequently delay in software projects is caused by ambiguity among other factors. This paper proposes an ambiguity minimization technique during requirements, this technique is premised on the view that wrong system objectives and business requirements results in problems characterizing the entire software. Since these objectives are defined during the elicitation phase, we used data from 3 companies in industry to relate the system objective to the business need so as to provide a desired product. We use set theory from a calculus perspective, to design a mapping technique to achieve clear requirement.