Automatic Transition of Natural Language Software Requirements Specification into Formal Presentation

Abstract

Abstract. Software requirements specification is a critical activity of the software process, as errors at this stage inevitably lead to problems later on in system design and implementation. The requirements are written in natural language, with the potential for ambiguity, contradiction or misunderstanding, or simply an inability of developers to deal with a large amount of information. This paper proposes a methodology for the natural language processing of textual descriptions of the requirements of an unlimited natural language and their automatic mapping to the object-oriented analysis model.

Proposing the new Algorithm and Technique Development for Integrating Web Table Extraction and Building a Mashup

“…For further works, we have planned to complete the available features in the Xtractorz GUI with JQuery facility and the NLP (Natural Language Processing) to further collaborate semantic meaning of the attributes or the table contents (cells) which are extracted (Ilieva and Ormandjieva, 2005).…”

“…Using the method in writing mathematical notion (Gatterbauer et al, 2007;Ilieva and Ormandjieva, 2005), in Table 1 we can see some notions and the explanations of Xtractorz algorithm rules.…”

Ontology-based Program Comprehension Tool Supporting Website Architectural Evolution

“…Most of this research has focused on analysing texts at the specification level, e.g., in order to automatically convert use case descriptions into a formal representation [18,19] or detect inconsistent requirements [20]. In contrast with these works, we aim to support the complete software documentation life-cycle, from white papers over design and implementation documents to inline code texts (e.g., JavaDoc).…”

A Software Requirement Engineering Technique Using OOADA-RE and CSC for IoT Based Healthcare Applications

“…M.G Illieva et al . [5] introduced another approach where the used natural language processing to remove ambiguity, contradiction in the requirements specifications and to map them to UML diagrams.…”