Generating UML Class Diagram from Natural Language Requirements: A Survey of Approaches and Techniques

Abdelnabi, Esra A.; Maatuk, Abdelsalam M.; Hagal, Mohammed

doi:10.1109/mi-sta52233.2021.9464433

Cited by 16 publications

(14 citation statements)

References 20 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Esra et al [3] conducted another systematic mapping study on the techniques and approaches of NL to UML Class diagram. However, our analysis is neither limited to class diagrams nor mapping the techniques and approaches.…”

Section: Inclusion and Exclusionmentioning

confidence: 99%

“…Besides, there are a few approaches that are comparatively recent and are fully automated. Still, these approaches are working under some constrained input such as restricted NL or some particular form of texts [3]. A previous work takes informal NL text requirements and generates UML Use Case and Activity Diagrams without any developer's intervention or assistance [4].…”

Section: Introductionmentioning

confidence: 99%

“…Many tools and approaches have been proposed and developed to extract information from natural language text to generate UML diagrams. However, natural language processing has many problems such as ambiguity, uncertainty, incompleteness, and incoherence [3]. Existing approaches perform poorly at times because of this ambiguity of NL.…”

Section: Introductionmentioning

confidence: 99%

“…Though there are some new solutions, they still require more rules to increase the domain knowledge, which is an another problem [3], [7]. So, our work will provide a conceptual framework showing an overview of using rule-based Most frequent words as query terms…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Automatic Transformation of Natural to Unified Modeling Language: A Systematic Review

Ahmed,

Eisty

2022

Preprint

View full text Add to dashboard Cite

Context: Processing Software Requirement Specifications (SRS) manually takes a much longer time for requirement analysts in software engineering. Researchers have been working on making an automatic approach to ease this task. Most of the existing approaches require some intervention from an analyst or are challenging to use. Some automatic and semi-automatic approaches were developed based on heuristic rules or machine learning algorithms. However, there are various constraints to the existing approaches of UML generation, such as restriction on ambiguity, length or structure, anaphora, incompleteness, atomicity of input text, requirements of domain ontology, etc. . Objective: This study aims to better understand the effectiveness of existing systems and provide a conceptual framework with further improvement guidelines. Method: We performed a systematic literature review (SLR). We conducted our study selection into two phases and selected 70 papers. We conducted quantitative and qualitative analyses by manually extracting information, cross-checking, and validating our findings. Result: We described the existing approaches and revealed the issues observed in these works. We identified and clustered both the limitations and benefits of selected articles. Conclusion: This research upholds the necessity of a common dataset and evaluation framework to extend the research consistently. It also describes the significance of natural language processing obstacles researchers face. In addition, it creates a path forward for future research.

show abstract

Section: Inclusion and Exclusionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Automatic Transformation of Natural to Unified Modeling Language: A Systematic Review

Ahmed,

Eisty

2022

Preprint

View full text Add to dashboard Cite

show abstract

“…Besides, it relates to the analysis since it is involved with detecting problems associated with the SRS, i.e., inconsistencies, incompleteness and ambiguities [2] [43]. Inconsistent requirements are requirements that are stated and described differently at different places in SRS, whereas ambiguous requirements referred to as one requirement has multiple perceptions and incomplete requirement, which refers to a requirement that does not convey a complete and meaningful requirement [43] [44].…”

Section: Introductionmentioning

confidence: 99%

A Framework for Aspectual Requirements Validation: an Experimental Study

Maatuk¹,

Alshareef²,

Abdelaziz³

2021

IJSEA

View full text Add to dashboard Cite

Requirements engineering is a discipline of software engineering that is concerned with the identification and handling of user and system requirements. Aspect-Oriented Requirements Engineering (AORE) extends the existing requirements engineering approaches to cope with the issue of tangling and scattering resulted from crosscutting concerns. Crosscutting concerns are considered as potential aspects and can lead to the phenomena “tyranny of the dominant decomposition”. Requirements-level aspects are responsible for producing scattered and tangled descriptions of requirements in the requirements document. Validation of requirements artefacts is an essential task in software development. This task ensures that requirements are correct and valid in terms of completeness and consistency, hence, reducing the development cost, maintenance and establish an approximately correct estimate of effort and completion time of the project. In this paper, we present a validation framework to validate the aspectual requirements and the crosscutting relationship of concerns that are resulted from the requirements engineering phase. The proposed framework comprises a high-level and low-level validation to implement on software requirements specification (SRS). The high-level validation validates the concerns with stakeholders, whereas the low-level validation validates the aspectual requirement by requirements engineers and analysts using a checklist. The approach has been evaluated using an experimental study on two AORE approaches. The approaches are viewpoint-based called AORE with ArCaDe and lexical analysis based on Theme/Doc approach. The results obtained from the study demonstrate that the proposed framework is an effective validation model for AORE artefacts.

show abstract

Development and Validation of AI-Driven NLP Algorithms for Chatbots in Requirement Engineering

Seidel,

Späthe

2024

Communications in Computer and Information Science

View full text Add to dashboard Cite

Generating UML Class Diagram from Natural Language Requirements: A Survey of Approaches and Techniques

Cited by 16 publications

References 20 publications

Automatic Transformation of Natural to Unified Modeling Language: A Systematic Review

Automatic Transformation of Natural to Unified Modeling Language: A Systematic Review

A Framework for Aspectual Requirements Validation: an Experimental Study

Development and Validation of AI-Driven NLP Algorithms for Chatbots in Requirement Engineering

Contact Info

Product

Resources

About