Early phases of software development are known to be problematic,
difficult to manage and errors occurring during these phases are
expensive to correct. Many systems have been developed to aid the
transition from informal Natural Language requirements to semi-structured
or formal specifications. Furthermore, consistency checking is seen
by many software engineers as the solution to reduce the number of
errors occurring during the software development life cycle and allow
early verification and validation of software systems. However, this
is confined to the models developed during analysis and design and
fails to include the early Natural Language requirements. This excludes
proper user involvement and creates a gap between the original requirements
and the updated and modified models and implementations of the system.
To improve this process, we propose a system that generates Natural
Language specifications from UML class diagrams. We first investigate
the variation of the input language used in naming the components
of a class diagram based on the study of a large number of examples
from the literature and then develop rules for removing ambiguities
in the subset of Natural Language used within UML. We use WordNet,
a linguistic ontology, to disambiguate the lexical structures of
the UML string names and generate semantically sound sentences. Our
system is developed in Java and is tested on an independent though
academic case study.
Abstract: This approach/work is mainly used to close the gap between
the original requirements and the updated and modified models and
implementations of the system. They propose a system that generates
Natural Language specifications from UML class diagrams. The work
is implemented in Java and uses WordNet, alinguistic ontology.
Introduction
1.1 The introduction is very nice written. Many points that i didn't
mention. Cost reduction in early phase of software development, requirements
tend to evolve over time naming the references.
Common:
You get a good insight and overview of how such a Generating NL system
works (process workflow). The generated NL looks like OO-oriented
sentences and is accordingly read. Perhaps it is not really industr-usable
(see evaluation part).
Compared to SALE MX Reverse:
We have additional thematic roles originated from a specification.
Thematic roles have to be specified for generating a SALE-graph,
which is our particular attention.
%0 Journal Article
%1 Meziane2008
%A Meziane, Farid
%A Athanasakis, Nikos
%A Ananiadou, Sophia
%D 2008
%J Requirements Engineering
%K NT2OD diagrams language linux specifications toread uml
%N 1
%P 1--18
%R http://dx.doi.org/10.1007/s00766-007-0054-0
%T Generating Natural Language specifications from UML class diagrams
%V 13
%X Early phases of software development are known to be problematic,
difficult to manage and errors occurring during these phases are
expensive to correct. Many systems have been developed to aid the
transition from informal Natural Language requirements to semi-structured
or formal specifications. Furthermore, consistency checking is seen
by many software engineers as the solution to reduce the number of
errors occurring during the software development life cycle and allow
early verification and validation of software systems. However, this
is confined to the models developed during analysis and design and
fails to include the early Natural Language requirements. This excludes
proper user involvement and creates a gap between the original requirements
and the updated and modified models and implementations of the system.
To improve this process, we propose a system that generates Natural
Language specifications from UML class diagrams. We first investigate
the variation of the input language used in naming the components
of a class diagram based on the study of a large number of examples
from the literature and then develop rules for removing ambiguities
in the subset of Natural Language used within UML. We use WordNet,
a linguistic ontology, to disambiguate the lexical structures of
the UML string names and generate semantically sound sentences. Our
system is developed in Java and is tested on an independent though
academic case study.
@article{Meziane2008,
abstract = {Early phases of software development are known to be problematic,
difficult to manage and errors occurring during these phases are
expensive to correct. Many systems have been developed to aid the
transition from informal Natural Language requirements to semi-structured
or formal specifications. Furthermore, consistency checking is seen
by many software engineers as the solution to reduce the number of
errors occurring during the software development life cycle and allow
early verification and validation of software systems. However, this
is confined to the models developed during analysis and design and
fails to include the early Natural Language requirements. This excludes
proper user involvement and creates a gap between the original requirements
and the updated and modified models and implementations of the system.
To improve this process, we propose a system that generates Natural
Language specifications from UML class diagrams. We first investigate
the variation of the input language used in naming the components
of a class diagram based on the study of a large number of examples
from the literature and then develop rules for removing ambiguities
in the subset of Natural Language used within UML. We use WordNet,
a linguistic ontology, to disambiguate the lexical structures of
the UML string names and generate semantically sound sentences. Our
system is developed in Java and is tested on an independent though
academic case study.},
added-at = {2009-11-19T17:33:12.000+0100},
author = {Meziane, Farid and Athanasakis, Nikos and Ananiadou, Sophia},
biburl = {https://www.bibsonomy.org/bibtex/2aa6e5802c7fa927dd6d80784256a7d33/butonic},
citeulike-article-id = {2268813},
doi = {http://dx.doi.org/10.1007/s00766-007-0054-0},
file = {:C\:\\Users\\Bugra\\Documents\\Studium\\DA\\Literatur\\Meziane2008.pdf:PDF},
interhash = {8363c801f8ab1b7d7a06442f6668cb58},
intrahash = {aa6e5802c7fa927dd6d80784256a7d33},
journal = {Requirements Engineering},
keywords = {NT2OD diagrams language linux specifications toread uml},
month = {January},
number = 1,
owner = {sjk},
pages = {1--18},
posted-at = {2008-01-21 13:37:00},
priority = {2},
review = {Abstract: This approach/work is mainly used to close the gap between
the original requirements and the updated and modified models and
implementations of the system. They propose a system that generates
Natural Language specifications from UML class diagrams. The work
is implemented in Java and uses WordNet, alinguistic ontology.
Introduction
1.1 The introduction is very nice written. Many points that i didn't
mention. Cost reduction in early phase of software development, requirements
tend to evolve over time naming the references.
Common:
You get a good insight and overview of how such a Generating NL system
works (process workflow). The generated NL looks like OO-oriented
sentences and is accordingly read. Perhaps it is not really industr-usable
(see evaluation part).
Compared to SALE MX Reverse:
We have additional thematic roles originated from a specification.
Thematic roles have to be specified for generating a SALE-graph,
which is our particular attention.},
timestamp = {2009-11-19T17:33:12.000+0100},
title = {Generating Natural Language specifications from UML class diagrams},
volume = 13,
year = 2008
}