Automated class diagram elicitation using intermediate use case template
Abstract Class diagrams, being more illustrative, provide an easier way of understanding software requirements compared to use case descriptions. Both manual and automated methods are used for the extraction of class diagrams from requirements. The automated techniques employ certain extraction rule...
Saved in:
| Main Authors: | , , |
|---|---|
| Format: | Article |
| Language: | English |
| Published: |
Wiley
2021-02-01
|
| Series: | IET Software |
| Subjects: | |
| Online Access: | https://doi.org/10.1049/sfw2.12010 |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
| _version_ | 1832546744466931712 |
|---|---|
| author | Shweta Ratna Sanyal Bibhas Ghoshal |
| author_facet | Shweta Ratna Sanyal Bibhas Ghoshal |
| author_sort | Shweta |
| collection | DOAJ |
| description | Abstract Class diagrams, being more illustrative, provide an easier way of understanding software requirements compared to use case descriptions. Both manual and automated methods are used for the extraction of class diagrams from requirements. The automated techniques employ certain extraction rules and natural language processing methods. Each use case description template introduces a small set of extraction rules. However, when all types of templates are considered, the number of rules becomes large and the procedure becomes tedious. Thus, researchers restricted the class diagram extraction procedure to some specific use case description templates. However, such a restriction negatively affects the software developers as they get restricted to working with only limited templates. The proposed work in this paper strives to remove this restriction on developers by introducing an intermediate template. The traditional use case description templates get transformed into the intermediate template and the rule extraction procedure is then applied to this intermediate template. This reduces the total number of extraction rules and hence, brings down the extraction complexity. The class diagrams extracted from use case description templates of different domains using proposed technique show more accuracy in terms of completeness and correctness when compared with the state of the art approaches. |
| format | Article |
| id | doaj-art-87f3dfe4009f46ce84a38a0985980271 |
| institution | Kabale University |
| issn | 1751-8806 1751-8814 |
| language | English |
| publishDate | 2021-02-01 |
| publisher | Wiley |
| record_format | Article |
| series | IET Software |
| spelling | doaj-art-87f3dfe4009f46ce84a38a09859802712025-02-03T06:47:26ZengWileyIET Software1751-88061751-88142021-02-01151254210.1049/sfw2.12010Automated class diagram elicitation using intermediate use case templateShweta0Ratna Sanyal1Bibhas Ghoshal2Information Technology Indian Institute of Information Technology Allahabad Allahabad Uttar Pradesh IndiaNIIT University Alwar Rajasthan IndiaInformation Technology Indian Institute of Information Technology Allahabad Allahabad Uttar Pradesh IndiaAbstract Class diagrams, being more illustrative, provide an easier way of understanding software requirements compared to use case descriptions. Both manual and automated methods are used for the extraction of class diagrams from requirements. The automated techniques employ certain extraction rules and natural language processing methods. Each use case description template introduces a small set of extraction rules. However, when all types of templates are considered, the number of rules becomes large and the procedure becomes tedious. Thus, researchers restricted the class diagram extraction procedure to some specific use case description templates. However, such a restriction negatively affects the software developers as they get restricted to working with only limited templates. The proposed work in this paper strives to remove this restriction on developers by introducing an intermediate template. The traditional use case description templates get transformed into the intermediate template and the rule extraction procedure is then applied to this intermediate template. This reduces the total number of extraction rules and hence, brings down the extraction complexity. The class diagrams extracted from use case description templates of different domains using proposed technique show more accuracy in terms of completeness and correctness when compared with the state of the art approaches.https://doi.org/10.1049/sfw2.12010diagramsformal specificationnatural language processing |
| spellingShingle | Shweta Ratna Sanyal Bibhas Ghoshal Automated class diagram elicitation using intermediate use case template IET Software diagrams formal specification natural language processing |
| title | Automated class diagram elicitation using intermediate use case template |
| title_full | Automated class diagram elicitation using intermediate use case template |
| title_fullStr | Automated class diagram elicitation using intermediate use case template |
| title_full_unstemmed | Automated class diagram elicitation using intermediate use case template |
| title_short | Automated class diagram elicitation using intermediate use case template |
| title_sort | automated class diagram elicitation using intermediate use case template |
| topic | diagrams formal specification natural language processing |
| url | https://doi.org/10.1049/sfw2.12010 |
| work_keys_str_mv | AT shweta automatedclassdiagramelicitationusingintermediateusecasetemplate AT ratnasanyal automatedclassdiagramelicitationusingintermediateusecasetemplate AT bibhasghoshal automatedclassdiagramelicitationusingintermediateusecasetemplate |