The organization has identified business objectives for the new expense reporting application that will be used to measure the effectiveness of the application. Subject matter experts and key stakeholders were identified to help define the requirements and specifications and will have final sign-off on the completed application. The expense reporting application will be built out over a series of releases allowing for changes based on any feedback received and / or changing business conditions.
The organization identified business objectives for the new expense reporting application. The IT department created a series of process diagrams used for “process validation” which they submitted to the Accounts Payable department for review. Based on the diagrams they created, the IT department has determined the project will take 13 months to complete. To save time, the IT department has started designing the initial application while Accounts Payable is reviewing the process flows.
Show technical users how to use Pega developer tools for collecting customer information.
Help estimate the total time required for the case life cycle to produce a new policy.
Ensure all team members have a common understanding of how a case is processed and resolved.
Guide the development team with guidelines on how to manage the project development.
Collect personal information
Confirm employee and employer
To the reporting manager
To the current user
To a specific user
To a work queue
The amount of time allowed for a user to advance a case to the next stage
The amount of time allowed before the case automatically advances to the next assignment
The amount of time in which the case or step must be completed
The amount of time in which the case or step should be completed
Track assignment status over time
Assign cases to the appropriate case worker
Help ensure timely completion of assignments
Generate service level reports
Will the information be stored in an external database?
How will users enter values in those fields?
Will users want to see information displayed using different styles?
What fields do users need to see?
Can users modify the values or only read the values?
Allow up to 200 concurrent users.
Reduce inaccurate claims to less than 10 percent of all claims.
Passwords must be at least eight characters
Require HR VP approval for sabbatical leave
Eliminate order processing delays due to incorrect routing of requests
A user should be able to cancel an order at any time.
System displays "Authorization History and Summary" for the last 12 months
User must be able to select "Add Temporary Member" when "Authorization is Required" notice is displayed.
If the complainant type is "Provider," then provider information must be populated during the Triage Stage in the Basic Research Step.
Reduce time needed for time-off approvals from three weeks to one.
User passwords shall be encrypted using AES-256 encryption.
The product catalog should be easy to navigate.
There is no difference between a requirement and a specification
A requirement describes what the business need is, and specifications describe how the application will meet the business need.
A requirement provides a blueprint for how the application will meet the goals defined in a specification.
A requirement defines a specific step in a process; a specification defines a complete process.
Represent an alternative flow of the case life cycle sequenced from beginning to end
Organize process steps that are not part of the normal course of events
define the tasks that users accomplish while the case is in the stage.
Define the expected flow of events in the life cycle of a case.
Add a process in a stage.
Add a step in a process.
Add an optional process to any stage in the case type.
Add a local action to the case type.
Allow a user to transfer a case to another employee at any stage of the case
Requiring a separate approval process whenever an order exceeds USD 10,000
Reassign any task that remains open after three days to another user
An application randomly sends a survey to customers once their case is resolved
Which email server should the correspondence use?
How often should you send the correspondence?
Who is the user that receives the correspondence?
When does the correspondence need to be sent?
How will the correspondence be sent?
Automating correspondence allows you to send timely communication
Automating correspondence allows you to advance a case.
Automating correspondence allows for sending consistent information to users.
Automating correspondence keeps all interested parties informed of the current status of a case.
Instructs an architect how to build the step.
Describes to an end user what should be done in the step.
Defines what the step should do.
Describes the business value of the step.
Steps cannot set a work status
Update the work status for the step
Create a local action to update the status
Configure an instruction for the step
Develop feature prototypes
Identify business objectives for an application
Configure UI forms
Define application requirements
Lead System Architect
Senior System Architect
By adding the ruleset that contains the property to the application
By naming PegaRULES as the built-on application
By applying directed inheritance.
By applying pattern inheritance.
The class of the rule.
The status of the rule.
The application that uses the rule
The type of the rule.
The description of the rule
Here's an interesting quiz for you.