Abstract
Requirements Engineering (RE) activity is often initiated with vaguely specified software requirements. The ambiguities must be overcome to the extent possible when the requirements are specified. Both functional (FRs) and non-functional (NFRs) requirements should be correctly and unambiguously specified. Users communicate about the NFRs in informal discussions. Requirements engineers use formal or semi-formal language notations to manually convey the NFRs. A laborious and ineffective manual approach, however, is unable to identify all likely NFRs and resolve ambiguities in those NFRs. This paper discusses an approach that attempts to overcome ambiguities from natural language requirements, recognize NFRs, and generate NFR specification through the extended Unified Modelling Language (UML) viz. use-case diagram. The empirical evaluation of the proposed approach on the PROMISE dataset achieves an average result of 79.76% recall, 90.05% precision, and 84.59% F-measure. The proposed approach allows the requirements analyst to semi-automatically recognize NFRs and visualize them using an extended use-case diagram at an early stage of RE.
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.
