This paper covers the recognition of textual entailment by means of different approaches based on lexical similarities and syntactic trees. These approaches are easily portable to other languages. We present the achieved results for each individual approach and we propose a simple voting strategy between these approaches and our previous system (presented in Second PASCAL Recognising Textual En...

Systems designed to recognize textual entailment typically employ both syntax and semantics. Our goal in this paper is to explore the degree to which semantics alone can be used to accurately detect entailment so that we can gain a better understanding of this single component within an entailment system. This paper reports the knowledge-bases considered and selected for person names, locations...

Most Web-based Q/A systems work by finding pages that contain an explicit answer to a question. These systems are helpless if the answer has to be inferred from multiple sentences, possibly on different pages. To solve this problem, we introduce the HOLMES system, which utilizes textual inference (TI) over tuples extracted from text. Whereas previous work on TI (e.g., the literature on textual ...

In the logic approach to Recognizing Textual Entailment, identifying phrase-tophrase semantic relations is still an unsolved problem. Resources such as the Paraphrase Database offer limited coverage despite their large size whereas unsupervised distributional models of meaning often fail to recognize phrasal entailments. We propose to map phrases to their visual denotations and compare their me...

The majority of artifacts created during software development are representations of programs in textual syntax. Although graphical descriptions are becoming more widespread, source code is still indispensable. To obtain programs that behave correctly and adhere to given coding conventions, source code must be analyzed — preferably using automated tools. Building source code analyzers has a lon...

Formal methods are increasingly used in software engineering. They offer a formal frame that guarentees the correctness of developments. However, they use complex notations that might be difficult to understand for unaccustomed users. It thus becomes interesting to formally specify the core components of a language, implement a provably correct development, and manipulate its components in a gr...

This article describes transformations of software requirements. We start from requirements (use cases) in textual form. These are subsequently encoded precisely in UML 2.0 Sequence Diagrams (SD) by a modelling expert. The SD model is automatically transformed back into textual form to allow the requirements producer to check correct interpretation. Once the latter is satisfied, the SD model is...

This study aimed to explore the function and frequency of textual metadiscourse markers (MDMs) in scientific English and Persian texts. Based on the qualitative and quantitative analysis of textual markers characterizing the selected genre, four different textbooks, two written in English and two in Persian were analyzed to identify the textual metadiscourse categories (including logical marker...

The requirements specification phase is one of the most important during software development. In many cases, its outcome takes a form use-case model, which consists diagrams and supplementary specifications. document used by various stakeholders, starting from customers or their representatives, through architects, developers to testers. Each role may have specific preferences for specificatio...