7/31/2019 DCO Introduction
1/10
DCO Introduction Pega PRPC v5.5
DCO stands for Direct capture of Objectives. As the name
suggests, it is a module in the PRPC to capture business
objectives, business requirements, actors and other kind of
information that will help in clearly stating the needs of the
customer.
The reason the module was introduced was to overcomethe challenges faced in maintaining multiple versions of
documents like the Business requirement documents
(BRDs), Functional Requirement documents (FRDs)
DCO will avoid the conventional approach of merging
different kinds of documents (like the ones mentioned
above) and taking the trouble of merging them.
I will use screenshots to explain how the module works.
Please note it is not a tool and it does not implement the
application for you. It is an enabling technology used by IT,
Business folks to work collaboratively over the entire
lifecycle of the project.
Login Page
7/31/2019 DCO Introduction
2/10
Once you login, you will see 6 slices Process, Policy
Decisions, User Interface, Integration, Monitor Activity,
Cases and content
Starting DCO:
DCO comprises of Application Profile, Enterprise Application
Accelerator and Document Wizard.
To walk you through how requirements are captured, I will
take a simple scenario-
http://techbpm.files.wordpress.com/2011/12/app-profile.jpghttp://techbpm.files.wordpress.com/2011/12/prpc-login-page.jpghttp://techbpm.files.wordpress.com/2011/12/app-profile.jpghttp://techbpm.files.wordpress.com/2011/12/prpc-login-page.jpg7/31/2019 DCO Introduction
3/10
Suppose the customer has a requirement to build a college
course and enrollment application. Currently everything is
done manually, where the professor/tutor will publish the
course he/she wants to start on the college noticeboard.
The students will have to submit on a piece of paper or a
form the courses they want to enroll for a particular season.
This new application is expected to smoothen this process
to allow better control on the courses, its contents with
necessary approvals from the college administration.
Necessary logic such as if the number of students enrolled
for a particular course is less than 10, the course gets
cancelled. A student can choose not more than 3 courses
from a particular specialization. A student should have met
certain eligibility criteria in order to be chosen for a particular
course (say, he should have got atleast B grade in the pre-requisite courses).
So the users who would interact with the new system would
be -
1. Students (who will find the courses available and select
the ones they want to enroll)
2. Professor/Tutor (who can create new courses and publish
them) .. They can edit the course content
7/31/2019 DCO Introduction
4/10
3. School Administration ( Can review the courses published
and provide necessary approvals. They can also get a
visibility of how many students have enrolled for a particular
course)
Once a student gets selected for a course, he/she will
receive an email confirming of the same.
School Administration can generate reports. One such
report will list down the final selection of the students and
the courses they are assigned to.
The above is a simple scenario just to illustrate the module.
So lets begin.
Getting Started: You can enter Organization name, project
name, project led by and give a description about the project
http://techbpm.files.wordpress.com/2011/12/get-started.jpg7/31/2019 DCO Introduction
5/10
Overview: Indicate whether it is a new application or based
on Pega framework.. and list the objectives
Actors:
After you have entered all the actors, it will look like this..
Requirements : Enter project requirements
http://techbpm.files.wordpress.com/2011/12/actors-2.jpghttp://techbpm.files.wordpress.com/2011/12/actors-1.jpghttp://techbpm.files.wordpress.com/2011/12/overview.jpghttp://techbpm.files.wordpress.com/2011/12/actors-2.jpghttp://techbpm.files.wordpress.com/2011/12/actors-1.jpghttp://techbpm.files.wordpress.com/2011/12/overview.jpghttp://techbpm.files.wordpress.com/2011/12/actors-2.jpghttp://techbpm.files.wordpress.com/2011/12/actors-1.jpghttp://techbpm.files.wordpress.com/2011/12/overview.jpg7/31/2019 DCO Introduction
6/10
You will have the requirements listed as -
Work Types: There are 5 predefined work types (common,
security, navigation, datamanagement, sysadmin). For our
requirement, I have created 2 work types and have attached
http://techbpm.files.wordpress.com/2011/12/requirement-3.jpghttp://techbpm.files.wordpress.com/2011/12/requirement-2.jpghttp://techbpm.files.wordpress.com/2011/12/requirement-1.jpghttp://techbpm.files.wordpress.com/2011/12/requirement-3.jpghttp://techbpm.files.wordpress.com/2011/12/requirement-2.jpghttp://techbpm.files.wordpress.com/2011/12/requirement-1.jpghttp://techbpm.files.wordpress.com/2011/12/requirement-3.jpghttp://techbpm.files.wordpress.com/2011/12/requirement-2.jpghttp://techbpm.files.wordpress.com/2011/12/requirement-1.jpg7/31/2019 DCO Introduction
7/10
use cases
Interfaces: Just to introduce this to you, we can have an
interface with an external database to retrieve student
information.
PRPC provides support for many protocols..
http://techbpm.files.wordpress.com/2011/12/interfaces.jpghttp://techbpm.files.wordpress.com/2011/12/worktypes-2.jpghttp://techbpm.files.wordpress.com/2011/12/work-types-1.jpghttp://techbpm.files.wordpress.com/2011/12/interfaces.jpghttp://techbpm.files.wordpress.com/2011/12/worktypes-2.jpghttp://techbpm.files.wordpress.com/2011/12/work-types-1.jpghttp://techbpm.files.wordpress.com/2011/12/interfaces.jpghttp://techbpm.files.wordpress.com/2011/12/worktypes-2.jpghttp://techbpm.files.wordpress.com/2011/12/work-types-1.jpg7/31/2019 DCO Introduction
8/10
Reporting : You can enter your reporting requirements for
the course administrator
Correspondence: Enter correspondence details..
Assumptions: You can enter assumptions
http://techbpm.files.wordpress.com/2011/12/correspondence.jpghttp://techbpm.files.wordpress.com/2011/12/reports.jpghttp://techbpm.files.wordpress.com/2011/12/interfaces-1.jpghttp://techbpm.files.wordpress.com/2011/12/correspondence.jpghttp://techbpm.files.wordpress.com/2011/12/reports.jpghttp://techbpm.files.wordpress.com/2011/12/interfaces-1.jpghttp://techbpm.files.wordpress.com/2011/12/correspondence.jpghttp://techbpm.files.wordpress.com/2011/12/reports.jpghttp://techbpm.files.wordpress.com/2011/12/interfaces-1.jpg7/31/2019 DCO Introduction
9/10
Participants: The kind of team that is to be involved should
be entered..
Sizing: PRPC provides project effort modeling tool.
Click on
create project sizing button to generate PRPC project effort
modelling excel sheet.
http://techbpm.files.wordpress.com/2011/12/sizing.jpghttp://techbpm.files.wordpress.com/2011/12/participants.jpghttp://techbpm.files.wordpress.com/2011/12/sizing.jpghttp://techbpm.files.wordpress.com/2011/12/participants.jpg7/31/2019 DCO Introduction
10/10
Create
Document:
The application profile document generated is something
like this..
Application Profile
ADVERTISEMENT
http://techbpm.files.wordpress.com/2011/12/application-profile.dochttp://techbpm.files.wordpress.com/2011/12/application-profile.dochttp://techbpm.files.wordpress.com/2011/12/create-document.jpghttp://techbpm.files.wordpress.com/2011/12/sizing-sheet.jpghttp://techbpm.files.wordpress.com/2011/12/create-document.jpghttp://techbpm.files.wordpress.com/2011/12/sizing-sheet.jpghttp://techbpm.files.wordpress.com/2011/12/application-profile.doc