• Primary unit of work in an application and the primary collection of data that a flow operates on
• Has a unique ID, an urgency value, and a status
• New name for work item

• Consumes AP work object
• Allows the user to expand on scope, work types, atomic use cases, actors and more in a flexible format
• Creates rules which are used as the foundation of your solution
• also creates its own work object
• Used in Elaboration phase

1. Base and Rulesets
2. Processes
3. Class Structure
4. Reports
5. Correspondence
6. Roles
7. Review Objects

• High-level map of the complete process
• Description of requirements
• Work types
• Use cases
• Interfaces
• Reports
• Correspondence

1. Processes
2. Integration
3. Reports
4. Correspondence
5. Assumptions
6. Project Roles
7. Profile Review

• An automated PRPC tool that creates a high-level scoping document that can be used as a project proposal and an application profile that can be consumed by the Application Accelerator to jumpstart application development.
• It details case types, requirements, specifications, actors, interfaces, and reports/correspondence for an implementation.

• Application Profile document often used with or as solution proposal
• Project Sizing worksheet used to gauge timelines for each phase and more
• Work object used by Application Accelerator (AA) and Project Management Framework (PMF)

1. Describes steps required to process and resolve work
2. Specify when create application profile and discovery map using the Application Profiler
3. Comprehensive or Atomic

• A point in the business process that requires human judgment and input.
• Flow processing of a work item normally pauses when it reaches an assignment shape until a user completes the assignment.
• The assignment normally appears on the worklist of the user who starts the flow.

1. One actor
2. Single event or method that triggers
3. No ownership change
4. Corresponds to one particular step or series of steps
5. Describes process
6. Details so developer can implement and tester can test
7. Take only a few minutes to enter

• Audit Notes can be found on any shape in which you can take an action including a flow action connector.
• History of action taken.

• Use draft mode to run through a process that has no implementation
• Use as a framework to present mocked up UI
• You can reference rules and flow actions that are not yet  PRPC validates whether rules exists for each shape in the flow

1. Used in a when rule
2. Returns a value of true or false

• Captures Business Objectives
• Defines Business Processes
• Creates and Manages Business Rules

• Describes and controls precisely how business is conducted
• Defines the data and information flows and interactions internally and externally
• Between individuals
• Internally within the organization
• Across the extended supply chain

1. Related to the business processes in the specific application
2. Is usually associated with a specific use case or step in a process, and identifies the system behavior at that step
3. Example: First name should not be longer than 20 characters

1. Related to the needs of making modification in the application and system, and managing those changes
2. Example: System shall support two-digit version numbers

• An application is organized as a hierarchy of classes.
• This hierarchy is referred to as a class structure and it governs how individual rules are applied.
• The main purpose of the class structure is to promote the reuse of rules through a mechanism called inheritance.
• When a class is said to inherit from another class, the inheriting class (referred to as a child class) gains use of all of the rule instances applied to the class from which it inherits (referred to as a parent class).

• Text:  For text strings
• Integer:  For a whole number without decimal places
• True or False:  For a Boolean value

• A type of flow action that advances a work item through a process
• Are usually displayed as choices in a pull-down list or as buttons
• Connector shape emanates from an assignment

1. System Behavior
2. Screen Implementation
3. External Interfaces
4. Application Document

• Take details from DCO sessions
• Assign work out to complete configuration of production ready application using an iterative construction model
• Fully unit test each component of application
• Complete test scripts, begin system test process

1. The process of capturing, organizing and storing information using PRPC tools
2. An enabling technology used by IT, Business, Testing, and others in a collaborative way
3. Association of business specifications to specific parts of the application that are implementing them
4. Clear 360 degree view

• A methodology
• A single tool
• A point in time
• A single event within a methodology

1. Session length 4 hours or less
2. Tightly controlled by moderator
3. Parking lot should not exceed 5-10 items

• Application Profiler
• Application Profile (AP)
• Application Accelerator (AA)
• Application Documentation Wizard

• A structure used to hold supporting information used by an application to process work
• Typically used to define a group of properties that repeat
• Mapped to a page property in an application class
• All data classes are derived from the class Data-, either directly or indirectly

• One of the groupings under the rules types and data classes category. 
• The decision category includes rule types that test values and include decision trees, decision tables, and map values.

• A rule that uses a table of numbers, test, or date ranges that converts one or two input values into a calculated result value
• Listed in the Decision rule category
• At runtime, PRPC evaluates the rows starting at the top and then columns left to right
• Seldom used; decision tree rules provide a similar format with more flexibility

• Decision Table*
• Decision Tree*
• When (this returns true false as the result)

* Used to calculate or evaluate the answer.  Called directly.

• Automate business decisions by removing manual steps and user actions
• Listed in the Decision category
• Return a single result value (such as a string, number, etc.)
• Access work item properties
• Can be called from the flow

