GUIDEWIRE ASSOCIATE EXAMS AND STUDY GUIDE 2024 WITH ACTUAL CORRECT QUESTIONS AND VERIFIE, Exams of Nursing

Download GUIDEWIRE ASSOCIATE EXAMS AND STUDY GUIDE 2024 WITH ACTUAL CORRECT QUESTIONS AND VERIFIE and more Exams Nursing in PDF only on Docsity! 1 | P a g e GUIDEWIRE ASSOCIATE EXAMS AND STUDY GUIDE 2024 WITH ACTUAL CORRECT QUESTIONS AND VERIFIED DETAILED RATIONALES ANSWERS BY EXPERTS |FREQUENTLY TESTED QUESTIONS AND SOLUTIONS |ALREADY GRADED A+|LATEST UPDATE| GUARANTEED PASS What are some of the relationships between entities 1. Fields - atomic data stored about the entity (non-restricted values 2. Type keys - a single reference to a value in a typelist 3. Array keys - a set of references to another entity 4. Foreign keys - a single reference to the id of another entity Provide an example of why a non-developer should have a basic understanding on application logic? - Most projects require some changes to application logic - Non-developers define requirements for UI changes - Non-developers help define requirements for Gosu rules - Non-developers define requirements for business rules Name two places where application logic exists? - Gosu rules - Business rules - The User Interface - Classes - Entity Names What are two types of rules? and who is responsible for developing each? - Gosu rules: created by developers - Business rules: created by non-developers What is the purpose of integration? Integration allows two systems to exchange data or perform work? Why is it important for non-developers to have a basic understanding of integration? Non-developers assist with documenting requirements including data mapping between the two systems and UI changes to communicate the requirements to developers 2 | P a g e Name some common examples of InsuranceSuite integrations - User Authentication - Geocoding - Check printing - Document production - Document management - Address verification What tasks are commonly performed by non-developers for integrations? Non-developers often prepare data mapping documents and screen mockups needed to support integration development What are the benefits of implementing InsuranceSuite using the base configuration? - Transform business operations with innovation - Keep current with technology trends in the industry - Leverage product documentation, best practices, standards, and tools - Leverage Guidewire consultants and expertise - Leverage industry best practice built into InsuranceSuite applications All of the Above What are the potential impacts of reinventing legacy systems or features? - Increased development time - Decreased cost - Performance Issues - Increased maintenance responsibilities - Limitations and challenges with upgrades 1, 3, 4, &5 - Increased development time - Performance Issues - Increased maintenance responsibilities - Limitations and challenges with upgrades Identify strategies and tools you can use to avoid reinventing legacy systems and and features when implementing InsuranceSuite applications. - Prepare for elaborating requirements by reviewing Inception Notes - Use the legacy system requirements as a starting point - Compare system changes to business objectives for alignment - Leverage the benefits of sticking to the base configuration - Refer to the Strategic Value Map to identify the value of the change - Demonstrate standard functionality in the InsuranceSuite application that will accomplish the same results - Point out the impacts to budget development time and maintenance management - Refer to the process they are familiar with in their current system 5 | P a g e - May be used by multiple fields - The Data Dictionary Typelist pages show details - Represents a predefined set of possible values Typelist Gap Analysis is performed in what phase of Guidewire project life cycle? Inception phase Definition of Done is considered in what phase of the Guidewire project life cycle? Sprint 0 (Development phase) Confirm scope in the goal of which phase of the Guidewire project lifecycle? Inception Inception events in order 1. Conceptual sprint plan 2. Infrastructure plan 3. Integration context diagram 4. High-level integrations design 5. Sandbox installed 6. Project resources are trained 7. Introduce Agile Concepts 8. Gap analysis Role of the Product Owner on a project team - Key stakeholder representing the voice of the customer - Business authority to make decisions (can delegate to key SMEs) - Shares vision with the development team - Collaborates with the teams to develop and deliver the work - Defines requirements and answers the development team's questions promptly and with authority - Responsible for signing off on user stories and defects - Does not write requirements or tests during development - DRIVES VALUE Common processes within each insurance product; a broad category of requirements, goals, or business priorities Theme Order of the layers of planning 1. Plan the program 2. Plan the project 3. Plan each release 6 | P a g e 4. Plan the iterations or sprints within the Release 5. Plan the daily Scrum Resource used to drive inception elaboration and scope confirmation User Story Cards In what phase is story card reviewed to confirm scope and effort Inception A single reference to the id of another entity Foreign Key Gosu rules consist of... 1. A business object or Root object (e.g. Contract or Claim or Policy) 2. A condition that evaluates to true or false 3. An Action that executes if the condition is true, nothing happens if the condition is false Shows definitions of Entities and Typelists Data Dictionary Information available in the Data Dictionary The meaning of a field What fields are available Where the fields are available Gosu Rules - Created and maintained by developers - Managed in Guidewire Studio - Written in the Gosu language - Available for many business purposes and business objects - Capable of handling complex logic Business Rules - Created and maintained by non-developers - Managed by Business Rules UI screens (in the administration screens) - Available for limited business purposes and business objects - Meant for simpler logic Gosu rules high level business purposes Approval Assignment Validation Business rules high level business purposes 7 | P a g e Activities Exposures Reserves Components of a Business Rule - Basic information: contains the name, description (optional) and triggering entity and action for this rule - Applicability criteria: contains conditions to filter out the trigger entities this rule doesn't apply to (Can be specified or all rule types; Fields available change based on rule type) - Rule conditions: contains one or more conditions which must be true in order to execute this rule's action - Actions: contains the action to be performed if this rule's conditions are true Guidewire Market place provides access to Accelerators Data Model makeup Entities + Typelist Steps of a Requirements Gathering Session in order 1. Demonstrate OOO product features 2. Identify user stories that support business processes 3. Elaborate requirements for user story 4. Write acceptance criteria for a story 5. Identify requirements that do not fit in standard user stories and user story gaps Steps of elaboration activities in order 1. Schedule elaboration meeting 2. Discuss high level product functionality 3. Elaborate requirements for each user story related to theme 4. Determine gaps 5. Estimate each user story Project team member who execute tests and coordinates with Developers accordingly Quality Analyst Accelerator An accelerator is a pre-built solution or framework that provides a head start in implementing Guidewire software for specific insurance lines or business processes Provides good Starting Point Extension 10 | P a g e What does acceptance criteria describe (Select 2) - Describe when user story is done - Value delivered to end user - Checklist of activities that must be completed before accepting the story - Describes user role, action and reason 1 & 2 - Describe when user story is done - Value delivered to end user Although business analysts are usually not involved in _____________ the design solution, but they are responsible for __________ the design solution. - Implementing, documenting - Communicating, Implementing - Implementing, outsourcing - Writing, Implementing Implementing, documenting Reasons for non-developers to understand the underlying technology - Determine what data is present in OOTB configuration - Know how data is used and documents change requests Reasons for non-developers to understand UI architecture - Request changes that are consistent with the base product architecture - Ensure consistent look and feel Which of the following are true about UI architecture? - Consists of Screen area, side bar, tab bar, info bar, workspace - Has familiar look and feel for all products How are UI changes made? User Interface (UI) changes are made in components called Page Configuration Format (PCF's) Non developers define business logic requirements for - UI functionality - Rule conditions and actions - Application processing flow Common roles on implementation project BA, QA and DEV Responsibilities of business analyst (Select 1) - Documenting requirements and answering questions on system functionality 11 | P a g e - Voice of customer - Acts as liaison between sales, SME and technical team - Documenting requirements and answering questions on system functionality Which phase ensures quality of the system for production deployment? Stabilization Best practice during elaboration session Do: a. Listen to the conversation b. Use standard workflows and screens as a starting point c. Focus on "happy path" first, then edge cases d. Use parking lot for off topic items Do not: a. Permit more than one conversation at a time b. Duplicate the legacy system c. Be afraid to suggest: "Let us put that on the backlog" when out of scope d. Revisit decisions Key Deliverables of Development Phase Planned Sprint Sprint Backlog Accepted User Stories Production Quality Burn down Reports Updated Velocity Reports Reprioritized Backlog Impact of UI changes that are consistent with base product architecture? - Ensure consistent look and feel - Simplify new user learning experience - Reduce development time - Simplify maintenance and upgrades - Reduce likelihood of performance impacts Why Non-Developers should understand Data model - Understanding the underlying data improves configuration decisions - When a new field is needed on a screen, it is useful to know if it already exists Foreign Key example Claim entity's AssignedUser → User entity's ID Stores a reference to a related object in the data model Regulatory Requirement 12 | P a g e Ensures compliance with state and federal regulations Non-developers define application requirements supporting integration including... - Data mapping between systems - UI changes to support new data - Timing - will the integration execute automatically, on demand, or on a schedule - What triggers the integration - user action, creation or update of data, and so on Non-developer understanding of Integration Mechanisms? - How data is shared between InsuranceSuite and other systems - Integrations move data to and from InsuranceSuite Which phases in the Guidewire project lifecycle are divided into sprints? - Inception - Development - Stabilization Cross Functional team success factors: - Frequent communication - Co-located teams - Empowered decision making - Active business involvement - Leverage value and product alignment What is a user story? - Ex: as a <role>, I want to <action> so that <reason> - High-level requirements from a user's perspective - Often captured on index cards or sticky notes during early planning sessions Good User Stories I - Independent N - Negotiable V - Valuable E - Estimable S - Small T - Testable Story elaboration goal is identifying value driven changes to ootb story, who are key stakeholders? BA's, SME, PO's What does it mean to elaborate a user story? Conversations occur between the users and the team to ensure all requirements are understood Elaboration session benefits 15 | P a g e 1. Demonstrate product features 2. Review process maps for that theme 3. Discuss user stories by theme/sub-theme 4. Gather enough information to estimate story 5. Time-box discussions to avoid excessive details 6. Update backlog with revised estimates and gaps What are the Product Owner's Responsibilities on a Guidewire project? (Select 3) - Answers the development team's questions promptly and with authority - Facilitates the agile process - Acts as a key stakeholder representing the voice of the customer - Signs off on user stories and defects 1, 3, &4 - Answers the development team's questions promptly and with authority - Acts as a key stakeholder representing the voice of the customer - Signs off on user stories and defects What are the Scrum Master's responsibilities on a Guidewire project (Select 3) - Facilitates the Agile process - Supports the sprint team - Works closely with Developers and Quality Analysts during sprint execution so the right features are built - Resolves impediments 1, 3, & 4 - Facilitates the Agile process - Supports the sprint team - Resolves impediments What are the benefits of accelerators? (Select 4) - They are extensions already developed by Guidewire or Partners to fill a common need - They are easily available for download on the Marketplace website - They become part of a customer's configuration and are supported by Guidewire - They offer a complete solution for InsuranceSuite products - They reduce implementation timelines by providing a good starting point 1, 2, 3, &4 - They are extensions already developed by Guidewire or Partners to fill a common need - They are easily available for download on the Marketplace website - They become part of a customer's configuration and are supported by Guidewire - They reduce implementation timelines by providing a good starting point Which of the following are tools or resources that a Developer might use when configuring InsuranceSuite products? (Select 3) - Guidewire Easy Guide - Accelerators 16 | P a g e - Release Planner - Guidewire Studio - Guidewire GO products 2, 4, &5 - Accelerators - Guidewire Studio - Guidewire GO products Which of the four principles of the Guidewire SurePath approach does this course (InsuranceSuite Implementation Tools) address? - Optimize scope for base work and changes - Follow Guidewire implementation guide rails and advice for solutions - Leverage Guidewire content for common needs to reduce project effort - Drive value by applying value alignment to prioritize discretionary spend 3 - Leverage Guidewire content for common needs to reduce project effort What are the benefits of the Guidewire Community website? (Select 3) - Provides access to product information in knowledge articles and documentation - Provides opportunity to participate in discussion groups - Provides access to training on the Guidewire Education portal - Provides product accelerators for download - Provides the ability to contact Guidewire Customer Support and case creation 1,2, & 5 - Provides access to product information in knowledge articles and documentation - Provides opportunity to participate in discussion groups - Provides the ability to contact Guidewire Customer Support and case creation Which of the following are tools or resources that might be leveraged by an implementation team during inception? (Select 3) - User Story Cards - Business Process Flows - Mind Maps - Deployment Plans - Accelerators 1, 2, &3 - User Story Cards - Business Process Flows - Mind Maps Which of the following are responsibilities of a Business Analyst on a Guidewire project? (Select 3) - Acts as a liaison with stakeholders to ensure clear communication between business and technical groups - Participates in application specification discussions to define functional requirements and workflows 17 | P a g e - Assists is defining concrete examples of system behaviors in Story Huddles when using BDD - Facilitates the Agile process 1, 2, &3 - Acts as a liaison with stakeholders to ensure clear communication between business and technical groups - Participates in application specification discussions to define functional requirements and workflows - Assists is defining concrete examples of system behaviors in Story Huddles when using BDD What is the purpose of the Mockup UI tab in a story card? - To describe the functional requirements for the UI - To show the proposed user interface (UI) for the story - To show the final user interface (UI) for the story - To list the options for the Type keys 2 - To show the proposed user interface (UI) for the story According to the story card best practices, when can you change a requirement number? - You can change a requirement number before the requirement is published - You can change a requirement number anytime - You should never change a requirement number 1 - You can change a requirement number before the requirement is published What are some common customizations of story cards? - Adding an additional column for requirement numbers - Creating an additional tab for integration - Adding an additional column for dates - Creating an additional tab for change management - Removing the Document Control tab 1, 2, 3, &4 - Adding an additional column for requirement numbers - Creating an additional tab for integration - Adding an additional column for dates - Creating an additional tab for change management Place the items in correct order for the naming convention used for user story cards. - Guidewire ID - Theme - xCenter with version - Sub-Theme 3, 2, 4, 3 xCenter-Theme-Sub-theme-ID Number 20 | P a g e - It shows the data elements that belong to entities and typelists - How existing and custom fields can be configured What are the four main areas of configuration in a Guidewire application? 1. User Interface 2. Data Model 3. Application Logic 4. Integration What are some of the technologies used in InsuranceSuite applications? Page Configuration Format (PCF) files Gosu (programming language) What are some reasons for a non-developer to understand the technology stack? To determine what data is stored and if new requirements need additional data elements. To know how and where data is used. To communicate what data may be needed beyond what is in the base configuration. To determine valid values or circumstances for the new data. What are some examples of what can be configured in the User Interface? The order of fields, change labels, regroup fields (simple change). Fields on a screen (moderate change). Screens (complex change). Screen-based logic (complex change). What are some examples of what can be configured in the Data Model? Information that the base application does not store (add passport number). Values for a Typelist (add valid values for AddressType or PhoneType). Data to support regulatory requirements. Why is it important for non-developers to understand the basics of the UI architecture and components? So that they can request changes to the UI that are consistent with the base product architecture and communicate effectively with developers, What are five common areas of the UI architecture? 1. The Screen Area 2. The Sidebar 3. The Tab Bar 4. The Info Bar 5. The Workspace Name three components of a PCF 21 | P a g e Card ListView Button Text Input Contact Picker Radio button Checkbox What keyboard shortcut provides just the location information for a screen viewed in an InsuranceSuite product? ALT+SHIFT+I displays the Location Info window What tool does a developer use to configure InsuranceSuite products? Guidewire Studio What are the two main components of the data model? 1. Entities 2. Typelists What is the purpose of the Data Dictionary? It shows the data elements that belong to entities and typelists What are some of the relationships between entities? Foreign keys - a link to a single row in another entity Array keys - a link to multiple rows in another entity Type keys - a link to a specific value in a typelist Why should a non-developer have a basic understanding of application logic? - Most projects require some changes to application logic - Non-developers define requirements for UI changes - Non-developers help define requirements for Gosu rules - Non-developers define requirements for business rules Name two places where application logic exists. Gosu rules Business rules The User Interface Classes Entity Names What are two types of rules and who is responsible for developing each? Gosu rules - developers Business rules - non-developers 22 | P a g e What is the purpose of integration? Integration allows two systems to exchange data or perform work. Why is it important for non-developers to have a basic understanding of integration? Non-developers assist with documenting requirements including data mapping between the two systems and UI changes and communicate the requirements to developers. Name some common examples of InsuranceSuite integrations. User authentication Geocoding Check printing Document production Document management Address verification What tasks are commonly performed by non-developers for integrations? Non-developers often prepare data mapping documents and screen mockups needed to support integration development. Which phases in the Guidewire project lifecycle are divided into sprints? Inception Development Stabalization What is the typical duration of a sprint in the Inception phase? One week During the Stabilization phase, what is the purpose of performance testing? Run tests to check how well the system works in anticipated and peak loads. During the Deployment phase, what happens during the Pilot step? - Allow a subset of users to use the system - Gather feedback - Triage feedback - Implement changes as needed During the support phase, who is responsible for monitoring business processes? Support team What are the Project Manager's responsibilities? Support the sprint team, facilitate the agile process, enable self-organization, resolve impediments, shield outside interference, is a participatory leader and not a dictating manager; servant leader 25 | P a g e -Assign a resource to each task -Estimate each task 5. Add new user stories and tasks as needed Which criteria are used to prioritize the backlog? (In no particular order) Priority, value, size, risk Name five responsibilities of a Business Analyst on a Guidewire Project. -Work with end users to understand business requirements -Act as a liaison with all stakeholders to ensure clear communication between business and technological groups. -Document business requirements including example maps, high-level process flows, business rules, forms, and typelist values. -Participate in application specification discussions to define functional requirements and workflows. -Work closely with developers and quality analysts during sprint execution so the right features are built. Name 3 benefits of the Guidewire Agile Approach/Methodology. -Leverage Guidewire content for common needs -Implementation model optimized for P&C -Focus on Value, Delivery, Knowledge Transfer What are the Scrum Master's responsibilities? -Supports the sprint team -Facilitates the agile process -Enables self-organization -Resolves impediments -Is a participatory leader. What are the product owner's responsibilities? -Acts as a key stakeholder representing the voice of the customer -Uses business authority to make decisions (can delegate to key SMEs) -Shares vision with the development team -Collaborates with the teams to develop and deliver work -Defines requirements and answers the development team's questions promptly and with authority -Signs off on user stories and defects Who are the most common Sprint Team Members? Business Analysts, Developers, Quality Analysts/Testers What are the benefits of accelerators? -Add value to multiple projects -Reduce implementation timelines by providing good starting points that you can customize as needed for your project 26 | P a g e -Make your team more efficient -Available on the Marketplace website What are the benefits of the Guidewire Community website? The Community is your one-stop shop for information about Guidewire products. There are on-demand resources such as software downloads, knowledge articles, and documentation. Also, this is where you can contact Guidewire Customer Support by creating a case. You can also participate in the Community through the discussion groups. What is the purpose of story cards? -Describe a standard product behavior -Represent a specific business requirement -Contain descriptions of user interface, business rules, and other requirements -Help customers understand the base product -Identify changes needed to satisfy business requirements -At end of project, detail what has been implemented What is the name of the tool that generates story cards? User Story Template Generator What is the naming convention for story cards? 1. xCenter with version 2. Theme 3. Sub-Theme / Screen 4. Guidewire ID What is the purpose of the Mockup UI tab in a story card? To show the proposed user interface (UI) for the story What are some common customizations of story cards? -Adding an additional column to hold information like: dates, text or numbers (Requirement Numbers), drop down lists -Creating an additional tab for: data mapping, integration, integration failover, change management According to story card best practices, is it advisable to change a requirement number? No. A requirement number should not be changed after the requirement has been published. When are the acceptance criteria written in the requirements gathering process? At the same time as the business requirement and before development can begin. They are further refined as the functional requirements are written. Who is responsible for driving the requirements elaboration workshop? Business analyst 27 | P a g e Based on the best practices for conducting an elaboration workshop, what should be the starting point? Use standard workflows and screens of the base configuration What are the Surepath guiding principles on the path to success? Agile, value driven and Success What are the Proven estimation accuracy? Introductory +- 30% Implementation workshop -+20% Inception phase +-10% Why is the link of community portal? https://Community.guidewire.com Guidewire connect Simple, seamless, smart approach to common integrations Fast, predictable delivery Always up and up to date One easy cost effective subscription Pre-built, line of business content with Guidewire Go Pre-packaged contents, Accelerators and Metadata driven definitions 35+ new product models in marketplace Accelerated delivery with prebuilt product contents curated, Tested and packaged by guidewire experts Examples of prebuilt content and solution available on guidewire marketplace GO Products Surepath content Accelerator Ready for Guidewire Surepath enables customers to do? Accelerated team member onboarding Lower implementation cost Achieve predictable results Maximize use of base product capabilities Guidewire cloud standards are produced for? Cloud transition Functional solutions Testing Security 30 | P a g e tab bar info bar workspace Business rules are used to create 1. Activities 2. Exposures 3. Reserves What are the Business Rule Components? 1. Basic Information 2. Applicability criteria 3. Rule conditions 4. Rule actions What are te logics those can be configured in PCFs? 1. Field behavior - visibility, availability, editability 2. Screen behavior - add buttons, links, and menu items Logic that can be configured in classes 1. New computed values or business logic 2. Non-dev document requirements for calculations or formatting changes 3. Dev writes code to implement requirement and tests it What are Gosu classes based on? Business objects What are utility classes based on? Common, reusable tasks and calculations Integration Mechanisms 1. Predefined plugins (authentication/geocoding) 2. Web services - xml based information exchange system 3. Messaging - exchanging messages between systems 4. Startable plugins - listens for requests from external systems 5. Batch processes - completes work without user input what are the two types of rules and who is responsible to develop each? - Gosu rules and Business rules - Gosu rules are created by developers and Business rules are developed by non-developers Which are the tools provided by GW to understand the product features ? (Any 3) 31 | P a g e Documentation/ Reference Resources Extension Packs Security Dictionary What is the purpose of 'Available' column in the UI Fields Tab ? Indicates if the use can click on the field When does a field needs to be marked as 'New' in UI Fields Tab ? Fields which are newly added to OOTB, is set a New Business cases are defined un Pre Inception What are the roles of Technical Business Analyst ? (Any 2) - Provides impacts analysis of downstream systems - Document transformation and cleansing rules What is done during sizing and planning - Inception phase ? (Any 3) - Finalize estimates - Develop conceptual sprint plan - Determine Development and Migration Strategy Gosu rules consists of (any 2) - Business object or Root object - A condition that evaluates true or false ________ is the common process within each product (select 2 options) Themes and User Guide Entity example - Claims - Fields - description, claimreportdate, weatherreated - Type Keys - Accident type, Claimsource, Losstype - Array keys - Alladdresses, secondary addresses - Foreign Keys - Catastrope, Assigned Group What is Miro? - An useful project planning tool for isnurancesuite implementation. - whiteboading applicatoin enables project team to share information and collaborate by creating dashboards with digital stickynotes How the Business analyst job aid Miro helps new business analysts? This is useful when onboarding by: - Helping them understand what is expected of them at each phase of the project 32 | P a g e - outlining the tasks they shold be prepared to perform - alerting them to available planning aids Accessibiliy features - InsuranceSuite includes accessiblity improvements in teh three areas: - scren magnification and color contrast - keyboard support - Screen reader support What are Extension pack? Extenstion packs are : - Suppoered product extensions - Developped by Guideware product development - Separate license fee Avoid using internal path for your classes com.guidewire.* should be avoided. These can always be potentially changed or replaced during an upgrade. When referencing typecodes, use the static property on the typelist class instead of the string representation Use TC_TYPECODE instead of "typecode", example: LossCause.TC_REAREND instead of "rearend" Use the text for logical operators instead of the symbols Use "and","or", and "not" instead of "&&", "||", and "!" Code placement 1) Avoid placing code within the CODE tab of a PCF. Create a UI helper class instead 2) Avoid extending entity enhancements with code supporting UI operations Avoid using deprecated classes and methods Guidewire will eventually remove deprecated classes and methods. Turn on and run Studio Inspections These analyze configuration resources Use whitespace effectively Add spaces around operators Do not add spaces between parentheses and operators Indent logical blocks of code by two spaces only Add a blank line after code blocks Add two blank lines after methods, including the last method in a class Comments and Annotations 35 | P a g e Example: PLUGIN.MotorVehicleRecord static var _motorVehiclePluginLogger = LoggerFactory.getLogger(PLLoggerCategory.PLUGIN."MotorVehicleRecord") Logging Format should be a standard format to simplify analysis of large logs Guarded Logging should be used To test log level before logging costly messages (those with expensive expressions) Typically used with the DEBUG level Format is - if (_logger.DebugEnabled) { <log statement content>} Not required for parameterized expressions lacking expensive operations, as in: var hello = "Hello" var world = "world" _logger.debug("{}, {}!", hello, world) Logging: Exception Messages Logged at the ERROR level when user interface is affected Not all exceptions are errors - if they are expected, log at WARN or INFO level Pass the exception object as the second argument Logging Guidelines Log with enough information to explain the state of the application and what was happening Excessive logging results in large logs with potential performance risk Insufficient logging results in logs that lack utility Use care with: Data that is protected by legal, regulatory, or contractual obligations Personally Identifiable Information (PII) - do not log PII at all! Guidewire Query API General Best Practices Use the property reference (EntityType#Property) for type-safe access to the properties on the query entity type Use the property reference to filter query results, join to another entity type, order rows in the result set, or to specify a column for a row query Use query.contains() after other query.compare() operations against indexed columns for better performance against large data sets Guidewire Query API - Denormalized columns improve performance of 36 | P a g e Ends with searches Case-insensitive searches Guidewire Query API Anti-Patterns - Bring back only the data you need by Avoid filtering query results in memory Avoid filtering query results in the application server Perform filtering in the database Avoid the use of where(), first(), last(), firstWhere(), and lastWhere() Guidewire Query API Anti-Patterns - use dot notation with care because accessing foreign keys or array fields retrieve additional entities into memory Guidewire Query API Anti-Patterns - Check for existence of an entity when the number of results is not important by Verifying the results of a targeted query are not empty Avoiding hasMatch(), countWhere(), and select().Count Guidewire Query API Anti-Patterns - When a count is necessary, let the database count the entities and Avoid countWhere() Avoid counting collections Avoid iterating over entities from the database to count them Avoid counting entities before accessing them Avoid countWhere() and select().Count Guidewire Query API Anti-Patterns - Avoid queries to check for new or changed entities, instead Use Boolean methods getChangedFields, getAddedArrayElements, getChangedArrayElements, and getRemovedArrayElements Use specialized methods that test for new or changed entities when available (Claim.PolicyChanged) Guidewire Query API Anti-Patterns - Avoid queries to access new or changed entities by Use Boolean methods getChanged, isFieldChanged, isArrayElementAddedOrRemoved, and isArrayElementChanged Check the Gosu API for specialized methods on entities Guidewire Query API Advanced Concepts - Entity queries should be used unless performance is not adequate Guidewire Query API Advanced Concepts - Row queries Use a single database query on the main entity and related entities to return only the data columns you select from the database Allow you to use only the values contained the query results Filter the rows returned from the database using query.compare 37 | P a g e Involve more code maintenance and should only be used when performance issues are encountered with an entity query Support database aggregate functions (Avg, Count, Min, Max, Sum) Guidewire Bundle Management - General information for Bundles A bundle is an in-memory container for entity instances representing rows in the database Bundles are read via queries or foreign key and array accessors Caching at the local and global level improves performance of bundleso Bundles can be read-only or writable Guidewire Bundle Management - A Current bundle is created by the application and is Read-only or writeable Contains entity instances available to current code context Guidewire Bundle Management - A New bundle is created in code and is Writeable Code determines the contents Guidewire Bundle Management - Bundle commits are Transactional - all entities are committed, or the entire bundle is rolled back Automatic when processed by the application in rules, workflows, and some plugins (depends on the underlying code) Manual bundle processing (managed by your code) required for: Web services and batch processes that make database changes Modification to entities returned by queries Certain plugins User interface changes when the UI is in read-only mode Guidewire Bundle Management - Gosu syntax for bundles: Using getCurrent() or newBundle() for Entities require an explicit commit New entities must be created with the syntax var myEntity = new MyEntity(bundle) Guidewire Bundle Management - Gosu syntax for bundles: Using runWithNewBundle ( \ bundle -> {}) with a code block for Entities are automatically committed New entities are automatically added to the bundle Options to create with or without a specified user Guidewire Bundle Management - Gosu syntax for bundles: Adding entities to a bundle uses myEntity = myBundle.add(myEntity) Guidewire Bundle Management - Gosu syntax for bundles: Entities referenced by accessors on entities already in a writable bundle 40 | P a g e Names must end with Test Extend gw.api.test.XXServerTestClassBase or gw.api.test.XXUnitTestClassBase Can include beforeMethod/afterMethod methods that run before or after each test method is invoked Can include beforeClass/afterClass methods that run as test class is loaded or after all tests are executed Are best organized in packages based on testing needs Can be created to be reused for repeated functions or data generation GUnit Testing - Test Methods Names must be lower camel case, have names that start with test, and describe the test being executed Set up test data using entity builders and variables Test and verify results using assert statements Include annotations (optional) GUnit Testing - Test annotations are strings that begin with @ and provide metadata about a Gosu element Example: uses gw.xml.ws.annotation.WsiWebService @WsiWebService() GUnit Testing - There are two types of test annotations Server runtime annotations appear before the class definition and indicate how the test interacts with the Guidewire server Environmental annotations provide additional test functionality and override default system behavior GUnit Testing - For code usability you should create Test helper classes or functions GUnit Testing - When executing a GUnit test, do so by Package or Class GUnit Testing - 4 characteristics of effective unit tests are Readable - speeds up developer productivity Accurate - predictable and repeatable Fast - long-running tests slow development and are abandoned Independent - can be reliably run in isolation from other tests to identify root cause of a problem Guidewire Profiler is used to Investigate performance problems in the production environment Help find and diagnose problems with database queries, rules, and other Gosu code Detect problems early by developers 41 | P a g e Guidewire Profiler Web profiler can Be used for core product user interface performance analysis Capture current user session in which web profiler enabled Capture one set of results from receipt of a request through sending response while enabled Save the web profile in user session (gone when user logs out) Track where time is spent on server: Guidewire application code Response time of calls to database, external services, and so on Guidewire Profiler Web profiler cannot Track Browser time, Network latency or Consumed web services Guidewire Profiler Entry-point profiler is used for integration-related performance analysis on Batch processes Work queues Message destinations REST operations Web services Startableplugins Guidewire Profiler Entry-point profiler captures All runs of targeted components across all nodes Displays separate results for each call/run on each node Saves results in database Guidewire Profiler is accessed 2 ways Navigate to Server Tools (Alt+Shift+T), select Profiler from left pane Popup from an application screen (Alt+Shift+P) Guidewire Profiler Before capturing a profile you must first do these 2 things Clear the application cache to force queries to go to the database Enable stack traces to show the widget or code where queries originate (impossible to pinpoint root causes otherwise) Guidewire Profiler - Web Profile terms Frame is single invocation of a profiled section of code Stack is single server round trip that includes multiple frames Profile is a single Profiler session that includes multiple stacks 42 | P a g e Guidewire Profiler - Web Profile Analysis terms Offset - chronological order of stackso Elapsed Time - execution time Own Time - time that is unaccounted for, indicates the need for code tags Show Queries - shows query aggregated view (default) Find Frames - used to find frames based on text search Query Details - SQL, Raw SQL, Basic, Stack Trace, Filtered Stack Trace, PCF Stack Trace PCF Stack Trace - shows PCF widgets related to the SQL Guidewire Profiler - Web Profile Analysis Guidelines Limit each Profile to a narrow focus of interactions Look beyond timings (the H2 database is fast and not always reflective of a production environment) Focus on anti-patterns, poorly written, or multiple execution of queries Test thoroughly using a representative data set to simulate scaling Guidewire Profiler - Entry Point Profiles and Profile Tags Profiling custom Gosu code requires these two things Creating custom profiler tags Adding the tags to the custom code Guidewire Profiler - Entry Point Profiles and Profile Tags Profiler Tags Are defined in a separate class as public static final variables Improve the ability to analyze performance issues Guidewire Profiler - Entry Point Profiles and Profile Tags Use the Profiler.push("profiler_tag") to push a frame onto the stack to begin profiling Guidewire Profiler - Entry Point Profiles and Profile Tags Use the Profiler.pop(some_frame) to pop a frame off the stack to end profiling Source Code Control Key Concepts Git: Is a distributed version control system (DVCS) Stores links to previous versions of unchanged files Provides each developer with a full copy of the entire history of the project Source Code Control Key Concepts Git: Most operations in Git are performed locally, supporting offline use 45 | P a g e Description: Used for multi-phase releases Naming convention: release/r-0-{phase_number} Created: Off release branch for parallel development Deleted: Source Code Control Key Concepts Branching Strategy - Branch: Hotfix Description: Critical system error requiring emergency fix to production code Naming convention: hotfix/identifier Created: Off master and merged back to master Deleted: Source Code Control Key Concepts Branching best practices Use version control repositories to track software changes Define a mainline branch for the latest project code Create user story and defect branches to isolate changes Break stories into development tasks to support task-level merges Integrate changes on user story and defect branches frequently Verify changes on user story and defect branches before merging Create release branches to stabilize release features Integrate changes on release branches into mainline immediately Use automated builds to verify health of mainline and release branches Use tools to support branching strategy Source Code Control Key Concepts User Story Branch - verify changes before merging Pull the latest changes from develop branch Run all automated unit tests for feature Run all executable specifications for feature (for behavior-driven development) Run critical automated tests against code on branch Conduct peer-review of changes Source Code Control Key Concepts Defect Branch - verify changes before merging Pull the latest changes from release branch Run all automated unit tests for release Run all executable specifications for release (for behavior-driven development) Conduct peer-review of changes Ensure manual verification by quality analyst Source Code Control Key Concepts Verify changes after merging 46 | P a g e Merge user story branch to develop, defect branch to release Perform automated build on destination branch Minimum steps for automated build scripts: ▪ Compile and generate deployment artifacts from tip of branch ▪ Run automated unit tests against tip of branch ▪ Run executable specifications against tip of branch (for behavior-driven development) ▪ Deploy artifacts to shared integration environment ▪ Run automated smoke tests on integration environment Mark build as failed for any error and notify team Fix failed builds immediately Database Design and Maintenance Database schema validation detects when the data model and database schema are out of sync. Correct errors found by schema validation by creating a SQL script to remove orphaned columns or to perform other adjustments to the database. Guidewire advises that you contact Guidewire Support to either provide a script or review a script written by a DBA or developer to ensure correct resolution of the problem o REQUIRED for production databases o Strongly recommended for non-production databases Run schema validation during development to detect out-of-synch conditions between the data model & schema Run during product upgrades to identify problems with the database Database Consistency Checks Database consistency checks verify the integrity of the data in the database Guidewire applications are responsible for ensuring database consistency Database consistency checks identify issues after they occur Database Consistency Checks Platform-level checks are generated from the data model and run against the database to ensure data consistency. Examples of these checks include: Verifying that required columns on subtypes are populated Verifying that every value in a typekey column matches a value in the corresponding typelist Verifying that one-to-one relationships have at most one referring entity Database Consistency Checks - Application-specific checks Guidewire application developers provide hundreds of application-specific checks that are included with each product. A few examples of application-specific checks include Verifying that a single address record is not shared between Contact records Verifying that denormalized search column values match their associated column values Verifying that there are consistent relationships between parent and child objects NOTE: Customers cannot create new application-specific checks 47 | P a g e Database Consistency Checks Potential consequences of database consistency check failures: Application performance may degrade Errors may be introduced into financial data Upgrade problems may be multiplied Archive/purge may fail Searches may return incorrect results Database Consistency Checks When to run database consistency checks: Frequently during development and testing to identify problems early Monthly in heavily used QA environments and on a recent copy of production in a lower environment Archiving Key Concepts Entities are included in the archive domain graph when: The Extractable delegate is implemented The entity has a foreign key relationship with an entity in the archive domain graph Archiving Key Concepts Entities added to the domain graph need a foreign key relationship with an entity inside the graph. The foreign key relationship must take one of these forms: The foreign key can be from the new entity to the owner entity: ▪ Owner can have an array of the new entity ▪ Owner can have a one-to-one or edge foreign key to the new entity The foreign key can be from the owner entity to the new entity with the archivingOwner property in the foreign key set to Source Archiving Key Concepts During startup the application verifies that all domain graph requirements are met Cloud Assurance: Ensures the readiness of an implementation for Cloud deployment; includes Process, Standards, Expertise, Training and certification, and Assessments Applies to new Cloud implementations and upgrades to Guidewire cloud Continues after go-live and in production Sets foundation for product alignment and adherence to Guidewire standards Identifies issues that could impact performance Cloud Assurance Assessments (CAA): Designed to maximize product alignment and minimize unnecessary customization Scheduled at regular intervals throughout implementation Build on prior assessments