Four dark corners of requirements engineering
ACM Transactions on Software Engineering and Methodology (TOSEM)
AbstFinder, A Prototype Natural Language Text Abstraction Finder for Use in Requirements Elicitation
Automated Software Engineering
Attempto Controlled English (ACE)Language ManualVersion 3.0
Attempto Controlled English (ACE)Language ManualVersion 3.0
Head-driven statistical models for natural language parsing
Head-driven statistical models for natural language parsing
Ontology as a Requirements Engineering Product
RE '03 Proceedings of the 11th IEEE International Conference on Requirements Engineering
Automatic discovery of term similarities using pattern mining
COMPUTERM '02 COLING-02 on COMPUTERM 2002: second international workshop on computational terminology - Volume 14
Natural language reporting for ETL processes
Proceedings of the ACM 11th international workshop on Data warehousing and OLAP
Innovations for Requirement Analysis. From Stakeholders' Needs to Formal Designs
Semantic enriching of natural language texts with automatic thematic role annotation
NLDB'10 Proceedings of the Natural language processing and information systems, and 15th international conference on Applications of natural language to information systems
Canadian AI'11 Proceedings of the 24th Canadian conference on Advances in artificial intelligence
NLDB'09 Proceedings of the 14th international conference on Applications of Natural Language to Information Systems
Validation of requirements for hybrid systems: A formal approach
ACM Transactions on Software Engineering and Methodology (TOSEM)
Ontological text mining of software documents
NLDB'07 Proceedings of the 12th international conference on Applications of Natural Language to Information Systems
Flexible and customizable NL representation of requirements for ETL processes
NLDB'07 Proceedings of the 12th international conference on Applications of Natural Language to Information Systems
| Hi-index | 0.00 |
Requirements engineering is the Achilles' heel of the whole software development process, because requirements documents are often inconsistent and incomplete. Misunderstandings and errors of the requirements engineering phase propagate to later development phases and can potentially lead to a project failure. A promising way to overcome misunderstandings is to extract and validate terms used in requirements documents and relations between these terms. This position paper gives an overview of the existing terminology extraction methods and shows how they can be integrated to reach a comprehensive text analysis approach. It shows how the integrated method would both detect inconsistencies in the requirements document and extract an ontology after elimination of inconsistencies. This integrated method would be more reliable than every of its single constituents.