Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

GW BA > GW BA > Flashcards

GW BA Flashcards

1
Q

Questions

A

Answers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What happens when requirements are managed and versioned

A

Right Product is build

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

After elaboration session, user stories are updated with

A

Typelists
UI Design
Business Rules

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Tool provided by Guidewire to help implementation

A

User story card

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Objective of Inception elaboration session

A
  1. Theme overview Demo
  2. Detailed Story
  3. Story Estimation
  4. Product documentation
  5. Confirm Product backlog
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Inception Workshop goals

A

Confirm the scope
Validate the size
Baseline the product

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Roles of a non developer in UI

A

Consitent with Base archirtecture
Better decisions
Communication with developers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

5 common areas of UI Architecture

A

Tab bar
Info bar
Side bar / Menu bar
Workspace
Screen Area

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Short cut for Location info

A

ALT + SHIFT + I

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Why non developers should understand data model

A

Because the data is available in base model and to design the requirements pertaining to functionality

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Key which is used as a reference for related objects in data model for ex assigned user in claim

A

Foreign Key

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Definitions of Array Key , Type key, Foreign key

A

Array Key - A set of references to another entity
Type Key - A single reference to a value in a typelist
Foreign Key - A single reference to the id of another entity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Which documents the entities and typelists

A

Data Dictionary

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Type lists are

A

Defines values for drop down and assiciate with a type key

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Non developer define business logic requirement for

A

UI Functionality
Rule conditions & actions
Application processing flow

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Which insures compliance with states the federal regulations

A

Regulatory requirements

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

GOSU rules consists of

A

Object / root object
Condition to evaluate and
Actions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Application Logic exists in

A

Gosu rules
Business rules
The User Interface
Classes
Entity Names

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

UI Logic is present in

A

PCF Files

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Why non developer should understand basic of integrations

A

Define application requirements supporting integration:

Data mapping between systems
UI changes to support new data
Timing - Automatic/ On Demand/ Scheduled
What triggers the integration

Prepare data mapping documents & screen mockups

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Integration Mechanisms

A

Predefined Plugins
Web services
Messaging
Startable plugins
Batch process

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Why integration mechanism is used

A

To exchange data between applications

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Phases of Guidewire project Life cycle

A

Pre inception
Inception
Sprint 0
Development
Stabilisation
Deployment Prep
Launch

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Business case completed , User story mapped to BC , Business resources trained are part of

A