• Contain onr or more rows, each containing test conditions and result to return
• Returns the value from the Actions column when all tests are true for a row
• If there is no test in a cell, it is true by default
• If no rows are true, it returns the value for the otherwise row
• Can be edited in Excel

• The tests are often based on the same set of properties
• Logic is easy to follow, and can be exported to MS Excel
• Familiar to Business Analysts with spreadsheet experience

• The tests tend to be for different properties
• Flexible format, good for complex if/then/else logic and nested conditions
• Familiar to System Architects with software development experience

• A decision rule that uses if/then logic to calculate a value in a user friendly format based on rows of property values, computations and comparisons
• Listed in the decision rule category.

• Use draft mode to run through a process that has no implementation
• Test processes without building all of its rules
• Get the process right before you begin building UIs, decisions, etc.
• Use as a framework to present mocked up UI
• Display UI rules in context

1. Use Case Details
2. Requirement Details
3. Business Flow Details
4. Draft Screens
5. Project Document

• Build out baseline foundation of application being proposed
• Perform DCO sessions to extract the details of the requirements, Use Cases and Work Types
• Create draft flows and UI(s)
• Develop test plan and establish standards

• Design Infrastructure to suppport today's capabilities and future needs
• Design class structure to support maximum re-use

1. Identifies and enterprise- or industry-wide standard to which the application or system must adhere
2. Example: Routing Transit Number must be 9 digits

• Also called a process or workflow
• Represents an application's business process (or part of one)
• Defines and controls ow work items are created and processed
• Provides a visual representation of an application's flow relationships

Controls how users interact with work object forms to complete their assignments. After selecting one flow action, users may fill in a section of the form to complete the assignment

• Marks the end of the flow.
• When processing reaches this shape, no further processing by this flow happens.
• A flow may contain none, one, or multiple Flow End shapes

• Identifies a subflow, which is a flow rule that is referenced in another flow.
• For example, add a Flow shape to the your flow rule to start another flow and end processing of the current flow.
• The second flow is called a subflow of the first flow. 

1. Similar to the business rule type, identifies what the system has to do
2. Typically used to identify a function that will be used in the application, rather than describing system behavior
3. Example: Remaining budget must be calculated to two decimal points

• Fully Deployed Day 1 data migration into production
• Fully deployed application into production
• Production support Plan / Documentation

• Address go live tasks and application maintenance and support. 
• Takes the final release candidate in transitions, supports its launch, and continues to maintain enhancements, fixes, and change requests by IT and business users.

• Adopt an iterative project approach
• Do nothing that is hard
• Build for change
• Design intent-driven processes
• Create easy-to-read flows

Use to define the appearance and processing of work item forms that we use in the application to create work items and process assignments.

These rules Defines the structure, appearance, and behavior of the forms used in applications to create and update work objects and assignments

• Data is saved to properties
• Properties are written to the database (creating a work item)
• PRPC pulls the work item out of the database and into memory to update the data

1. Business Objectives
2. Requirements
3. High Level Use Cases
4. Work Types
5. High Level Model
6. Application Profiles

• Define the scope of the program, project and sliver
• Capture business requirements, organize them into projects, and break them down into logical slivers
• Identify process improvements
• Capture high level requirements, use cases and work types for sliver
• Estimate effort

• Define scope of project by detailing Business requirements for program
• Organize them into Projects and ultimately breaking the down into logical slivers.
• Build out application Profile that defines /details the scope of first sliver.

• A primary benefit of object oriented technology
• Also called polymorphism, allows a rule created for one class to be applied to other classes that inherit from it

• Flow actions that update an assignment
• Similar to a connector flow action, except that it does not complete the assignment or advance the work item in the process
• Added to an assignment as an attribute rather than a connector
• Local Flow Actions appear below the dashed line

• Creates, approves, resolves and manages work
• Monitors activities and consumes reports

1. Identifies qualities the overall system must have, typically related to how the system performs
2. Example: System needs to have 2-3 seconds screen to screen interaction

Provides read-only text for a cell in a work object form that can include bold, italics, colored text, images, and other rich text

• Is agile and iterative
• Releases capabilities quickly
• Focuses on business value and results
• Documents at the appropriate level
• Is extensible; can evolve and change based on the project

• Vision Definition
• Project Initiation
• Enterprise Planning
• Release Implementation
• Release Retrospective

The highest level in the PRPC UI, this rule defines the overall layout of the user interface.

• Determine Scope of first project
• Kick off the project
• set expectations

• Used to manage projects throughout their lifecycles
• Assign tasks, bugs, and issues to individuals or workbaskets
• Track the status and completion of tasks, groups of tasks, bugs and issues
• Produce Project Status Reports (PSRs) on demand
• Can be used at any time (typically from Inception onward)

