Extraction of Essential Requirements from Natural Language Requirements
Keywords:
About, Essential Use Case, Natural Language, Requirements Engineering, Synonym Extraction,Abstract
Requirement is a formal expression of user’s need. It is the main foundation of any software development project. Natural language (NL) is often used to express and write system requirements specifications as well as user requirements. However, there is a very high probability that more than half natural language requirements can be ambiguous, incomplete and inaccurate. A software engineer can miss-interpret the natural language requirements and can generate an erroneous software model, which finally will lead to project failure. Earlier, we have introduced a prototype tool that provides natural language requirements authoring facilities and consistency checking to assist requirement engineers when working with informal and semi-formal requirements. However, the tool has pattern limitation to support the extraction of the essential requirements from the NL requirements. Therefore this study is aimed to enhance the accuracy and scalability of the tool to capture the essential requirements from the NL requirements. Our approach is to implement lexical analysis and embed an English lexical database where it will serve as a thesaurus in the tool. This tool is expected to be able to find the synonym of the extracted phrases (essential requirements) in the database to match it to the essential interaction pattern (phrases and expressions) in the library. Our future work will focus on the next phase of requirements engineering, which is requirements validation.References
Alberto Rodrigues da Silva, “Quality of Requirements Specifications: A Preliminary Overview of An Automatic Validation Approach,” in 29th Annual ACM Symposium on Applied Computing, 2014, pp. 1021–1022.
M. Kamalrudin, J. Grundy, and J. Hosking, “MaramaAI: tool support for capturing and managing consistency of multi-lingual requirements,” Proc. 27th IEEE/ACM Int. Conf. Autom. Softw. Eng. - ASE 2012, p. 326, 2012.
M. Kamalrudin, J. Grundy, and J. Hosking, “Tool support for essential use cases to better capture software requirements,” in Proceedings of the IEEE/ACM international conference on Automated software engineering - ASE ’10, 2010, p. 255.
M. Kamalrudin and J. Grundy, “Generating essential user interface prototypes to validate requirements,” in 2011 26th IEEE/ACM International Conference on Automated Software Engineering (ASE 2011), 2011, pp. 564–567.
M. Kamalrudin, J. Grundy, and J. Hosking, “Managing Consistency between Textual Requirements, Abstract Interactions and Essential Use Cases,” in 2010 IEEE International Conference on Computer Software and Applications Conference (COMPSAC), 2010, no. July, pp. 327–336.
M. Kamalrudin, J. Hosking, and J. Grundy, “Improving requirements quality using essential use case interaction patterns,” in 2011 33rd International Conference on Software Engineering (ICSE), 2011, pp. 531–540.
M. Kamalrudin, N. A. Moketar, J. Grundy, and J. Hosking, “Automatic Acceptance Test Case Generation From Essential Use Cases,” in 13th International Conference on Intelligent Software Methodologies, Tools and Techniques, 2014, pp. 246–255.
N. A. Moketar, M. Kamalrudin, S. Sidek, and M. Robinson, “TestMEReq : Automated Acceptance Testing Tool For Requirements Validation,” in International Symposium on Research in Innovation and Sustainability, 2014, pp. 15–16.
N. A. Moketar, M. Kamalrudin, S. Sidek, M. Robinson, and J. Grundy, “TestMEReq: Generating Abstract Tests for Requirements Validation,” in Proceedings of the 3rd International Workshop on Software Engineering Research and Industrial Practice - SER&IP ’16, 2016, pp. 39–45.
N. A. Moketar, M. Kamalrudin, S. Sidek, M. Robinson, and J. Grundy, “An Automated Collaborative Requirements Engineering Tool for Better Validation of Requirements,” in 31st IEEE/ACM International Conference on Automated Software Engineering (ASE 2016), 2016, pp. 864–869.
N. A. Moketar, M. Kamalrudin, S. Sidek, M. Robinson, and J. Grundy, “An automated collaborative requirements engineering tool for better validation of requirements,” in Proceedings of the 31st IEEE/ACM International Conference on Automated Software Engineering - ASE 2016, 2016, pp. 864–869.
B. Gleich, O. Creighton, and L. Kof, “Ambiguity Detection : Towards a Tool Explaining Ambiguity Sources,” in 16th International Working Conference, REFSQ, 2010, vol. 6182, pp. 218–232.
S. F. Tjong and D. M. Berry, “The design of SREE - A prototype potential ambiguity finder for requirements specifications and lessons learned,” Lect. Notes Comput. Sci. (including Subser. Lect. Notes Artif. Intell. Lect. Notes Bioinformatics), vol. 7830 LNCS, pp. 80–95, 2013.
A. B. Rojas, G. B. Sliesarieva, U. D. C. Rica, S. Jos, and C. Rica, “Automated Detection of Language Issues Affecting Accuracy , Ambiguity and Verifiability in Software Requirements Written in Natural Language,” in Proceeding of the NAACL HLT 2010 Young Investigators Workshop on Computational Approaches to Languages of the Americas, 2010, no. June, pp. 100–108.
R. Li, K. He, and H. Chen, “From natural language requirements to requirement ontologies,” 2010 2nd Int. Conf. Futur. Comput. Commun., pp. V3-755-V3-758, 2010.
G. Lami, S. Gnesi, F. Fabbrini, M. Fusani, and G. Trentanni, “An Automatic Tool for the Analysis of Natural Language Requirements.”.
Downloads
Published
How to Cite
Issue
Section
License
TRANSFER OF COPYRIGHT AGREEMENT
The manuscript is herewith submitted for publication in the Journal of Telecommunication, Electronic and Computer Engineering (JTEC). It has not been published before, and it is not under consideration for publication in any other journals. It contains no material that is scandalous, obscene, libelous or otherwise contrary to law. When the manuscript is accepted for publication, I, as the author, hereby agree to transfer to JTEC, all rights including those pertaining to electronic forms and transmissions, under existing copyright laws, except for the following, which the author(s) specifically retain(s):
- All proprietary right other than copyright, such as patent rights
- The right to make further copies of all or part of the published article for my use in classroom teaching
- The right to reuse all or part of this manuscript in a compilation of my own works or in a textbook of which I am the author; and
- The right to make copies of the published work for internal distribution within the institution that employs me
I agree that copies made under these circumstances will continue to carry the copyright notice that appears in the original published work. I agree to inform my co-authors, if any, of the above terms. I certify that I have obtained written permission for the use of text, tables, and/or illustrations from any copyrighted source(s), and I agree to supply such written permission(s) to JTEC upon request.