Discussion

3
Replies
579
Views
LORENA SILVA (LORENAS0)
Capgemini

Capgemini
BR
LORENAS0 Member since 2015 1 post
Capgemini
Posted: March 1, 2016
Last activity: October 4, 2016
Posted: 1 Mar 2016 8:26 EST
Last activity: 4 Oct 2016 18:51 EDT
Closed

CDA Exam

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.
Pega Academy
Moderation Team has archived post, This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Discussion, please write a new Discussion.