What should be done with a requirement number after it has been published?

Once a requirement number has been published, it is important to maintain its integrity and ensure consistency throughout the project lifecycle. Changing a published requirement can lead to confusion and misalignment among team members, as well as potential impacts on project documentation and traceability. By not changing the requirement number, teams can confidently refer back to it throughout the development process, ensuring clear communication and maintaining a consistent understanding of what was originally agreed upon. This practice helps in managing scopes, variations, and helps in tracking changes effectively when needed.

Archiving a requirement (as suggested in another choice) usually occurs at a later stage, after the requirement has been implemented or is no longer relevant. In contrast, maintaining the published status and not changing it directly supports project clarity and helps safeguard against the introduction of errors that could arise from revisions.