• Properties hold the data associated with a running process
• Sometimes call "process instance data"
• Properties can be the fields that are visible in the user interface
• Properties cal also be hidden from view
• Example:  Calculations
• Example:  Confidential Information
• Property Names should reflect the following naming conventions:
• Alphanumeric (must start with a letter)
• No dashes, dots, etc.
• Cannot start with the letters px (read only), py (editable), pz (private property used by Pega)
• Property references are case sensitive and require a leading "."
• .CreditScore and .creditscore reference two different properties

• Single
• Value - contain a single text string value.
• Value List - contain an ordered list of single values
• Value Group - contain an unordered group of single values. (Rare)
• Page (multiple properties)
• Page - contain an embedded page as its value
• Page List - contain an ordered list of embedded pages
• Page Group - contain an unordered group of embedded pages

1. Start with a letter
2. Camel Case
3. No Spaces
4. No Punctuation Marks
5. Case Sensitive

• Defines the type of data the property will contain
• May affect the format and characters allowed for the value

• Within SmartShapes, rules can be selected and reused
• Smart shapes are the shapes associated with using the Visio diagrams

• Continuous improvement
• Assess, learn, adjust, and improve

• Details a business need
• Used to verify that the resulting implementation is what the business needed

1. Are an inventory of events, conditions or functions that need to be satisfied
2. Generic – non-functional
3. Can articulate specific business rules

1. Cohesive – address 1 and only 1 thing
2. Complete – fully stated in one place with no missing information
3. Consistent – no contradictions w/ other requirements & documentation
4. Correct – meets all or part of a business need
5. Current – not obsolete by passage of time

• Sends an assignment to a user, workbasket, or agent other than the current user.
• Associate a Router task with an assignment task.
• This activity determines which worklist or workbasket is to contain the assignment.

Defines the appearance and contents of one horizontal portion of a work object form

Every property must have a type which defines the value it holds [image]

1. Receiving
2. Routing
3. Reporting
4. Responding
5. Researching
6. Resolving

Identifies a collection of CSS styles to be used in a PRPC User Interface

• Phases are smaller and easier to manage
• ROI/business value realized sooner
• Re-use is emphasized and built upon
• Easier to apply lessons learned

• Plan for multiple small releases; each release targeted for 3 months duration (no longer than 6 months)
• Each release should be self-contained
• Plan for maintenance patches between major releases on an ongoing basis
• Prioritize most critical functionality and higher risk features in early releases gto obtain maximum value and lower risk

• Short release cycles of 3-6 months ensures that maximum value is obtained along the way
• Users provide higher quality requuirements for subsequent releases after first hand experience
• Short release cycles reduce pressure on users to review all functionality in first release
• Planning for multiple releases establishes a framework for continued flow gain in the future

• Initiation
• Inception
• Elaboration
• Construction
• Transition
• Go Live

• Manages end-to-end testing of an application
• Used from Elaboration onward

1. QA Test Results
2. UA Test Results
3. Move to Production

1. Portal Rules
2. Harness Rules
3. Section Rules
4. Flow Action Rules
5. Paragraph Rules
6. Skin Rules

• Harness Rule
• Portal Rule

• Understand the big picture
• Develop roadmap and high-level product backlog

• Used in Flow Rules or Secion Rule to conditionally hide information (true/false)
• Used to test property values for one or more boolean logical statements
• Can be used by other rules or shapes in a flow rule

• Unlike other decision types, when rules are called from connectors; these connectors can only be used when the decision shape is set to the Fork option

• Conditionally allow users to perform an action or display content in a section or harness

• A Fork shape is used to reference a when rule in the flow editor
• Use when rules on connectors emanating from a fork shape

• Represents a business transaction process you want to manage, e.g., dispute a charge
• Is accomplished by various people or a system performing tasks or activities to resolve the process

• A work object that is also a parent to one or a few other related work objects
• A work object is a concrete class derived from the Work-Cover- abstract class
• Provides a means to coordinate processing of the related work objects

• Holds a collection of one or more other work objects (which themselves may be basic work objects, other folders, or covers) providing access for analysis and reporting
• Members can belong to different work types, which need not belong all in a single work pool
• The relationships between folder work objects and their contents may be many-to-many
• One work object may be associated with multiple, but with only one cover
• A work object in a concrete class that inherits from the Work-Folder- class

• The primary unit of work completed by an application and the primary collection of data that a flow operates on.
• Operators using an application create, update, and eventually resolve and close work items.

• A collection of assets used to transact a process
• A business problem that requires an automated solution that is associated with one business specification and one or more atomic specifications.
• For example: A claim, loan, or service request.

Focal point for business

• Defines the information required to execute the processes
• Typically derived from business use cases
• Will inherit from one of three possible work classes
• Work Object
• Work Cover
• Work Folder