Proceedings IEEE Joint International Conference on Requirements Engineering (2002)
Sept. 9, 2002 to Sept. 13, 2002
<p> A major concern of most software customers, managers, and requirements engineers is to remove ambiguity in communication of requirements and specifications. The most obvious solution is to try to anticipate all possible misunderstandings and write the requirements perfectly precisely. In practice, this doesn?t work.</p> <p>This talk explains why it doesn?t work, and offers easy, inexpensive methods for removing ambiguity-methods that anyone can do. The fundamental principle is to add redundancy, especially redundancy relating to context. High-bandwidth, informal communication is always a necessary supplement to formal, mathematical expressions. As software development is in essence the creation of formal, executable descriptions for the informal domains where our intents lie, we explore many ways to break up this process into small stages, allowing programmers and customers to detect ambiguity through real-world feedback.</p>
B. Kovitz, "Ambiguity and What to Do about It," Proceedings IEEE Joint International Conference on Requirements Engineering(RE), Essen, Germany, 2002, pp. 213.