Which two essential tasks for requirements management are least supported by text processing tools?

The task of requirements tracing is least supported by text processing tools because tracing requires a structured way to link related requirements, often involving multiple documentation types and complex relationships. Text processing tools are primarily designed for creating and editing documents, which means they lack the specialized features needed for tracking dependencies and relationships between requirements efficiently.

Requirements tracing typically involves mapping requirements back to stakeholder needs and forward to design and testing artefacts; this necessitates the use of specialized requirements management tools that can handle the intricate relationships and provide visual aids for understanding these connections. Text processing tools may not provide the necessary functionalities to maintain such traceability effectively, such as automated updates, visual representations of links, or change impact analysis.

In contrast, version management of individual requirements, generation of result documents, and creation of graphic models are tasks that can be facilitated by text processing tools. These tools can manage versioning through document editing capabilities, generate output documents based on text formatting, and allow for basic graphic model creation, although they may not provide the depth of functionality that dedicated requirements management tools offer.