The document outlines topics to be covered in a training course on the role of a PegaBusinessArchitect. The topics include defining the architect's role, understanding business processes and methodologies, using tools like the PRPC portal and Document Wizard, developing workflows, reports, interfaces and rules to automate processes. Hands-on sessions will cover requirements gathering, running a Direct Capture of Objectives session, building reports, and specifying requirements from an architect's perspective. The course is estimated to take 15-20 hours over multiple 1-1.5 hour weekday classes or longer weekend classes.

1. TOPICS COVERED
 Define the role of the PegaBusinessArchitect ƒ
 Knowledgeof businessprocesses,bestpracticesandpolicies ƒ
 Familiaritywithone ormore projectmethodologieslike SCRUM/PEGA BPM
 Associatingprojectspecificationswithbusinessimpactandcomplexity
 Usingthe PRPCBusinessAnalystportal
 Buildingvariouscorrespondence templatesprimarilyEmail templates
 Documentingyourapplicationusingthe DocumentWizard
 Create workflowdiagramstoautomate businessprocesses ƒ
 Developdraftworkflowsanduserinterfaces
 Buildreportstoanalyze businessandprocessmetrics ƒ
 Designmulti-channel,responsive,modernuserinterfaces ƒ
 Configure businessrulestoautomate policies,proceduresanddecisions ƒ
 Documentan applicationthroughall phasesof development,fromproposal torelease ƒ
 Detailedsessiononhowtouse Pega’s Direct Capture of Objectives approachthroughout
applicationdevelopmenttoidentify objectivesandrequirements,andfromthemdevelop
specificationsthatbusinessandsystemarchitectscanuse to configure applicationfeatures.
 Gather requirementsandwrite specificationsinPega7 ƒ
 Understandbasicrule typesandtheirusage ƒ
 Identifyprocessimprovementstoimprove efficiencyandreduce errors ƒ
 Drive processdefinitionduringapplicationdevelopment ƒ
 Understanda PegaData Model ƒ
 Automate businesspolicies,procedures, anddecisions
 Identifyanddecomposecases ƒ
An overview of below topics would also be covered so as to give familiarity
to the terminologies used by Dev and Lead Architect teams.
Application Design
� Application Express
� Requirements and specifications
� Direct Capture of Objectives
� Business Architect responsibilities
Automating Business Policies
� Available decision rule types
– Decision tables

2. – Decision trees
– When rules
� Using decision rules in applications
� Service levels
� Sending correspondence from flows
� Delegating rules to the business and Build for Change®
Case Design
� Case steps and stages
� Cases and sub cases
� Flow rules
� Sub flows
� Flow shapes and their uses
� Work status
Reporting
� Using the Report Browser
� Using the Report Editor to create or modify reports
� Report types and capabilities
– List-type reports
– Summarized reports
– Charting
� Using application data in reports
UI Design
� Basic UI rules and their uses
– Harness
– Flow Action
– Section
PRACTICALS COVERED
 HANDS ON
o APPLICATION REQUIREMENT GATHERING
o RUN A DCO SESSION
o EMBEDDING CAPTURED INFO IN PEGA
o BUILDING REPORTS
o KEY IN SPECIFICATIONS AND REQUIREMENTS FROM THE
PERSPECTIVE OF A BUSINESS ARCHITECT.
COURSE DURATION
15-20 HOURS (BASED ON THE TOPICS COVERED HERE AND HANDS ON EXERCISE).

3. EACH CLASS CAN BE OF 1-1.5 HOUR DURATION ON WEEKDAYS.
WEEKEND CLASSES CAN BE OF 2 HOURS (MIN) BASED ON THE AVAILABILITY.