Question

Which of the following is not the limitation of document-based approach to developing and managing requirements?

A. It's difficult to keep the documents current and synchronized.
B. Communicating changes to all affected team members is a manual process
C. It's not easy to store supplementary information-attributes-about each requirement
D. maintain a history of the changes made to each requirement

Answer 1

Option D, 'maintain a history of the changes made to each requirement' is not a limitation of the document-based approach, as document versioning allows for tracking of historical changes.

Step-by-step explanation:

The limitation of a document-based approach to managing requirements is A. It's difficult to keep the documents current and synchronized. This challenge arises from the static nature of documents, which can become outdated quickly as project requirements change. The need to manually update and disseminate these documents can lead to information silos and misalignment among team members. In contrast, B. Communicating changes to all affected team members is indeed a limitation of the document-based approach, as it relies on manual dissemination of information, which can be slow and error-prone. Similarly, C. Storing supplementary information or attributes for each requirement is also a challenge in document-based systems, where such details may not be readily accommodated. However, D. Maintaining a history of the changes made to each requirement is typically feasible with a document-based approach, as documents can be versioned to track changes over time.