UML generator – use case and class diagram generation from text requirements

Narawita, Chamitha Ramal; Vidanage, Kaneeka

doi:10.4038/icter.v10i1.7182

Cited by 14 publications

(11 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…To automate the task of the modeling of SRs, various methods have been developed. For example, Narawita and Vidanage [12] used "natural language processing" to generate the UML diagrams form the textual requirements so that the system analyst can save time.…”

Section: Methods For Modeling the Software Requirementsmentioning

confidence: 99%

“…These requirements are modeled by the UCDs in Figures 8, 9, and 10. The same set of requirements is modeled by the class diagrams in Figures 11,12,13, respectively. In the case of the large dataset of an IES [27], we obtained the same ranking order of the FRs that we obtained for the small dataset, i.e., F R 10 , F R 1 , and F R 6 .…”

Section: Step 4: Computation Of Ranking Values Of Frs Using Fuzzy Topsismentioning

confidence: 99%

See 1 more Smart Citation

Software requirements modeling from the selected set of requirements using fuzzy based approach

Arif

Mohammad

Sadiq

2022

ECTI-CIT Transactions

View full text Add to dashboard Cite

Software requirements (SRs) modeling is one of the sub-processes of requirements engineering whose aim is to model and design the SRs before the development of a project. Different techniques are employed for representing the SRs using goal concepts, unified modeling language, etc. There could be a large number of SRs after the completion of the requirements elicitation process. It is not practical to model the complete set of the identified SRs because of the cost, time, and other limitations of an organization. There should be some systematic methodology to identify and select those SRs for modeling that need to be implemented during the software development process. The selection of SRs from the list of the elicited requirements is a multi-criteria decision-making process. In this process different stakeholders participate in the selection of the SRs. Linguistic variables may be used by the stakeholders to specify the preferences of SRs. To deal with this issue, a method has been proposed using a fuzzy based approach so that the selected set of SRs can be modeled and implemented during the development phase. The proposed method is explained by considering the small and large set of SRs for an institute examination system. The ranking value of the functional requirements of an examination system is computed. Based on the ranking order, top three requirements are modeled using use-case diagrams (UCDs) and class diagrams. It is found that both diagrams represent different information about the requirements of an examination system and there is no overlap in the information captured through UCDs and class diagrams.

show abstract

Section: Methods For Modeling the Software Requirementsmentioning

confidence: 99%

Section: Step 4: Computation Of Ranking Values Of Frs Using Fuzzy Topsismentioning

confidence: 99%

Software requirements modeling from the selected set of requirements using fuzzy based approach

Arif

Mohammad

Sadiq

2022

ECTI-CIT Transactions

View full text Add to dashboard Cite

show abstract

“…The work in [12] proposed a tool to generate a class diagram from requirements, then generate code from class. Chamitha et al [13] proposed a workflow for generating use cases and class diagrams. They used web browsers to enter the text, finally process it using NL processing techniques, and then generate candidate diagram elements.…”

Section: From Requirements To Uml Transformationmentioning

confidence: 99%

“…To minimize the errors that arise in a traditional system Do not cover traceability and consistency [10] Use Case Diagram Facilitate the requirements analysis process Do not cover traceability and consistency [11] Activity and Sequence Diagrams Manual transformation from requirements to UML Do not cover traceability and consistency. It also missing automation [12] Class and Sequence Diagrams Supporting the Analysis stage of software development Do not cover traceability and consistency [13] Use Case and Class Diagrams…”

Section: Requirements Traceabilitymentioning

confidence: 99%

“…The paper covers moving from SRS to Software Architecture Design Description (SADD) in a semiautomatically to make bi-directional traceability in a consistent matter to ensure requirements consistent with the design. In the literature review section, lots of research were reviewed; these researches cover generation design diagrams from requirements without considering consistency and traceability [7]- [13], [15]. There is some research cover traceability but did not deal with consistency management [16]- [25].…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

Requirements and Design Consistency: A Bi-directional Traceability and Natural Language Processing Assisted Approach

Omer

Sahraoui

Mahmoud

et al. 2021

EJENG

View full text Add to dashboard Cite

phase in the Software Development Life Cycle (SDLC). The design phase follows it. Traceability is one of the core concepts in software engineering; it is used to follow updates to make consistent items. This paper aimed to cover consistency through bi-directional traceability between requirements and design phase in a semi-automatic way. The Natural Language Processing (NLP) was used to analyze the requirements text and generate a class diagram; then, the generated items can be traced back to requirements. We developed a novel process to support consistency and bi-directional traceability. To ensure our proposed process's practical applicability, we implemented a tool named as Requirements and Design Bi-directional Traceability (RDBT). RDTB receives textual format requirements, performs NLP tasks (Tokenization, Part-of-Speech Tagging, etc.), generates UML class diagram, and finally performs traceability management to ensure consistency of requirements and UML class diagram. The work evaluation reveals good results, which indicates it can be used efficiently as a guide to generate the UML class diagram semi-automatically and manage traceability.

show abstract

Intelligent Software Engineering: The Significance of Artificial Intelligence Techniques in Enhancing Software Development Lifecycle Processes

Kulkarni¹,

Kolhe²,

Kulkarni³

2022

Lecture Notes in Networks and Systems

View full text Add to dashboard Cite

UML generator – use case and class diagram generation from text requirements

Abstract: Abstract-

Cited by 14 publications

References 5 publications

Software requirements modeling from the selected set of requirements using fuzzy based approach

Software requirements modeling from the selected set of requirements using fuzzy based approach

Requirements and Design Consistency: A Bi-directional Traceability and Natural Language Processing Assisted Approach

Intelligent Software Engineering: The Significance of Artificial Intelligence Techniques in Enhancing Software Development Lifecycle Processes

Contact Info

Product

Resources

About