What are two recommended best practices with user interface (UI) mock-ups in a ClaimCenter implementation project? (Choose two.)

Best practices for UI mock-ups emphasize clarity, traceability, and using appropriate tools. Linking a mock-up to a specific requirement number (D) is crucial for traceability, ensuring developers understand which requirement the design fulfills. Using a dedicated tool (D) or annotating a screenshot (B) are both valid and effective methods. A screenshot is a practical, low-fidelity approach when specialized tools are unavailable, clearly communicating the desired changes in context.

A. A live system demonstration shows an already-built feature; it is not a substitute for a mock-up, which is used to define requirements before development.

C. This option incorrectly prohibits the use of mock-up tools, which are industry-standard and highly effective for creating clear, professional UI designs.

1. Guidewire ClaimCenter Configuration Guide, Version 10.x, "User Interface Configuration" chapter, Section: "PCF File Fundamentals". The guide implicitly supports designing UI changes before configuration, for which mock-ups are a standard practice.

2. Guidewire Education, Course Catalog, "ClaimCenter for Business Analysts," Module: "Eliciting and Documenting Requirements". This module covers best practices for requirements documentation, including the use of visual aids like mock-ups and the importance of traceability by linking artifacts to requirement numbers.