What can a business analyst use to track requirements documentation?

A version control system is a tool specifically designed to manage and track changes to documents and other collections of information over time. For a business analyst, this is crucial for managing requirements documentation as it evolves. It allows for tracking revisions, identifying who made changes and when, comparing different versions, and reverting to previous states if necessary. This ensures the integrity and traceability of the requirements throughout the project lifecycle.

A. An affinity diagram is a tool used to organize a large number of ideas into groups based on their natural relationships.
B. A data dictionary defines data elements; it is a piece of documentation itself, not a system for tracking it.
C. A business rules matrix is a tool for documenting and analyzing business rules, not for managing document versions.

Project Management Institute. (2017). The PMI Guide to Business Analysis. Section 6.4.2, Store Requirements, p. 186. (This section describes the need for a system to store and manage product information, with version control being a key feature of such systems).

Wiegers, K., & Beatty, J. (2013). Software Requirements (3rd ed.). Microsoft Press. Chapter 19, Change Happens, discusses version control as a fundamental practice for managing requirements artifacts. (While a commercial press, this is a foundational text often cited in academic contexts for software engineering and business analysis).