When a new requirement for a commercial general liability product necessitates a change to the Guidewire data model, business analysts are…

When the base Guidewire application does not have the necessary data structures to support a new business requirement, the data model must be extended. The business analyst's role is to translate the business need into specific configuration requirements. This involves defining the new data elements needed. In Guidewire's data model, this most commonly translates to specifying new fields to be added to an existing entity (e.g., a "Special Handling" text field on the Policy entity) and defining new values for a typelist (e.g., adding "Commercial Drone" to the CoverageType typelist).

A. System performance metrics and security roles are non-functional and security requirements, respectively, not direct data model extensions for storing business data.

C. Integration mapping and UI mockups are related tasks, but they concern data exchange and presentation, not the core data storage structure itself.

D. External system connections and batch schedules are technical and operational configurations, typically defined by architects and developers.

E. Modifying core entity relationships is a highly complex task generally avoided; indexing is a technical performance optimization, not a business requirement.

F. Defining database table structures and writing complex logic (Gosu) are the responsibilities of developers who implement the BA's requirements.

1. Guidewire PolicyCenter Configuration Guide, "Data Model Introduction," Section 2.1, "Extending the Data Model." This section explicitly states that common extensions include adding new fields to entities and new categories to typelists.

2. Guidewire Education, "PolicyCenter Configuration for Business Analysts," Module 3: "Data Model and Typelists." This course material details the BA's responsibility to identify and document requirements for new entity fields and typelist values.

3. Guidewire Data Dictionary. The documentation for any entity (e.g., Policy.eti) shows the base fields and clarifies that new fields (.ext fields) are the standard mechanism for storing custom data.