Pre inception phase

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Implemetation workshop and benfit mapping are done in which phase
Pre inception phase
26
Confirm the scope, plan the project, infrastructure sizing is done in
Inception phase
27
Which is a high level sprint plan that Is delivered at the end of the inception that outlines which user stories are build when
Conceptual sprint plan
28
What are Product Owner Roles
- Represents the Voice of Customer - Shares vison with the Development Team - Collaborates with the teams to develop and deliver the work - Answers the development team's questions - Business Authority to make decisions - Responsible for signing off on user stories and defects
29
What are Scrum Master Roles
- Supports the sprint team in accomplishing tasks - Facilitates the agile process with scrum principles - Enables self-organization and hyper-productivity - Resolves impediments by getting out of the way - Shields team from outside interference - Acts as a participatory leader
30
What are Business Analyst Roles
- Works with end users to understand business requirements - Acts as a liason with all stakeholders to ensure clear communication - Documents Business requirements, example maps and high-level process flows - Define functional requirements and workflows - Works closely with Developers and Quality Analysts during sprint execution - Assists in defining concrete examples of system behaviours in Story Huddles when using BDD - Always focused on demonstrating value for end users
31
What are Business Architect Roles
- Coordinates all technical requirements related to the Guidewire products, customer source systems and integrations - Documents gaps and integrations, and assists in the creation of design documents - Provides impact analysis of downstream systems - Works closely with Developers and Quality during sprint execution so the right features are bulit and function end to end throughout all impacted systems - Documents transformation and cleansing rules (example: data migration) - Produces mapping documentation (example: document production)
32
What are SME Roles
- Defines business objectives and future-state processes - Participates in requirements gathering sessions - Reviews and helps refine process flows, use cases, and system requirements - Answers questions from business analysts - Answers questions from technical team members about desired system functionality
33
What are Developer Roles
- Works with the business to understand and develop technical requirements - Assists in defining concrete examples of system behaviors in Story Huddles when using BDD - Creates design documentation - Writes code to configure the application or to integrate it with other applications/systems - Supports test activities during sprint execution to ensure a high-quality, working peice of software is delivered: * Executes unit testing * Resolves defects * Conducts peer code reviews * Reviews test plans and test cases
34
What are QA Roles
- Works with the BA and Develoeprs in Story Huddles to understand requirements - Assists in defining concrete examples of system behaviors in Story Huddles when using BDD - Develops test scenaros for each * Main process flow (Happy Path) * Alternate process * Exception flow - Executes tests and coordiantes with Developers * Validate that features are developed per requirements * Confirm if an issue is a defect * Monitor defects and retest as needed
35
What are Specialist Roles
- Certain roles are highly specialized and in short supply - Specialists offen support the needs of multiple IT projects and/or production systems - Sometimes part of a "Systems Team" created to meet the needs of the Guidewire Implementation
36
Examples of Specialist
DBAs System Engineers Security Specialists Architects Others
37
Cross functional team success factors
Frequent communication Empowered decision-making Active business involvemnent High quality resources
38
Common roles in implementation project
BA QA Dev
39
User story consists of
Role Action Reason
40
INVEST Full form
Independent Negotiable Valuable Estimable Small Testable
41
Story elaboration goal is identifying value driven changes to OOTB story who are the key stakeholders
BA and SME ( Subject Matter Experts)
42
Elaboration Session Sequencing
Guidewire begins with evaluating backlog stories Standard process flow High level req gathering
43
Requirement gathering sequencing
-
44
Who uses acceptance criteria in user story workflow
BA capture them during requirements gathering Developers use them to configure and code requirements QA use them to define test cases and derive pass/fail status Product Owners use them to confirm if a user story can be accepted
45
Accpetance criteria is
- They are definition of 'done' - Describe the conditions to be met before a user story is considered complete - They are conditions of satisfaction - Written as clear, concise statements with a clear pass/fail result - They provide details that are foundational input for test case creation They are NOT: - Test cases or edge test cases - Restatements of the requirements - Description of solutions
46
What are the common process in guidewire product
Themes and Application guide
47
Activities in inceptions workshop / elaboration sessions
Demonstrate the product features Update the backlogs
48
Which statement best describes Guiding principles
-
49
Which site is used for accessing guidewire training material on base product
education.guidewire.com
50
In market place you can download ?
Accelarators and extension packs
51
Accelarators are best defined as
Extension of core product to meet specific need
52
which provides starting point for solution that can be customised
Accelarators
53
In which phase we use story cards
Pre inceptions and Inception phases
54
Do's and Don’t's from a user story
Do: - Implement a peer review process - Review every requirement with the team - Include a requirement number for traceability - Follow a set of UI standards Don't: - Include field requirements in the UI Mockup tab - Document the same requirement in more than one place - Change a requirement number after the requirement is published
55
Examples of user story customisation
- Adding Columns (Example - Next Follow-Up Date) - Adding Tabs (Example - Integration Triggers tab, Integration Failover tab, Change Management tab)
56
Best practices before attending a workshop
- Review current state and future state processes. - Review inception notes and any backlog grooming details. - Review the Application Guide and functionality in the Sandbox. - Review any training materials and training notes. - Create data demostration necessary for demostrating functionality. - Identify key questions to be answered during the workshop. - Prepare for your audience (supporters, detractors and those new to the project). - Prepare an agenda. - Establish and communicate workshop participation expectations. - Schedule the meeting in advance.
57
Best practices while elaborating requirements
- Start by reviewing the workshop agenda and expectations. - Review guiding principles and strategic objectives. - Identify participant roles. - Activiely listen to the conversation. - Designate a note-taker. - Refer to the standard workflows and screens for the base configeration. - Keep the conversation focused on what the business needs are. - Focus on the "happy path" of the requirement first, and then edge cases. - Use the parking lot for the off topic items. - Document decisions. On the other hand... - Do not permit more than one conversation at a time. - Do not reinvent the legacy system. - Do not be afraid to suggest: "let us put that on the backlog". - Do not revisit decisions that have already been made.
58
Best practices after "Elaborating Requirement" workshop
- Ensure the User Story Card is fully updated. - Follow-up on any Action Items. - Schedule future follow up meetings if needed. - Update related documents such as process flow, decision logs or story status. - Escalate any risks or concerns to Scrum Master, PMO or Steering Commitee.
59
While business analaysts are not responsible for ---- design he is responsible for ---- design
Collaborating Implementing
60
Who performs test execution
QA
61
In which phase accepted user story are defined, build and tested for development
Development Phase
62
Components of PCF
Card Listview Button Text Input Contact Picker Radio Button Checkbox

GW BA (3 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions