Hi

I have a question that I didn't find the answer at Pega PDN... can somebody help me? Tks!

Which of the following is NOT a reason why issues related to specifications are tracked in an issue tracking system?

1. It gives the Business Analysts a tool from which to analyze the artifacts they generate making it easier to determine trends and create a continuous improvement process to get better quality results.
2. It gives the Lead Systems Architects a useful mechanism for evaluating more effective configuration management approaches and the Build Engineer an improved approach for listing rule revisions made by System Architects.
3. It gives the developer a place to log issues when they are encountered; this helps to facilitate better communication, especially with offshore or off-site resources.
4. It is a best practice to separate out Specifications/Requirements issues from coding issues because they involve different categories of resources.