Abstract
Disagreements in interpreting words in software requirements specifications (SRSs) can lead to project failure. Various approaches to identifying and preventing ambiguous words in SRSs have been proposed. Yet, it is unclear which ambiguous words are used in the actual SRSs and to what extent they need to be modified. This paper quantitatively analyzes existing SRSs to clarify (1) how many ambiguous words are included in SRSs and (2) how many of these words require correction. This paper targets the Request for Proposals (RFPs), which describe the initial requirements of 40 systems of local governments, libraries, universities, and hospitals in Japan. Ten ambiguous Japanese words were analyzed. The result shows that “juubun” (sufficient) appeared most frequently, and 42% required correction when this word was used. The result also indicates that the number of ambiguous words varied greatly among the RFPs and that larger RFPs did not necessarily contain more ambiguous words.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
