[CASE NAME]

Process – [NAME]
Pega High Level
Design
Document Classification: TCS-Confidential
 TABLE OF CONTENTS

[*Page number needs to be updated]

1 Document Control 4
1.1 Revision History 4

1.2 Document Approval 4

1.3 Document References 4

1.4 Assumptions 4

1.5 Issues 5

1.6 Dependencies 5

1.7 Risks 5

2 Introduction 5

2.1 Document Purpose 5

2.2 Overview 5

2.3 Audience 5

3 High level Architecture diagram 6

4 Use Stories 6

5 Application Design 6

6 Ruleset Design 6

7 Enterprise Class Structure 6

7.1 Overview 6

Framework Classes 6

Implementation classes 6

Organization classes 6

7.2 Enterprise Class Structure Inheritance Pattern 6

8 Work Types 7

9 High Level Process Flow 7

10 Main Process Design 7

10.1 Process Overview 7

10.2 Process Implementation 7

11 Exceptional Handling 7

12 Interfaces 7

13 UI Design 7
14 Create Case Functionality 8
15 Work Groups (Teams) 8

16 Workbaskets 8

17 SLAs 8

18 Reuse 8

19 Monitoring 8

20 NFR Design 8

21 Database Table Mapping 8

22 Data Dictionary 9

23 Organizational Structure 9

24 Access Groups 9

25 User Roles 9

26 Portals 10

27 Security 10

28 Encryption 10

29 Exception Scenarios 10

30 Reports 10

31 Environmental Details 10

32 Glossary and Acronyms 10

 1 Document Control
Revision History

Version Version Changed By Status/Changes

No. Date

Document Approval

Version Version Date Approved By(Reviewed) Role

No

Document References

Ref No. Document Name Version

1 P 7.2
D
N
2 CSSA Exercise Guide 7.2
3 CSSA Student Guide 7.2

Assumptions

Ref No. Application Description Raised By Status

Issues

Ref Applicatio Descripti Raised By Status

No. n on
Dependencies

Ref Application Description Raised By Status

No.

Risks

Ref Application Description Raised By Status

No.

2 Introduction
Document Purpose
The purpose of this document is to automate the XYZ Process with complete details using PEGA 8 Platform.

Overview

Audience
3 High level Architecture diagram

ABC

ABC-FW-XYZ

Product

ABC-

Product

4 Use Stories
Create your story based on all stages provided in used case

5 Application Design
A case type named XYZ is created consisting of n stages. They are

1. Stage 1
 2. Stage 2

3. Stage 3

Add additional stages if require

6 Ruleset Design
Framework rulesets:

● ……………..
● ……………..
● ……………..
● ……………..

Implementation rulesets:

● ……………..
● ……………..
● ……………..
● ……………..

7 Enterprise Class Structure

Overview

Framework Classes
This framework class contains n classes:

Framework work class: ……………..

Framework data class: ……………..

Framework integration class: ……………..

Implementation classes
This implementaion class contains n classes:

Implementation work class: ……………..

Implementation Data class: ……………..

Implementation Int class: ……………..

Organization classes
This has one organization class: ……………..
 Enterprise Class Structure Inheritance Pattern

[*Please include structure as per your case]

8 Work Types

Name Work ID Prefix Implementation Class

XYZ D- ABC-Div-Unit-XYZ-WORK-XXY
9 High Level Process Flow

We have n flows in our project.

● ……………
● ……………
● ……………

10 Main Process Design

Process Overview

[*write your story here]

Process Implementation

11 Exceptional Handling
The Validation is used for capturing date to check that is not future date.

12 Interfaces
Interfa
Integration Name Source Destination
ce
Type

13 UI Design
● [*write your story here]
 User Interface – Form Design:

Attachments:

14 Create Case Functionality

[*write your story here]

15 Work Groups (Teams)

Customer@ABC : This work group is used for customers.

Stage1@ ABC: This work group is used for …..

Stage2@ ABC: This work group is used for …..

Stage3@ ABC: This work group is used for …….

16 Workbaskets

XYZTeamWB

All the assignments will be present in XYZTeam Workbasket, the customer enters his details.

17 SLAs
The cases created by customer with XXY pending for more than n days will be rejected and notification will be
sent to customer and XXY. Within 2 days notification will be sent to corresponding operator.

18 Reuse
Data types, case type and all are been created in framework.

So they can be reused in implementation layer.

19 Monitoring

Tracer, PAL and SMA is used for monitoring purpose.

20 NFR Design
● Monitoring Performance through tracer
● Compliance Score must be greater than 90%
● Using Log files to find errors

21 Database Table Mapping

DB Class
Table Name

22 Data Dictionary
Property Type
First Name Text
Last Name Text
Date of Birth Date only
Gender Pick List (Radio Button)
23 Organizational Structure
When designing user access, it is possible to put all access information in the Operator ID instances.
However, for companies with large numbers of users (several thousand, for example), managing the access to
applications on a user-by-user basis would take a great deal of time. It is much more efficient to divide users into
functional groups, based on the work they do, and then give access to the entire group at a “division” or
“organization” level.

Organization Structure: ABC-Div-Unit

Operator Access
ID Group
Customer DEBITCARD: Customers

24 Access Groups
XYZ: Customers

XYZ: Stage 1

XYZ: Stage 2

Etc.

25 User Roles

Access Group Role Privilege Purpose

AllFlows() Can run any flow.

Can use any of

the
XYZ: Customers AllFlowActions() flow actions
XYZ: Stage 1 presented
XYZ: Stage 2 in a
Managers
work object form
Allows
requestors to
changes to the
UpdateWorkGroupSkills() skills array
information in
any Operator ID
data instance
 associated with
their work
group.
can update the
UpdateWorkGroupAvailability() availability of the
work group.
Can perform
actions on
PerformBulk() multiple
assignments or
multiple work
objects
Allows users
of list view or
summary view
ShowStoredValues()
reports to pick
criteria values
at
run time
It can run
ReportWizard()
the Report
Wizard.
Can perform
an
PerformWork()
assignment
on someone
elseís
worklist
AllFlows() Can run any flow.
Can use any of
the flow actions
AllFlowActions()
presented in a
XYZ: Customers work object form
Users
Can perform
an
Perform()
assignment
on someone
elseís
worklist

26 Portals
[*Provide portal names as per your case]
27 Security
By giving proper privileges to particular operator, we can maintain security. so that others do not have
access to that assignments.

28 Encryption
Password Encryption

29 Exception Scenarios
Whenever the data is not obtained from external database to the application, then we can use simulated
data source.

30 Reports
After capturing customer Details it will be routed to Manager’s Worklist defined through Report
Definition containing columns CaseNo , Created Date, Created Operator, Updated Operator, Case Status.

31 Environmental Details

Environme U
nt R
L
Dev 192.168.242.131:9080
SIT
UAT
Prod
Sharepoint
Database
<<< >>>>
32 Glossary and Acronyms

Glossary/Acronyms Descripti
on
TCS Tata Consultancy Services

NFR Non Functional Requirements

BRD Business Requirement Document

PAL Performance Analyzer

SMA System Management Application

WB Work Basket