A: Rewriting requirements independent of the solution design is not a good option because it would be redundant and time-consuming. The existing solution documents already contain the necessary information for the solution consultants to customize the system. The BA only needs to add some additional attributes for the new and changed requirements, not rewrite them from scratch.
B: Entering the information in the company's change management system is not a good option because it would not be accessible or useful for the solution consultants. The change management system is typically used for tracking and approving changes to the existing system, not for defining and documenting requirements for a new system. The BA needs to communicate the requirements to the solution consultants in a format that they can understand and use for customization.
C: Adding the attributes to the original requirements catalog and changing requirements is not a good option because it would modify the as-is solution documents, which may be needed for reference or comparison purposes. The BA should not alter the existing solution documents without the consent of the solution consultants, who created and own them. The BA should create a separate document for the new and changed requirements, and link them to the original requirements catalog if necessary.
D: Creating a new workbook of requirements with necessary attributes is the best option because it would allow the BA to capture and manage the information for the new and changed requirements in a structured and consistent way. The BA can use a spreadsheet or a similar tool to create a new workbook of requirements, and include the additional attributes such as the source, reason, complexity, and priority of change. The BA can also reuse some of the requirements in other work by copying or referencing them in the workbook. The BA can share the workbook with the solution consultants, who can use it to customize the system according to the PGA needs.