2011
DOI: 10.1016/j.jss.2011.02.025
|View full text |Cite
|
Sign up to set email alerts
|

Parsed use case descriptions as a basis for object-oriented class model generation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
24
0

Year Published

2014
2014
2023
2023

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 40 publications
(24 citation statements)
references
References 16 publications
0
24
0
Order By: Relevance
“…The target is models and UML diagrams, for instance, creation of use case diagrams [21] and UML Activity Diagrams using identification of simple verbal sentences [22] from textual requirements in Arabic. UML class diagrams from textual requirements [23], and from use case descriptions [24] are created in English. Researchers also analyse textual user requirements in natural language and requirements used by engineering diagrams to create the Use Case Path model, the Hybrid Activity Diagram model and the Domain model [25].…”
Section: Related Workmentioning
confidence: 99%
“…The target is models and UML diagrams, for instance, creation of use case diagrams [21] and UML Activity Diagrams using identification of simple verbal sentences [22] from textual requirements in Arabic. UML class diagrams from textual requirements [23], and from use case descriptions [24] are created in English. Researchers also analyse textual user requirements in natural language and requirements used by engineering diagrams to create the Use Case Path model, the Hybrid Activity Diagram model and the Domain model [25].…”
Section: Related Workmentioning
confidence: 99%
“…To validate their approach the authors implemented a tool named ABCD. Elbendak et al [8] present a tool, Class-Gen, which can partially automate the identification of objects/classes from NL requirements specifications for object identification. Ibrahim et al [11] propose a method and a tool to facilitate requirements analysis process and class diagram extraction from textual requirements supporting NLP techniques.…”
Section: Related Workmentioning
confidence: 99%
“…The transition from requirements expressed in NL to a domain model is an important step to obtain a precise and analyzable specification [20]. Automated model extraction from NL requirements has been studied for a long time, with a large body of literature already existing in the area such as [7], [8], [11], [14], [18], [21].…”
Section: Introductionmentioning
confidence: 99%
“…Therefore, the kind of automatic support to provide for requirements formalization, as well as how to provide it, is a crucial problem to be solved in order for software industry to benefit from the formal specification technique. Compared with formal notation, natural language is easier to use and a number of researchers are devoted to automatic or semi-automatic transformation of informal descriptions into formal specifications [3]- [5]. However, most of these transformation methods largely depend on the Natural Language Processing technique which is still facing the problem of the great amount of ambiguity issues at every linguistic level of natural language [5].…”
Section: Introductionmentioning
confidence: 99%
“…Compared with formal notation, natural language is easier to use and a number of researchers are devoted to automatic or semi-automatic transformation of informal descriptions into formal specifications [3]- [5]. However, most of these transformation methods largely depend on the Natural Language Processing technique which is still facing the problem of the great amount of ambiguity issues at every linguistic level of natural language [5]. Although Controlled Natural Languages are proposed to reduce these ambiguities to some extent by restricting the grammar and vocabulary [6], [7], they need to be studied and their completeness is hard to guarantee.…”
Section: Introductionmentioning
confidence: 99%