Chapter 14. To Duplicate or Not to Duplicate
It’s not unusual to discover that you need to replicate a specific requirement or piece of requirements-related information in multiple places in your project documentation. This poses a problem that has no perfect solution. On the one hand, it’s convenient to be able to view and print all the information associated with a specific issue, topic, function, feature, or use case in a single location. This lets you treat that block of information as a self-contained package. A developer who is responsible for implementing that block will have all the necessary information grouped together.
On the other hand, duplicating information ...
Get More About Software Requirements: Thorny Issues and Practical Advice now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
