Detecting Incoherence Requirements in Large Documents
Abstract
The different protagonists involved in requirement production is a source of mismatches, inconsistencies, incoherence and redundancies. Indeed, stakeholders, technical writers, managers, and then, users and manufacturers, all play different roles and have different views on these requirements. These discrepancies are developed in technical writing principles (Schriever, 1989), (Unwalla, 2004), (Weiss, 1991) and (Kuhn 2014) where a large synthesis is proposed. In an attempt to overcome these problems, most industrial sectors have defined authoring recommendations (e.g. IEEE 830 and variants, ISO 29148), methods (IREB Handbook of Requirement Modelling (Cziharz et al. 2016) and Elicitation (Häußer et al., 2019)) and tools to elaborate, structure and write requirements of various types. These specify how correct requirements should be elaborated. For that purpose, they provide attribute elicitation techniques and discuss the iterative application of requirements processes within life cycles. The result is easier traceability, control and update.